writing-plans

An implementation plan breaks down feature development into small, actionable steps with exact file paths, complete code examples, and verification procedures. This Skill generates comprehensive, step-by-step plans that engineers with zero codebase context can follow to execute features correctly, ensuring clarity and reducing errors.

Task breakdowns should specify exact file references, runnable code samples, explicit test instructions, and expected outputs for each step. This Skill structures plans into 2-5 minute tasks aligned with DRY, YAGNI, and TDD principles, making workflows repeatable and commit-friendly across team handoffs.

Yes. After finalizing a design, this Skill generates detailed implementation plans assuming minimal domain knowledge, providing complete code examples and exact commands so any engineer can build the feature correctly without codebase familiarity or extensive guidance.

Vague plans leave engineers guessing about file structure, code patterns, and testing strategy, leading to rework, inconsistency, and context-switching overhead. Detailed plans with precise file paths, runnable samples, and verification steps eliminate ambiguity and accelerate execution.

Breaking features into small, bounded tasks with explicit commands and expected outputs reduces cognitive load and decision paralysis. Engineers execute predictable steps, verify progress immediately, and maintain momentum, turning complex implementations into manageable workflows.

After plan generation, execution options include subagent-driven implementation or parallel session handoff. The structured plan with exact file references and code samples becomes a repeatable, commit-friendly workflow any team member can execute independently.