openspec-propose

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

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-propose-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-propose
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-propose-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, implementation-ready change proposal normally requires manually writing proposals, spec deltas, design documents, and task lists. This Skill automates that entire OpenSpec workflow in one step using the openspec CLI. ## Core Features & Use Cases - One-step change scaffolding: Creates the change directory and generates every required artifact (proposal.md, spec deltas, design.md, tasks.md) in dependency order. - Schema-driven artifact generation: Reads instructions, templates, and dependency graphs from openspec status and openspec instructions to produce artifacts that conform to your project's schema. - Multi-store support: Discovers registered OpenSpec stores and targets the correct one with --store flags. - Use Case: Describe "add user authentication" and receive a complete change folder with proposal, spec deltas, design, and an ordered task list ready for implementation via /opsx:apply. ## Quick Start Ask the assistant to propose a new OpenSpec change for the feature you want to build, describing it in a sentence.

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 from a feature idea?

Describe what you want to build in plain language. The skill derives a kebab-case change name, runs `openspec new change`, then generates every required artifact (proposal, specs, design, tasks) in dependency order using the openspec CLI.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it produces proposal.md (what and why), spec deltas under specs/<capability>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set is determined by your schema's dependency graph.

Does openspec-propose require the openspec CLI installed?

Yes, the skill requires the openspec CLI to be available, as stated in its compatibility metadata. All scaffolding, status checks, and instruction retrieval are executed through openspec commands.

Can I use OpenSpec proposals with multiple stores or repositories?

Yes. The skill runs `openspec store list --json` to discover registered stores and passes `--store <id>` to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

Why are some artifacts skipped during proposal generation?

Artifacts are skipped only when the change declares skip_specs in .openspec.yaml (status reports skipped) or when the artifact's own instruction marks it conditional, such as design.md. The skill never skips required artifacts by its own judgment.