openspec-propose

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

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-propose-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/skills/openspec-propose
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-propose-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, implementation-ready change proposal normally requires writing multiple planning documents by hand. This Skill automates that by creating an OpenSpec change and generating all required artifacts (proposal, design, tasks) in one guided workflow. ## Core Features & Use Cases - One-Step Change Scaffolding: Runs the openspec CLI to create a change directory and derive a kebab-case name from a plain-language description. - Dependency-Aware Artifact Generation: Reads the artifact build order from openspec status and generates proposal.md, design.md, and tasks.md in the correct sequence, using each completed artifact as context for the next. - Schema-Guided Output: Follows per-artifact instructions, templates, and rules from the CLI so every document matches the expected structure. - Use Case: Describe "add OAuth login with Threads" and receive a complete change folder with a proposal explaining the why, a design covering the how, and a task list ready for implementation via /opsx:apply. ## Quick Start Ask the assistant to propose a new change for the feature you want to build, and it will scaffold the change and generate all planning artifacts.

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 in plain language, and the skill derives a kebab-case change name, runs `openspec new change`, then generates proposal.md, design.md, and tasks.md in dependency order using the openspec CLI.

What artifacts does an OpenSpec proposal include?

A typical change includes proposal.md covering what and why, design.md covering how, and tasks.md listing implementation steps. The exact set is determined by the schema's applyRequires field reported by `openspec status`.

Does openspec-propose require the openspec CLI installed?

Yes, the skill depends on the openspec CLI being available. It shells out to commands like `openspec new change`, `openspec status --json`, and `openspec instructions` to scaffold and generate artifacts.

What happens if a change with the same name already exists?

The skill asks whether you want to continue the existing change or create a new one with a different name, rather than overwriting or failing silently.

How do I implement the change after the proposal is generated?

Once all required artifacts show status done, run `/opsx:apply` or ask the assistant to implement. The generated tasks.md provides the ordered implementation steps.