openspec-propose

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/pvtvv/climber-app --skill openspec-propose-pvtvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/pvtvv/climber-app/tree/main/.cursor/skills/openspec-propose
Command: npx skills add https://github.com/pvtvv/climber-app --skill openspec-propose-pvtvv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal 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 scaffolding: Creates a kebab-case change directory and generates every artifact (proposal.md, spec deltas, design.md, tasks.md) in dependency order. - Schema-aware artifact generation: Reads per-artifact instructions, templates, and dependency graphs from the OpenSpec CLI so output follows the project's configured workflow schema. - Store and multi-root support: Discovers registered OpenSpec stores and applies the correct --store flag across all CLI commands. - Use Case: A developer says "add user authentication" and receives a complete, validated planning package—proposal, spec delta, design, and 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 the change you want to build or provide a kebab-case name. The workflow runs openspec new change, then generates every required artifact—proposal, specs, design, and tasks—in dependency order using the CLI's instructions and templates.

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 workflow schema.

Does openspec-propose implement the code after planning?▼

No. The workflow is strictly limited to planning artifacts and never edits project code. After the artifacts are presented, implementation requires a separate explicit request that starts the apply workflow.

Can I use a different OpenSpec workflow schema?▼

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

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

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