Skip to content

ericrisco/rsc-harness / skills/plan

Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify and tasks: architecture, contracts, data flow, testing strategy, sequencing and risks, at structure altitude, never framework syntax. NOT the what/why spec (that is `specify`), NOT the ambiguity sweep (that is `clarify`), NOT the task breakdown (that is `tasks`), NOT the code (that is `implement`).

FileKindSize
SKILL.mdskill md9.9 KB
evals/README.mdmarkdown3.7 KB
evals/cases.yamlconfig5.3 KB
references/plan-template.mdmarkdown6.0 KB

evals/cases.yaml

View on GitHub
skill: plan

should_trigger:
  - prompt: "We've got the signed-off spec for the checkout-reservation feature. Now design the architecture and how the pieces talk to each other before anyone codes."
    why: "Clarified spec in hand, asking for architecture + component contracts before code — the exact intent → tasks slot this skill fills."
  - prompt: "Write the implementation plan for the new notifications service: components, the contracts between them, the data flow, and how we'll test it."
    why: "Names every plan section (architecture, interfaces, data flow, testing strategy) without naming the phase — squarely in scope."
  - prompt: "How should we build this? I want the data model, where each thing lives, what's transactional, and the order we can build it in."
    why: "Data model + consistency boundaries + sequencing is the plan artifact; phrased as a 'how do we build' question, the structure-not-syntax altitude."
  - prompt: "Before we start the feature, lay out the testing strategy — which seams get unit vs integration tests and what we have to mock to stay fast."
    why: "Choosing test LEVELS per seam and what to fake is plan's testing-strategy section (strategy, not tooling)."
  - prompt: "What are the main risks in this design and what could go wrong once we wire it to the payments provider? Rank them with mitigations."
    why: "Ranked risk register with triggers/mitigations is plan §7; the non-obvious framing is 'what could go wrong', not the word 'plan'."
  - prompt: "We have the spec and the clarifications are all resolved. What's the blueprint to get from here to shipping?"
    why: "Explicitly post-clarify, asking for the technical blueprint — the handoff point clarify → plan, no stack named."
  - prompt: "Sketch the box-and-arrow architecture and the interface each component promises, keeping it stack-neutral so the FastAPI/Go choice comes later."
    why: "Architecture diagram + language-neutral contracts above the seam is precisely plan's altitude and its defer-to-stack rule."

should_not_trigger:
  - prompt: "I have a fuzzy idea for a referrals feature but no spec yet. Help me pin down what we're building and why."
    route_to: "specify"
    why: "Requirements capture from a fuzzy intent — that's specify; there's no spec to plan from yet."
  - prompt: "The spec is written but vague on edge cases and what happens on a partial failure. Help me surface the ambiguities and resolve them."
    route_to: "clarify"
    why: "De-risking an existing spec by surfacing ambiguities is clarify, the gate that must pass before plan."
  - prompt: "The plan's approved. Break it into an ordered checklist where each item has a done-check I can verify independently."
    route_to: "tasks"
    why: "Slicing an approved plan into an ordered, verifiable task list is the tasks phase, not planning."
  - prompt: "Write the actual SQL schema, the indexes, and the EXPLAIN-verified migration for the orders table."
    route_to: "postgresdb"
    why: "Concrete DDL/indexes/migration mechanics are below the plan's altitude — the postgresdb stack skill owns them."
  - prompt: "Implement the Go HTTP handler and the table-driven tests for the reservation endpoint we planned."
    route_to: "go"
    why: "Writing the actual handler + test code is implement-time stack mechanics (go), not the structure-level plan."
  - prompt: "What are our project-wide non-negotiables — the stack canon and quality bars every feature must respect?"
    route_to: "constitution"
    why: "Capturing project-wide principles is the constitution phase; plan reads it but doesn't author it."

capability:
  - scenario: "User says: 'We have a clarified spec for an order-reservation feature (reserve stock for a cart for 15 minutes, then auto-release; must be idempotent per cart; calls an external payments provider). Write the implementation plan.' The agent has read the spec and constitution."
    must_include:
      - "Writes the artifact to 02-DOCS/wiki/sdd/plans/<slug>.md using the seven-section structure (context, architecture, interfaces, data model/flow, testing strategy, sequencing, risks)"
      - "Architecture section names components with single responsibilities and marks the payments provider as EXTERNAL; states one top architectural decision with a reason tied to a constraint"
      - "Interfaces section gives a language-neutral contract for reserve (inputs → outputs incl. error modes) and explicitly states the idempotent-on-cartId invariant and the 15-minute auto-release"
      - "Data model + flow names entities at the model level (not DDL) and calls out the consistency/transactional boundary; defers concrete schema/indexes/migration to the postgresdb stack skill rather than writing SQL"
      - "Testing strategy maps each acceptance criterion to a test level (unit/contract/integration/e2e), states what each asserts and what it mocks (e.g. the payments provider), and defers the test runner/tooling to the stack skill"
      - "Risks section is ranked with trigger + impact + mitigation per risk (e.g. payments timeout, double-reservation race); does NOT claim zero risk"
      - "Stays stack-neutral above the seam — no framework route decorators, ORM session code, or test-runner flags in the plan"
      - "Ends by pointing to the tasks phase and notes indexing the plan in 02-DOCS/wiki/index.md (the Knowledge map), never the root CLAUDE.md"
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall