openspec-propose

Creates OpenSpec change proposals with specs, design, and tasks artifacts.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/aguachis/Nicole-DB --skill openspec-propose-aguachis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/aguachis/Nicole-DB/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/aguachis/Nicole-DB --skill openspec-propose-aguachis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a rough feature idea into a complete, structured change proposal for spec-driven development, generating all planning artifacts (proposal, specs, design, tasks) in one guided workflow without touching project code. ## Core Features & Use Cases - One-step change scaffolding: Runs the openspec CLI to create a change directory and derives a kebab-case name from your description. - Dependency-aware artifact generation: Uses openspec status and openspec instructions to build every required artifact (proposal.md, specs, design.md, tasks.md) in the correct order. - Planning-only guardrails: Strictly limits the workflow to planning artifacts and defers implementation to a separate apply workflow. - Use Case: Describe "add user authentication" and receive a complete proposal with delta specs, design decisions, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change for adding user authentication using the openspec-propose skill.

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, and the workflow runs `openspec new change` to scaffold the change, then generates every required artifact in dependency order using `openspec status` and `openspec instructions`.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it creates proposal.md (what and why), specs/<capability>/spec.md (a delta of required behavior), 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 presenting the artifacts. Implementation requires a separate explicit request that starts the apply workflow, such as openspec-apply-change.

Can I use a custom schema or registered store with openspec?▼

Yes. Explicitly request a schema by name to pass `--schema`, or name a registered store so the workflow discovers it with `openspec store list --json` and appends `--store <id>` to subsequent commands.

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.