openspec-propose

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-propose-neuthos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/neuthos/ldx-monorepo/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-propose-neuthos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing specs, design documents, and task lists by hand. This Skill automates that entire planning phase using 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 via the openspec CLI. - Schema and Store Awareness: Supports custom workflow schemas and registered OpenSpec stores, resolving the correct planning root automatically. - Planning-Only Guardrails: Strictly limits the workflow to planning artifacts, never editing project code or starting implementation. - Use Case: Describe "add user authentication" and receive a complete, validated change proposal with spec deltas, design decisions, and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change for adding user authentication using the openspec-propose workflow.

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?▼

Provide a change name in kebab-case or describe what you want to build. The workflow runs openspec new change, then generates each required artifact in dependency order using openspec instructions until the full required set exists.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it creates proposal.md, spec deltas under specs/<capability-path>/spec.md, design.md, and tasks.md. The exact set is determined by the schema and the transitive dependencies reported by openspec status.

Does openspec-propose implement the change it plans?▼

No. The workflow is strictly planning-only and never edits project code. After artifacts are presented, implementation requires a separate explicit request that starts the apply workflow.

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

Yes. Request a schema by name to pass --schema, or name a registered store to scope commands with --store <id>. The store flag stays sticky for all subsequent spec and change commands in 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 before proceeding, avoiding accidental overwrites or duplicate change directories.