writing-plans

To turn a feature spec into an implementation plan, decompose requirements into bite-sized, testable tasks with explicit file touchpoints, tests, and commit history. This provides a clear roadmap guiding end-to-end execution while preserving DRY and TDD principles.

Test-driven planning is decomposing feature specifications into task-based roadmaps where each task defines explicit tests and interfaces before implementation. It ensures plans are auditable and bite-sized, enforcing TDD, DRY, and YAGNI principles across execution and review.

Break down work for an existing codebase by mapping specification requirements to specific file touchpoints and interfaces. Create a project-wide plan header that outlines the required tests, documentation, and commit sequence for each isolated task.

Yes, task decomposition from a spec works for both new features and existing codebases. It generates a comprehensive, reusable plan structure by mapping required file changes, tests, and documentation across diverse engineering teams.

The best way to enforce DRY and YAGNI principles during planning is to use a structured plan layout that decomposes specifications into isolated, testable tasks. This prevents over-engineering by defining strict file touchpoints and test interfaces upfront.

Yes, you can generate a commit sequence and documentation map from a feature specification. Decomposing the spec into a comprehensive plan provides explicit commit history and file touchpoints for each task, leaving engineers with a clear roadmap.