openspec-propose

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

7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Printaga/PiLot --skill openspec-propose-printaga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Printaga/PiLot/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/Printaga/PiLot --skill openspec-propose-printaga

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 change creation: Derives a kebab-case change name from your description and scaffolds the change directory via openspec new change. - Dependency-aware artifact generation: Reads openspec status --json to determine the required artifact set (proposal, specs, design, tasks) and creates them in dependency order using schema-provided templates and instructions. - Store and schema support: Works with registered OpenSpec stores via --store flags and supports alternate workflow schemas when explicitly requested. - Use Case: Describe "add user authentication with OAuth" and receive a complete planning package—proposal.md, spec deltas, design.md, and tasks.md—ready for review before any code is written. ## Quick Start Ask the assistant to propose a new change for adding user authentication and have it generate the full OpenSpec planning 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 from a feature idea?▼

Describe what you want to build in plain language. The workflow derives a kebab-case change name, runs openspec new change to scaffold the directory, then generates every required artifact—proposal, specs, design, and tasks—in dependency order.

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 and the applyRequires dependency graph.

Does openspec-propose implement the code after planning?▼

No. The workflow is strictly limited to planning artifacts and explicitly stops after presenting them. Implementation requires a separate, explicit user request that starts the apply workflow.

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 all spec and change commands. The store selection stays sticky for the rest of the workflow.

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 failing silently.