openspec-propose

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

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-propose-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-propose
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-propose-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, implementation-ready change proposal normally requires manually writing specs, design docs, and task lists. This Skill automates that entire process through the OpenSpec CLI, producing all required artifacts in one guided step. ## Core Features & Use Cases - One-Step Proposal Generation: Creates a change directory and generates proposal.md, spec deltas, design.md, and tasks.md in dependency order. - Schema-Driven Artifacts: Reads artifact instructions, templates, and dependency graphs from the OpenSpec CLI so every file follows the project's spec-driven schema. - Multi-Store Support: Discovers registered OpenSpec stores and targets the correct repository with the --store flag. - Use Case: Describe "add user authentication" and receive a complete change folder with a proposal, capability spec deltas, technical design, and an ordered task list ready for implementation via /opsx-apply. ## Quick Start Ask the assistant to propose a new change by describing what you want to build, for example requesting a proposal for adding user authentication to the project.

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 skill derives a kebab-case change name, runs openspec new change, then generates every required artifact in dependency order. When finished, run /opsx-apply to start implementation.

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>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set is determined by the schema's dependency graph.

Does openspec-propose require the OpenSpec CLI installed?▼

Yes, the skill shells out to the openspec CLI for all operations including new change, status, and instructions. Without the CLI installed and a resolved openspec root or registered store, the workflow cannot run.

Can I use OpenSpec proposals across multiple repositories or stores?▼

Yes, the skill runs openspec store list --json to discover registered stores and passes --store <id> to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

Why are some artifacts skipped during proposal generation?▼

Artifacts are skipped when the change declares skip_specs in .openspec.yaml, reported as status skipped, or when the artifact's own instruction marks it conditional, such as design.md. The skill never skips required artifacts by its own judgment.