openspec-propose

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-propose-ssttkkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/ssttkkl/finance-tracker/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-propose-ssttkkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, implementation-ready change proposal requires writing multiple coordinated documents (proposal, specs, design, tasks). This Skill automates that entire OpenSpec workflow in one step using the openspec CLI. ## Core Features & Use Cases - One-Step Change Scaffolding: Creates the change directory and generates every required artifact (proposal.md, specs, design.md, tasks.md) in dependency order. - Dependency-Aware Artifact Generation: Uses openspec status --json to resolve the transitive artifact set and builds each artifact from its schema template and instructions. - Store-Aware Operation: Supports named OpenSpec stores via --store <id> flags discovered through openspec store list --json. - Use Case: Describe "add user authentication" and receive a complete, validated change folder with delta specs, design decisions, and an ordered task list ready for implementation. ## Quick Start Ask the assistant to propose a new change for the feature you want to build, for example: propose a change to add session-based login 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?

Run `openspec new change <name>` to scaffold the change, then generate each artifact in dependency order using `openspec instructions <artifact-id> --change <name> --json`. This Skill automates that full loop from a plain-language description.

What artifacts does an OpenSpec proposal include?

The default spec-driven schema produces proposal.md (what and why), specs/<capability>/spec.md (delta requirements), design.md (how), and tasks.md (implementation steps). The exact set is resolved transitively from the apply requirements.

Does openspec-propose require the openspec CLI?

Yes, the Skill depends on the openspec CLI being installed and only invokes Bash commands scoped to `openspec:*`. Without the CLI, change scaffolding, status checks, and validation cannot run.

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

Yes, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on commands that read or write specs and changes. Without a store flag, commands act on the nearest local openspec/ root.

Why is an artifact skipped during change creation?

An artifact is skipped when the change declares skip_specs in .openspec.yaml (status reports skipped) or when its own instruction field marks it conditional, such as design.md. Skipped artifacts must not be created.