openspec-propose

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-propose-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-propose-jhonma82

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 artifact the apply phase depends on (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: Resolves registered OpenSpec stores and passes the correct --store flag so specs are read and written in the right repository. - Use Case: Describe "add user authentication" and receive a kebab-case change folder containing a proposal, spec deltas for the affected capabilities, a design document, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change, for example: create an OpenSpec proposal for adding user authentication to the API.

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 and the skill derives a kebab-case change name, runs openspec new change, then generates every required artifact in dependency order using openspec status and openspec instructions. You review the artifacts before any implementation starts.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it creates proposal.md, spec deltas under specs/<capability-path>/spec.md, design.md, and tasks.md. The exact set is determined by the schema's dependency graph, and conditional artifacts like design.md may be skipped when the instructions mark them optional.

Does this skill implement the change after creating the proposal?▼

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

Can I use OpenSpec proposals with a registered store instead of a local repo?▼

Yes. Run openspec store list --json to discover registered store ids, then the skill appends --store <id> to every command that reads or writes specs and changes. Without a store, commands act on the nearest local openspec/ root.

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 with a different name, rather than overwriting or duplicating work silently.