writing-plans

To turn a spec into an implementation plan, the skill breaks down multi-step engineering work into bite-sized, 2–5 minute test-driven tasks like writing failing tests, implementing minimal code, and committing frequently.

Creating build-ready task plans requires spelling out exact file touchpoints for modifications, detailing testing instructions, and specifying which documentation to consult, minimizing guesswork and missing context during development.

External API grounding in an implementation plan requires verifying real API response shapes with actual calls, then embedding the verified response directly in the plan to avoid mock assumptions during development.

The best way to plan multi-step engineering work for subagent delegation is to include explicit plan document headers that route execution through a subagent-driven-development approach for task-by-task building and review.

Yes, this approach is specifically designed for new features where the implementer needs exact file touchpoints, guided task granularity, and explicit testing instructions to minimize rework during multi-step engineering work.

Build-ready implementation plans generated from your requirements should be saved under the docs/plans directory to maintain organization and ensure easy access for subagent-driven execution.