openspec-propose

To generate a project proposal, you provide a brief description of the change and run a CLI workflow. This automatically scaffolds a complete proposal.md, design.md, and tasks.md to ensure end-to-end readiness for implementation.

The best way to scaffold design and task artifacts is using an automated CLI-driven workflow that applies frontmatter metadata and dependency-based generation. This creates a unified proposal, design, and tasks file set from your initial input.

Yes, you can auto-generate proposal, design, and tasks files in one step. By submitting a brief description, the system enforces a guided workflow that outputs all three artifacts simultaneously to save planning time.

Yes, the artifact generation workflow requires a kebab-case naming convention. It determines a kebab-case change name directly from your input description to maintain consistent file and project tracking.

You need a CLI-driven scaffold for change proposals when a team requires an end-to-end plan ready for implementation. It enforces structured frontmatter metadata and dependency-based artifact generation to ensure alignment across teams.