openspec-propose

To generate design and task artifacts for an OpenSpec change proposal, you provide a rough idea or kebab-case name, and the workflow automatically scaffolds the proposal, design, and tasks in dependency order until apply-ready.

The best way to turn a rough idea into an implementation-ready change proposal is using a coordinated workflow that auto-generates required artifacts, queries status in JSON, and stops only when all apply-ready requirements are complete.

Artifact generation handles missing context during spec design by asking for user clarifications when information is unclear, then continuing the dependency-aware creation of the remaining implementation tasks.

Yes, the workflow satisfies OpenSpec CLI requirements by creating a change, querying status and instructions in JSON, and writing artifacts from templates to ensure the output is fully apply-ready.

Yes, you can scaffold a new OpenSpec change from a descriptive text, as the system derives the required kebab-case name from your description to begin generating the proposal artifacts.

Automated proposal generation for task planning is limited to producing artifacts in dependency order until apply-ready requirements are met, stopping without executing the actual implementation or deployment phases.