openspec-propose

Generates complete OpenSpec change proposals with design, specs, and tasks from a slice contract.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill openspec-propose-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Wizarck/nexandro/tree/main/skills/openspec-propose
Command: npx skills add https://github.com/Wizarck/nexandro --skill openspec-propose-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually scaffolding a change proposal with its design document, specs, and task list is slow and error-prone, especially when each change must stay consistent with an approved slicing contract. This Skill automates the entire proposal phase of the BMAD+OpenSpec workflow in one step. ## Core Features & Use Cases - One-step artifact generation: Creates proposal.md, design.md, and tasks.md for a change by driving the openspec CLI through its dependency-ordered artifact workflow. - Slice contract enforcement: Reads the approved change list in docs/openspec-slice.md and enriches each proposal with the FRs, dependencies, components, and scope notes approved at Gate C, refusing unknown change IDs. - Batch and ad-hoc modes: Supports --batch to scaffold every slice row in dependency order, and --no-slice for legacy ad-hoc changes described inline. - Use Case: After approving a slicing document, run the Skill with a change ID like "add-supplier-pricing" to get a fully populated change folder under openspec/changes/ ready for implementation. ## Quick Start Ask the assistant to propose the change "add-supplier-pricing" from the slice file so it scaffolds the full OpenSpec change with proposal, design, and tasks.

Frequently Asked Questions about openspec-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenSpec change proposal automatically?▼

Invoke the Skill with a change ID that exists in docs/openspec-slice.md. It runs openspec new change, then generates proposal.md, design.md, and tasks.md in dependency order using openspec instructions until all apply-required artifacts are done.

What is the openspec-slice.md file used for?▼

It is the canonical slicing artifact produced by the BMAD phase. The Skill parses its approved change list and scope notes to pre-fill each proposal with FRs, dependencies, components, and journeys approved at Gate C.

Can I propose a change that is not in the slice file?▼

Yes, by passing --no-slice. The Skill then asks what you want to build, derives a kebab-case name, and scaffolds the change without the FR and dependency enrichment from the slice contract.

Why does the Skill refuse my change ID?▼

The change ID is not a row in the resolved slice file. Either add it by re-slicing and re-approving Gate C, or rerun with --no-slice for ad-hoc changes; the Skill never auto-adds rows.

Does openspec-propose support batch scaffolding?▼

Yes, the --batch flag iterates every slice row in dependency order, skipping already-scaffolded folders, and emits one summary of scaffolded, skipped, and failed counts.