writing-plans

Creating a detailed implementation plan involves generating bite-sized, actionable steps that guide engineers through file modifications, code implementation, testing, and commit procedures. The plan assumes an engineer with general skills but no specific project context, saving outputs to `docs/plans/`.

The best way to break down a feature is to enforce task breakdown into small steps that incorporate best practices like TDD, DRY, YAGNI, and frequent commits. This provides contextual guidance by detailing necessary file modifications and testing procedures for each phase.

Yes, generated implementation plans offer subagent-driven or parallel execution options. The plans provide comprehensive contextual guidance and task breakdown, allowing multiple development steps to be executed concurrently by different agents or engineers.

Yes, this planning approach enforces best practices by embedding TDD, DRY, YAGNI, and frequent commits directly into the workflow. It guides developers from writing failing tests to committing the final code, ensuring documentation and testing are integral to the implementation steps.

You need a step-by-step implementation plan when starting a new feature, especially if engineers lack context about the codebase. It bridges the context gap by providing detailed guidance on file modifications, code implementation, testing, and documentation procedures.