openspec-propose

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing proposals, specs, 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 the apply phase depends on, including proposal.md, specs deltas, design.md, and tasks.md. - Dependency-Aware Artifact Generation: Reads the artifact dependency graph from openspec status --json and creates artifacts in the correct order, re-reading dependencies from disk for context. - Store and Schema Support: Works with registered OpenSpec stores via --store flags and supports alternate workflow schemas when explicitly requested. - Use Case: Describe "add user authentication" and receive a complete planning package with a proposal, spec deltas, design decisions, and an implementation task list ready for review before any code is written. ## Quick Start Ask the assistant to propose a new change for adding user authentication and generate all planning artifacts.

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 from a feature idea?

Describe what you want to build in natural language, and the workflow derives a kebab-case change name, scaffolds the change with `openspec new change`, then generates every required artifact in dependency order. You review the artifacts before starting implementation.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it produces 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 reported by `openspec status --json`.

Does openspec-propose implement the code 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 /openspec-apply-change.

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

Yes. If you name a registered store, the workflow discovers it with `openspec store list --json` and passes `--store <id>` to subsequent commands. A custom schema is used only when you explicitly request one by name via `--schema`.

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 with a different name. It does not overwrite or merge into an existing change without confirmation.