openspec-propose

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

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-propose-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-propose
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-propose-phuchoang2603

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 without touching project code. ## Core Features & Use Cases - One-step change scaffolding: Creates a kebab-case change directory and generates every artifact the apply phase depends on (proposal.md, spec deltas, design.md, tasks.md) in dependency order. - Schema and store awareness: Supports custom workflow schemas and registered OpenSpec stores, resolving the correct planning root automatically via the openspec CLI. - Guardrailed planning boundary: Produces planning artifacts only and explicitly stops before implementation, keeping proposal and apply phases separate. - Use Case: Describe "add user authentication" and receive a complete, validated change folder with proposal, spec deltas, design notes, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new OpenSpec change for the feature you want to build, for example by describing the change and letting it run the openspec-propose workflow.

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 and the workflow derives a kebab-case change name, runs openspec new change, then generates every required artifact in dependency order using openspec status and openspec instructions. All planning files are produced in one pass.

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 is determined by the schema's dependency graph.

Does openspec-propose implement the change after planning?▼

No. The workflow is strictly limited to planning artifacts and stops once they are complete. Implementation requires a separate explicit request that starts the apply workflow, such as openspec-apply-change.

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

Yes. The workflow discovers registered stores with openspec store list --json and applies --store <id> to subsequent commands. A custom schema is used only when explicitly requested via --schema <schema-name>.

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 before proceeding, avoiding accidental overwrites of in-progress proposals.