openspec-propose

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

4|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-propose-jin1c-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Jin1c-3/obsidian-advanced-maps/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-propose-jin1c-3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing specs, design documents, and task lists by hand. This Skill automates that planning workflow through the OpenSpec CLI, producing all required artifacts in one guided pass. ## Core Features & Use Cases - One-step proposal generation: Creates the change directory and generates proposal.md, spec deltas, design.md, and tasks.md in dependency order. - Schema-aware artifact building: Reads the configured workflow schema and follows each artifact's instructions, template, and dependency graph via the openspec CLI. - Store and multi-root support: Works with registered OpenSpec stores and local openspec roots, keeping commands scoped with the correct --store flag. - Use Case: Describe "add user authentication" and receive a complete, validated change folder with specs, design rationale, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change named add-user-auth that adds login and session handling, and let it generate the full OpenSpec proposal 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?

Provide a kebab-case change name or describe what you want to build. The workflow runs openspec new change, then generates each required artifact (proposal, specs, design, tasks) in dependency order using openspec status and openspec instructions.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it creates proposal.md (what and why), spec delta files under specs/<capability-path>/, design.md (how), and tasks.md (implementation steps). The exact set depends on the configured schema and its dependency graph.

Does openspec-propose implement the code after planning?

No. The workflow is strictly planning-only: it creates the change artifacts and stops. Implementation requires a separate explicit request that starts the apply workflow, such as openspec-apply-change.

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

Yes. Run openspec store list --json to discover registered store ids, then the workflow appends --store <id> to commands that read or write 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 workflow asks whether you want to continue the existing change or create a new one with a different name, rather than overwriting or duplicating the existing change directory.