plan-creator

You can generate an architectural plan for a new feature by providing a natural language description or a design file path. The system creates a structured implementation plan under docs/plans and commits it directly to git.

A design-to-plan workflow converts feature descriptions or design documents into structured implementation plans. It identifies the modules, components, and interfaces needed before any coding begins in an existing codebase.

Yes, you can use a markdown design file as input for feature planning by providing its file path. The system processes the design document and transforms it into a structured architectural plan saved under docs/plans.

Yes, the plan creation process supports automated git commits. After generating the architectural design document under the docs/plans directory, the workflow automatically executes a git commit step to save the changes.

The best way to structure end-to-end implementation plans is to define modules, components, and interfaces before coding begins. This approach uses a loop or swarm executor to process inputs and output plans to docs/plans.

You need to create a design doc for new codebase features when starting brownfield work and need to define modules and interfaces before coding. It helps generate end-to-end plans from ideas to concrete design artifacts.