openspec-propose

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

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-propose-hongwt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/hongwt/dsplm-monitor/tree/main/.pi/skills/openspec-propose
Command: npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-propose-hongwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal normally requires writing specs, design docs, 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: Queries the OpenSpec CLI for artifact dependencies and instructions, ensuring every artifact the implementation phase needs actually exists. - Store and Schema Support: Works with registered OpenSpec stores and custom workflow schemas when the default spec-driven schema does not fit. - Use Case: Describe "add user authentication" and receive a complete planning package with capability specs, technical design, 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 it in a sentence or two.

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 in plain language, and the workflow derives a kebab-case change name, scaffolds the change with openspec new change, then generates every required artifact in dependency order.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it produces 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 apply phase 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 request that starts the apply workflow.

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

Yes. Pass a schema name explicitly to use --schema, or name a registered store so commands run with --store <id>. 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 workflow asks whether you want to continue the existing change or create a new one, rather than overwriting or duplicating work silently.