openspec-propose

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

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-propose-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-propose-8007342

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 proposal.md, spec deltas, design.md, and tasks.md in dependency order. - Schema-Aware Artifact Building: Reads the configured OpenSpec workflow schema and follows each artifact's instructions, templates, and dependency graph. - Store and Context Support: Works with registered OpenSpec stores and project context from config.yaml to ground proposals in the actual codebase. - Use Case: Describe "add user authentication" and receive a complete, validated planning package ready for review before any code is written. ## Quick Start Ask the assistant to propose a new change, for example: create an OpenSpec proposal for adding user authentication to the app.

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 or provide a kebab-case change name. The workflow runs openspec new change, then generates every required artifact such as proposal.md, spec deltas, design.md, and tasks.md in dependency order.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it creates proposal.md describing what and why, spec deltas under specs/<capability-path>/spec.md, design.md covering how, and tasks.md listing implementation steps. The exact set depends on the configured workflow schema.

Does openspec-propose implement the code after planning?▼

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.

Can I use OpenSpec proposals with a registered store?▼

Yes. Run openspec store list --json to discover registered store ids, then the workflow appends --store <id> to all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

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

The workflow stops without creating files and offers to run openspec init. It waits for you to request initialization explicitly, then reruns the context check before continuing with proposal creation.