Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/plan
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.
Passed 6 of 16 test cases with the skill, and 6 of 16 without it.
3 fixed5 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
While analyzing requirements REQ-STORAGE-002 and system design docs for docs/plans/cloud-storage/, we noticed that the existing storage service code directly contradicts the system design contract. Should we proceed with decomposing task work orders or pause?
| Checked | Without skill | With skill |
|---|---|---|
| Work order decomposition pauses when specification documents contradict implementation code. | Passed | Passed |
| The technical approach references relevant Architectural Decision Records. | Missed | Passed |
The instructions your model reads when the skill loads.
Translate requirements and system designs into a delivery plan under
docs/plans/<initiative>/. The plan and its work-order files are implementation
records. They are not product specifications.
Read docs/specs/guide/plans-and-work-orders.md and
docs/specs/guide/traceability-and-lifecycle.md before you write the plan.
Read these sources in full:
REQ-* or AC-* IDs.Use the legacy feature specification during migration only when no replacement requirement or design exists.
Read each spec's Implementation Plans and related-plan links, then inventory
all existing companion plan directories. Treat linked packages as one
synchronized implementation record: reconcile every affected task scope, E2E
scenario matrix, status, and exact final verification results/counts before
completion.
Create:
docs/plans/<initiative>/plan.md
docs/plans/<initiative>/task-<NN>-<short-slug>.md
plan.md is the work-package manifest. Each task-*.md file is one work order.
test cases passed, vs 6 / 16 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.