openspec-propose

To generate a feature proposal with design and tasks in one step, describe your intended change in plain language. The system outputs standardized proposal.md, design.md, and tasks.md files, applying frontmatter metadata to align stakeholders quickly.

A standardized change management proposal includes proposal.md, design.md, and tasks.md artifacts. These files package requirements, technical specs, and implementation tasks into cohesive documents for product and engineering review.

Yes, you can use plain language to create product specs and design documents. Describing a feature request or improvement in plain text triggers automated generation of standardized planning artifacts with appropriate frontmatter metadata.

Yes, the generated proposal follows standardized templates and metadata formats. It ensures all output artifacts, including design and specs, apply consistent frontmatter metadata for streamlined change management and stakeholder alignment.

The best way to streamline planning for a new feature request is generating cohesive artifacts in one step. Packaging design, specs, and tasks into standardized documents aligns product, design, and engineering stakeholders quickly for review.