writing-plans

Generate a comprehensive implementation plan that breaks complex features into bite-sized tasks (2-5 minutes each), complete with exact file paths, code snippets, test instructions, and commit steps. This ensures any engineer, regardless of codebase familiarity, can execute the plan efficiently.

An implementation plan specifies every file modification, test case, documentation update, and verification command needed to build an API endpoint. It follows DRY and YAGNI principles, provides precise paths and commands, and sequences tasks so engineers can work through TDD cycles and commit incrementally.

Yes. Implementation plans eliminate onboarding friction by providing zero-context-ready instructions—no prior codebase knowledge required. New team members or AI subagents can follow the exact steps, file modifications, and verification commands immediately after design phases complete.

Structure a refactor plan with granular steps that isolate each code change, specify affected files and tests, and include commands to verify the refactor works. This approach applies refactoring patterns consistently and prevents missed dependencies or regression.

Use an implementation plan to map the feature workflow: start with design, then generate a comprehensive plan with precise file touches, test coverage, documentation, and commit sequences. Save the plan as a markdown document for reference and handoff to any team member or agent.