openspec-propose

To generate an OpenSpec change proposal in one step, this Skill automatically scaffolds the change directory and populates proposal.md, design.md, and tasks.md artifacts. This streamlines change creation by avoiding manual setup and coordination before implementation.

An OpenSpec change requires proposal.md, design.md, and tasks.md artifacts before implementation. This Skill generates these required files automatically by querying openspec status and instructions to create them in dependency order and verify apply readiness.

Yes, creating OpenSpec change proposals requires the openspec CLI installed and permission to run openspec status and openspec instructions commands, plus read and write file access in the change directory to generate the required artifacts.

Dependency-aware artifact generation queries openspec status and instructions to produce proposal, design, and task artifacts in the correct dependency order. This ensures the change scaffold is populated sequentially and verifies apply readiness before implementation begins.

Yes, you can track progress during OpenSpec artifact generation through a built-in todo and tracking mechanism that displays creation progress and lists generated artifacts. The Skill also uses interactive questions to clarify unclear inputs during the workflow.

The best way to scaffold an OpenSpec change for a feature request is to use automated one-step proposal generation, which creates the change scaffold and populates all required proposal, design, and task artifacts ready for engineering handoff.