writing-plans

To convert a feature spec into an implementation plan, you provide the specification details and the tool generates a structured task breakdown covering files, tests, documentation, and commits. The plan is then saved as a markdown file.

The best way to break down vague software specifications is to use a planning tool that translates them into comprehensive, end-to-end implementation plans. This process specifies exactly what files to touch, how to implement, and how to test.

The worktree workflow keeps planning isolated by supporting a dedicated worktree environment. This separates the generated implementation plans and task breakdowns from your main development branch.

Yes, the generated implementation plan includes testing and commit history strategies. It creates a comprehensive task breakdown that explicitly covers what files to touch, how to test, how to document changes, and how to structure commits.

Yes, you can use this for end-to-end task breakdowns across multiple files. It is specifically applicable to software engineering projects requiring comprehensive implementation plans that detail modifications, testing, and documentation across the codebase.

Generated implementation plans are saved in the docs/plans directory using a date-based naming convention. This structure ensures easy versioning and quick retrieval of your task breakdowns.