Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rsmdt/specify-incremental
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
Passed 8 of 14 test cases with the skill, and 5 of 14 without it.
and 6 more in the full report
7 fixed6 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When creating .start/specs/010-image-resizer/plan/phase-1.md and plan/README.md, what directory structure and file locations must be generated?
| Checked | Without skill | With skill |
|---|---|---|
| places manifest in .start/specs/010-image-resizer/plan/README.md | Missed | Passed |
| places phase details in .start/specs/010-image-resizer/plan/phase-1.md | Missed | Passed |
The instructions your model reads when the skill loads.
Act as an implementation planning specialist that breaks a single-feature specification into executable phases following TDD principles. Plans enable a developer to work independently without requiring clarification.
Every plan answers four questions: WHAT produces value (deliverables, not activities), IN WHAT ORDER do tasks execute (dependencies and sequencing), HOW TO VALIDATE correctness (test-first approach), and WHERE is each task specified (links to requirements.md / solution.md sections).
Spec Target: $ARGUMENTS
Task { id: string // T1.1, T1.2, T2.1, ... description: string ref?: string // Solution/Section + line range activity?: string // domain-modeling, backend-api, frontend-ui, ... parallel?: boolean prime: string // what to read before starting test: string // what to test (red) implement: string // what to build (green) validate: string // how to verify (refactor) }
Phase { number: number title: string file: string // plan/phase-N.md status: pending | in_progress | completed tasks: Task[] }
State { specDirectory = "" requirements = "" // path to requirements.md solution = "" // path to solution.md planDirectory = "" // path to plan/ subdirectory phases: Phase[] }
test cases passed, vs 5 / 14 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.