spec-design

To generate software development specifications, use a tool that creates design.md and tasks.md artifacts. It enforces structured documentation with context, goals, specifications, risks, and a dependency-ordered actionable checklist with file paths and acceptance criteria.

A design.md file should include structured documentation outlining context, goals, specifications, decisions, risks, and migration plans. This ensures all aspects of project design are clearly defined and organized before implementation begins.

Creating a dependency-ordered task list involves generating a tasks.md file with an actionable checklist. It maps out implementation steps by including specific file paths and acceptance criteria to guide the development workflow.

Yes, OpenSpec enforces specific formatting rules for requirements, scenarios, and tasks. It also enforces path configurations for the specs_path to maintain consistency across your software development documentation.

Starting the specification generation process typically uses a proposal.md as the foundational input. This allows the system to automatically generate the corresponding design.md and tasks.md files based on the proposed feature.

The best way to structure implementation tasks is to generate a tasks.md file with a dependency-ordered, actionable checklist. This file explicitly maps each task to specific file paths and acceptance criteria for clear development tracking.