requirement-to-plan

To convert natural-language requirements into executable task plans, you provide a clear text prompt containing the goal, scope, and constraints. The system then generates a structured plan file and initiates the task workflow automatically.

The task planning workflow integrates with git by creating a dedicated feature branch named using the yymm-dd-task-desc format. It initiates work with a task-start commit and finalizes it by moving the plan to docs/done with a task-done commit.

The required file naming convention for project planning documents is yymm-dd-task-desc.md. Files must be created under the docs/ directory and moved to docs/done upon task completion to maintain an auditable repository structure.

Yes, you can automate task lifecycle commits for project planning in docs. The process enforces branch creation and generates task-start and task-done commits to ensure a repeatable and auditable version control history.

To generate a project plan file, you need to provide inputs such as the project Goal, Scope, Constraints, Acceptance criteria, and a short task slug extracted from your natural-language prompt.

The best way to structure vague feature requests for version control is to translate them into concrete markdown plans under docs/ using a standardized naming format. This approach pairs planning documents directly with lifecycle branching and commits.