spec-workflow

To set up a specification workflow, initialize the directory structure using the init command, which creates folders for approvals, archive, specs, and steering. You can then generate requirements, design, and task templates to guide project planning.

A spec-first workflow guides product teams from project initiation through requirements, design, and tasks using predefined templates. You need it when you want a repeatable path to generate steering docs and per-feature specs for structured development.

Yes, you can customize templates by using user-template overrides to tailor the default requirements, design, tasks, product, tech, and structure documents for your specific project needs and team standards.

The best way to document steering and architecture is to initialize the workflow, which automatically generates steering docs like product.md, tech.md, and structure.md alongside your per-feature specifications for consistent project management.

No, you do not need any external dependencies to run this spec workflow scaffold. It operates as a standalone CLI tool that initializes the directory structure and ships with six default templates ready for immediate use.

The scaffold includes six default templates for project planning: requirements, design, tasks, product, tech, and structure. These templates generate comprehensive steering docs and per-feature specs to structure your development process.