openspec-propose

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

Updated Mar 7, 2024
One-click install
npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-propose-girlguidingstaplehurst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/girlguidingstaplehurst/booking/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-propose-girlguidingstaplehurst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable implementation plan requires writing proposals, specs, 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 Proposals: Creates a change directory and generates every required artifact (proposal.md, specs, design.md, tasks.md) in dependency order. - Schema-Aware Planning: Uses the configured OpenSpec workflow schema and per-artifact instructions to structure each document correctly. - Planning-Only Boundary: Strictly limits itself to planning artifacts and never edits project code, handing off to a separate apply workflow for implementation. - Use Case: Describe a feature like "add user authentication" and receive a complete, validated change proposal with delta specs, design decisions, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change for the feature you want to build, describing what it should do.

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 the feature or fix you want to build, and the workflow derives a kebab-case change name, runs openspec new change, and generates all required artifacts in dependency order. You review the artifacts before starting implementation separately.

What artifacts does an OpenSpec proposal generate?▼

With the default spec-driven schema it generates proposal.md, delta spec files under specs/<capability-path>/, design.md, and tasks.md. The exact set is determined by the schema's dependency graph reported by openspec status.

Does openspec-propose implement the code changes too?▼

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

What happens if no OpenSpec root exists in my project?▼

The workflow runs openspec context --json first and stops if no root is found. It offers openspec init and waits for you to request initialization rather than creating anything automatically.

Can I use a different workflow schema for a proposal?▼

Yes, but only when you explicitly request a schema by name. The workflow then passes --schema <schema-name> to openspec new change; otherwise it uses the configured default schema.