openspec-propose

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

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-propose-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-propose
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-propose-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing specs, design documents, and task lists by hand. This Skill automates that planning phase by driving the OpenSpec CLI to scaffold a change and generate every required artifact in dependency order. ## Core Features & Use Cases - One-step proposal generation: Creates proposal.md, spec deltas, design.md, and tasks.md from a single user description. - Schema-aware artifact ordering: Reads the OpenSpec status JSON to resolve artifact dependencies and builds them in the correct sequence. - Store and schema support: Works with registered OpenSpec stores and custom workflow schemas when explicitly requested. - Use Case: A developer says "add user authentication" and receives a complete planning package—proposal, capability spec delta, design notes, and implementation tasks—ready for review before any code is written. ## Quick Start Ask the assistant to propose a new change, for example: "Create an OpenSpec proposal for adding user authentication to the app."

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 or provide a kebab-case change name. The workflow runs openspec new change, then generates every required artifact—proposal, specs, design, and tasks—in dependency order using the openspec CLI.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it creates proposal.md (what and why), spec deltas under specs/<capability-path>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set depends on the configured schema.

Does openspec-propose implement the change after planning?

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

Can I use a custom schema or registered store with OpenSpec?

Yes. Explicitly name a schema to pass --schema, or name a registered store to append --store <id> to CLI commands. Otherwise the configured default schema and nearest local openspec root are used.

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

The workflow asks whether you want to continue the existing change or create a new one, rather than overwriting or duplicating work silently.