he-plan

To generate an executable project plan from a technical specification, use a tool that reads the spec file and outputs a structured document with milestones, concrete steps, and validation criteria. This ensures the resulting plan is actionable and ready for implementation.

The best way to break down a spec into verifiable milestones with observable outcomes is to parse the specification document and translate its requirements into a structured plan containing discrete, verifiable milestones, concrete commands, and recovery steps.

Yes, you can create a step-by-step execution plan that a novice developer can follow by transforming the technical specification into a self-contained, detailed guide. This plan includes concrete commands, validation steps, and recovery procedures to ensure clarity and completeness.

Yes, the generated plan supports iterative refinement and domain document population. After the initial plan is created from the specification, it can be iteratively refined to populate domain documents and adapt to evolving project requirements.

Generated plans adhere to a specific markdown structure, typically `docs/PLANS.md`, to ensure project execution consistency. This structure standardizes milestones, concrete steps, validation, and recovery procedures across the development workflow.

You should not use automated spec to plan generation when your technical specification is incomplete or lacks clear requirements, as the tool relies entirely on the input spec to generate accurate milestones, concrete steps, and validation criteria.