openspec-propose

To generate OpenSpec change proposals, provide a clear change name or description to scaffold required artifacts. This process creates proposal.md, design.md, and tasks.md files under openspec/changes/<name>/, ready for implementation planning and governance alignment.

The OpenSpec workflow scaffolds project management artifacts by deriving a kebab-case change name and generating structured proposal, design, and tasks documents. It tracks dependencies to align governance and implementation planning for coordinated team changes.

Yes, automated artifact generation applies to cross-file edits, framework changes, and collaborative tasks. By processing a provided change description, it outputs ready-for-implementation files that coordinate complex development efforts across your project.

The best way to structure collaborative change proposals is using a standardized OpenSpec workflow that enforces guardrails. It scaffolds proposal.md, design.md, and tasks.md files, ensuring all dependencies are tracked and implementation plans are clearly defined.

You need an environment supporting the openspec directory structure to scaffold artifacts. The workflow generates files directly under openspec/changes/<name>/, requiring no additional dependencies to output ready-for-implementation proposal, design, and tasks documents.