openspec-propose

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

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-propose-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-propose
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-propose-miftah-fentaw

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 workflow through the OpenSpec CLI, producing all required artifacts in one step. ## Core Features & Use Cases - One-Step Change Proposals: Creates a change directory and generates every artifact the schema requires, including proposal.md, spec deltas, design.md, and tasks.md. - Dependency-Aware Artifact Generation: Uses openspec status and openspec instructions to build artifacts in the correct dependency order, reading completed artifacts for context. - Store and Schema Support: Works with registered OpenSpec stores via --store flags and supports explicitly requested workflow schemas. - Use Case: Describe a feature like "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 adding user authentication and it will generate the full OpenSpec proposal with specs, design, and tasks.

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 every required artifact such as proposal.md, specs, design.md, and tasks.md in dependency order.

What artifacts does an OpenSpec proposal include?▼

With the default spec-driven schema it includes proposal.md describing what and why, spec deltas under specs/<capability-path>/spec.md, design.md describing how, and tasks.md listing implementation steps.

Does openspec-propose implement the code after planning?▼

No. The workflow creates planning artifacts only and explicitly stops after presenting them. Implementation requires a separate user request that starts the apply workflow, such as running /opsx-apply.

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 commands that read or write specs and changes for the rest of the session.

What happens if there is no OpenSpec root in the project?▼

The workflow runs openspec context --json first. If it reports no_openspec_root, it stops without creating files and offers openspec init, waiting for the user to request initialization before continuing.