writing-plans

Implementation plans bridge knowledge gaps before coding by breaking specifications into bite-sized tasks with explicit steps, required file modifications, tests, and commit history. This ensures every stakeholder understands the required milestones and execution handoff for predictable delivery.

Test-driven development planning requires a comprehensive, structured plan document with a standardized header that enforces deterministic execution steps. It outlines specific tests to write and documentation to update before touching any code, ensuring thorough coverage across a dedicated worktree.

Yes, implementation planning supports a test-driven development workflow within a dedicated worktree. It generates standardized plan documents that track bite-sized tasks, explicit execution steps, and commit history to ensure isolated and predictable feature delivery.

To generate a complete plan, provide the feature name and constraints to produce a structured document detailing files to touch, tests to write, documentation to update, and commit history. This prevents missed requirements by enforcing a standardized header and bite-sized task granularity.

You should write a comprehensive implementation plan for multi-step engineering tasks that require deterministic steps and thorough documentation. Planning before touching code bridges knowledge gaps, aligns stakeholders on milestones, and ensures predictable delivery through structured execution handoffs.