writing-plans

To generate an implementation plan from a feature brief, the skill outputs a structured document with a standard header, bite-sized task breakdown, explicit file paths, and commands. It targets software projects where a spec exists but code has not yet been written, ensuring pre-development alignment across engineers and stakeholders.

Breaking down software tasks before coding requires producing bite-sized task granularity that covers code, tests, docs, and commits. The skill enforces DRY, YAGNI, and TDD principles to guide teams toward writing minimal, testable steps, ensuring complete alignment on required files and scope.

Task decomposition for test-driven development planning works by enforcing DRY, YAGNI, and TDD emphasis to guide teams in writing minimal, testable steps. It automatically generates a complete, repeatable implementation plan that covers code, tests, docs, and commits, ensuring alignment on scope before any code is written.

Yes, generated implementation plans can be saved to a reproducible file path. The skill automatically saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md, including a standard Plan Document Header, task sections, and explicit file paths and commands following a specific structure.

Yes, you need an existing software specification. The skill specifically targets software projects where a spec exists but code has not yet been written, using the feature brief to enable pre-development alignment across engineers, testers, and stakeholders before generating the step-by-step plan.

Creating implementation plans before writing code helps teams quickly generate a complete, repeatable plan for complex tasks. This ensures alignment on scope, required files, tests, docs, and commits, preventing miscommunication across engineers, testers, and stakeholders during the development process.