openspec-propose

To generate a complete change proposal in one step, you can use an automated CLI workflow that creates design.md, specs.md, and tasks.md artifacts simultaneously from a basic description. This dependency-driven process ensures all required files are produced and ready for immediate design review and planning.

An artifact-driven workflow for project change management is a process that scaffolds required documentation files like design specs and tasks based on dependencies. It guides teams through a sequence to ensure all necessary artifacts are generated and validated before implementation, streamlining the transition from request to structured proposal.

Yes, you can use the openspec CLI to scaffold a change proposal directly from a simple text description. The CLI initiates a one-step workflow that automatically generates the required design, specifications, and implementation tasks, satisfying status checks and dependency-driven artifact creation.

Automated proposal generation works for teams needing structured design review and planning by transforming a user request into a complete, scaffolded proposal. It produces standardized design and tasks artifacts, enabling rapid iteration and ensuring all dependency requirements are met for team review.

The best way to automate design specs and tasks generation is using a one-step CLI workflow that processes a change description and outputs structured artifacts. This approach handles dependency-driven creation automatically, ensuring design.md, specs.md, and tasks.md are consistently formatted and ready for planning.

Your change proposal workflow requires dependency-driven artifact creation to ensure structural consistency and completeness across generated files. By guiding the sequence of artifact generation, the system enforces status checks and guarantees that design, specs, and tasks are correctly linked before the proposal is finalized.