openspec-propose

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

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/pablof7z/pod0 --skill openspec-propose-pablof7z
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/pablof7z/pod0/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/pablof7z/pod0 --skill openspec-propose-pablof7z

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. ## Core Features & Use Cases - One-Step Proposal Generation: Creates a change directory and generates every required artifact (proposal.md, spec deltas, design.md, tasks.md) in dependency order using openspec new change, status, and instructions commands. - Schema-Aware Planning: Respects the configured default workflow schema or an explicitly requested one, and supports registered OpenSpec stores via --store flags. - Planning-Only Guardrails: Strictly limits the session to planning artifacts and never edits project code, handing off to a separate apply workflow for implementation. - Use Case: A developer says "add user authentication with OAuth". The Skill derives the kebab-case name add-user-auth, scaffolds the change, and produces the proposal, spec delta, design, and tasks files ready for review before any code is written. ## 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 the Skill derives a kebab-case change name, runs `openspec new change`, then generates every required artifact in dependency order. You review the artifacts before starting implementation.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it produces proposal.md (what and why), spec delta files under specs/<capability-path>/spec.md, 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 change after planning?▼

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

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

Yes. Explicitly naming a schema adds `--schema <name>` to the change creation command, and selecting a registered store appends `--store <id>` to all read and write commands. Without these, the configured default schema and nearest local openspec root are used.

What happens if a change with the same name already exists?▼

The Skill asks whether you want to continue the existing change or create a new one with a different name, rather than overwriting or failing silently.