openspec-propose

To generate a change proposal, you provide a concise sentence describing the desired change. The tool then derives a kebab-case name and automatically outputs proposal.md, design.md, and tasks.md artifacts under openspec/changes/<name> for immediate implementation.

Transforming vague feature requests into structured task tracking documents requires generating an artifact set. This tool creates a ready-to-implement plan by producing proposal, design, and task artifacts that streamline project planning and document dependencies for audit.

Yes, the openspec workflow supports tracking change proposal progress to ready-for-apply status. It follows the official openspec CLI workflow to generate artifact files, document dependencies, and monitor the proposal state from creation through to application readiness.

You can automatically derive kebab-case identifiers for design documentation by providing a simple text description. The interactive flow asks for a change name when needed, derives the identifier, and creates structured artifacts without manual file naming.

Creating proposal, design, and task files without manual formatting is done by entering a concise change description. The system automatically generates proposal.md, design.md, and tasks.md in the openspec/changes directory, ensuring standardized documentation.