generate-spec

To generate planning docs from templates, you can automate the creation of spec.md, tasks.md, and checklist.md. This ensures structured, spec-first workflows by automatically scaffolding the required planning artifacts into a centralized docs/plans folder.

A spec-first workflow requires generating planning documents before coding begins. You need to create planning artifacts like spec.md and tasks.md when your project demands explicit approvals, clarification tracking, and structured feature planning to ensure consistency across skills.

To track clarifications and enforce explicit approvals during feature planning, use a structured documentation approach that generates checklists and specs. This automates approval gating and ensures all requirements are mapped and backfilled after implementation.

Yes, you can reuse generated planning documents across multiple skills. The tool stores artifacts in a centralized docs/plans folder using a structured naming convention, enabling seamless access and synchronization for multi-skill workflows.

To backfill status and map requirements after implementation, the planning doc generator synchronizes your tasks.md and checklist.md files. This updates the tracking documents to reflect the completed work and maintains consistency with the original spec.

The best way to organize planning artifacts is to store them under a dedicated docs/plans directory using a dated naming convention. This targets workflows requiring structured, spec-first approaches and ensures artifacts are easily reusable by other skills.