openspec-propose

Generate complete OpenSpec change proposals with specs, design, and tasks artifacts.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-propose-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-propose-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable implementation plan requires writing proposals, spec deltas, design documents, and task lists by hand. This Skill automates that entire planning phase through the OpenSpec CLI, producing all required artifacts in one guided workflow. ## Core Features & Use Cases - One-Step Change Creation: Creates a change directory and generates every required artifact (proposal.md, spec deltas, design.md, tasks.md) in dependency order. - Schema-Aware Planning: Uses the configured OpenSpec workflow schema, resolves artifact dependencies via openspec status, and follows per-artifact instructions and templates. - Planning-Only Guardrails: Strictly limits the workflow to planning artifacts, never editing project code or starting implementation until explicitly requested. - Use Case: Describe "add user authentication" and receive a complete change folder with a proposal, capability spec delta, design document, and ordered implementation tasks ready for review. ## Quick Start Ask the assistant to propose a new OpenSpec change for the feature you want to build, for example by describing the change and letting it generate the full proposal, specs, 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?▼

Describe what you want to build and the skill derives a kebab-case change name, runs `openspec new change`, then generates every required artifact in dependency order. You get proposal.md, spec deltas, design.md, and tasks.md ready for review.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it includes proposal.md (what and why), spec deltas under specs/<capability-path>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set is determined by the schema's dependency graph.

Does openspec-propose implement the change after planning?▼

No. The workflow is strictly planning-only and stops after all artifacts are created. Implementation requires a separate explicit request that starts the apply workflow, such as running /opsx-apply.

Can I use a different OpenSpec workflow schema?▼

Yes, but only when you explicitly request a schema by name. The skill then passes --schema <schema-name> to `openspec new change`; otherwise it uses the configured default schema.

What happens if a change with the same name already exists?▼

The skill asks whether you want to continue the existing change or create a new one before proceeding, avoiding accidental overwrites of in-progress planning work.