openspec-propose

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-propose-kevmendesdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/KevMendesDev/mercadinho-sao-francisco/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-propose-kevmendesdev

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: Derives a kebab-case change name from your description and scaffolds the change directory via openspec new change. - Dependency-Aware Artifact Generation: Uses openspec status and openspec instructions to build proposal.md, spec deltas, design.md, and tasks.md in the correct dependency order. - Planning-Only Guardrails: Strictly limits the workflow to planning artifacts and never edits project code, handing off to the apply workflow only on explicit request. - Use Case: Describe "add user authentication" and receive a complete change folder with proposal, spec deltas for the auth capability, technical design, and an ordered implementation task list ready for review. ## Quick Start Ask the assistant to propose a new OpenSpec change for the feature you want to build, describing it in one or two sentences.

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 plain language and this workflow derives a kebab-case change name, scaffolds the change with openspec new change, then generates proposal, specs, design, and tasks artifacts in dependency order.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it creates proposal.md describing what and why, spec delta files under specs/<capability-path>/, design.md covering how, and tasks.md listing implementation steps. The exact set is determined by the schema's dependency graph.

Does openspec-propose implement the code after planning?▼

No. The workflow is strictly planning-only and never edits project code. After artifacts are presented, you must explicitly start the separate apply workflow to begin implementation.

Can I use a different OpenSpec schema or a registered store?▼

Yes. Explicitly naming a schema adds the --schema flag, and naming a registered store triggers openspec store list to resolve its id, after which --store is appended to all spec-reading commands for the rest of the workflow.

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 artifacts silently.