feature-plan

Generates a staged, TDD-driven implementation plan from an existing feature design document.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-plan-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-plan
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-plan-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished technical design into an executable implementation plan is error-prone: stages get cut too large, codebase assumptions go unverified, and dependencies between work items stay implicit. This Skill converts an existing feature design into a staged, test-driven plan where each stage is a committable unit with verified test commands and an explicit parallel-execution schedule. ## Core Features & Use Cases - Design-grounded planning: Reads the design file end-to-end, refuses to plan when open questions remain, and halts back to the design step when decisions are missing. - Codebase verification: Confirms the design's claims about existing files, symbols, contracts, and test infrastructure before drafting, and records the real test runner commands with an observed baseline. - Staged TDD plan with execution schedule: Produces committable stages following write-test, confirm-fail, implement, confirm-pass, and groups independent stages into parallel batches using a named independence rule. - Use Case: After finishing a technical design for a new reminders feature, run the skill to get a plan of five staged commits, each with its own failing-test-first steps, plus a schedule showing which stages can be built concurrently. ## Quick Start Ask the assistant to run /feature-plan to turn the latest feature design into a staged TDD implementation plan.

Frequently Asked Questions about feature-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature design into an implementation plan?

Run /feature-plan after completing a design with /feature-design. It reads the design, verifies its claims against the codebase, and writes a staged TDD plan where each stage is one committable unit with test-first steps.

How do I break a large feature into smaller committable stages?

The skill drafts stages sized so each lands green with its own tests, then groups independent stages into parallel batches using an explicit independence rule. Stages are never split or invented just to gain parallelism.

Can I plan an implementation without a finished design document?

No. The skill requires a real design file resolved by feature-resolve and halts if the design's open-questions section is non-empty. Run /feature-design first to close those decisions, then plan.

Does the plan verify test commands before implementation starts?

Yes. The planning subagent identifies the project's test runner from manifests and CI config, executes each recorded command once, and records the observed baseline in the plan so an already-red suite surfaces before any stage runs.

What happens when the design contradicts the actual codebase?

The grounding step reads the code behind every design claim, including shapes, mechanisms, anchors, and deleted symbols. Conflicts and gaps are raised during review, recorded as planning decisions, or corrected in the design before drafting.