writing-plans

Implementation plans specify exact file paths, concrete code samples, and verification steps for each task. This Skill generates zero-context plans that break features into 2-5 minute bite-sized actions, including tests, implementation, and commit instructions, so any engineer can execute them without domain knowledge.

Comprehensive plans cover functional and technical requirements, exact file paths, complete code examples, test cases, documentation, verification steps, a standardized header, and a step-based workflow. They support frontend, backend, and tooling tasks using DRY, YAGNI, and TDD principles.

Yes. After design approval, plans provide step-by-step instructions for endpoint implementation, including TDD steps, exact commands with expected output, code samples, tests, and commit messages—enabling engineers to ship features consistently.

Plans assume zero context and include all necessary information: precise file locations, complete code, expected command outputs, and verification procedures. New engineers execute tasks directly without requiring codebase familiarity or domain expertise.

Plans translate designs into actionable steps with concrete deliverables: exact file paths, runnable code examples, test cases, and verification commands. They enforce disciplined workflows and eliminate ambiguity, unlike architectural overviews.

Yes. Plans cover not just code implementation but also documentation, setup instructions, and tooling across the full stack, breaking all work into bite-sized, verifiable tasks with clear completion criteria.