openspec-propose

Generate a complete change proposal by providing a feature description; the system automatically scaffolds schema-compliant design documents and implementation task lists in correct dependency order, eliminating manual artifact creation.

Automating design document creation is best handled by generating coordinated proposal artifacts in one step, ensuring all documents align with OpenSpec standards and integrate context from dependent documents automatically.

Yes, generating schema-compliant change proposal artifacts requires the OpenSpec CLI to process documents in the correct dependency order and integrate context from completed dependent documents automatically.

Yes, you can generate a ready-to-implement proposal package from a single feature description request, producing all required change artifacts including design documents and task lists without manual writing.

Manual change proposal creation causes inconsistency because coordinating design documents and task lists by hand is time-consuming and prone to structural misalignment across different artifact types.

You need to scaffold change proposal artifacts in dependency order when creating coordinated software development initiatives, ensuring generated design documents and task lists follow project-defined OpenSpec rules.