openspec-propose

You can generate a change proposal and related artifacts in one step by providing a high-level description or change name. The workflow derives a kebab-case identifier and scaffolds proposal.md, design.md, and tasks.md automatically in dependency order.

Scaffolding a new change proposal generates three core artifacts: proposal.md, design.md, and tasks.md. This ensures all required project-planning artifacts are created together to align stakeholders with specs and implementation tasks.

Yes, the openspec CLI is required to automate proposal and task generation. The process relies on the openspec CLI to scaffold changes, generate artifacts, and track status throughout the workflow.

You can standardize change management workflows across teams by using a single-command proposal process. Providing a quick high-level input auto-generates consistent design specs and tasks, ensuring uniform artifact creation.

The best way to track status after generating a change proposal is through the openspec CLI. It manages the guided workflow, scaffolds the initial artifacts, and tracks the change status throughout its lifecycle.

The workflow resolves dependencies by prompting for input and creating required artifacts in strict dependency order. This ensures the proposal, design, and tasks files are generated sequentially based on their relationships.