openspec-propose

Scaffold a complete OpenSpec change package with proposal, design, and tasks.

Updated Nov 29, 2022
One-click install
npx skills add https://github.com/circlebacknever/soundstage --skill openspec-propose-circlebacknever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/circlebacknever/soundstage/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/circlebacknever/soundstage --skill openspec-propose-circlebacknever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of turning a rough idea into a structured OpenSpec change, so you can move from concept to implementation-ready planning without assembling artifacts manually.

Core Features & Use Cases

  • One-step proposal generation: Creates the full change scaffold and supporting artifacts in a single workflow.
  • Implementation-ready planning: Produces proposal, design, and task documents that are ready for review and execution.
  • Best for scoped product or engineering changes: Use it when you need to quickly define a feature, fix, or enhancement before implementation begins.

Quick Start

Ask the skill to propose a change for your feature idea and generate the full OpenSpec package.

Frequently Asked Questions about openspec-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a software change proposal and design specification at the same time?

To generate a complete change proposal and design specification simultaneously, use an automated scaffolding workflow that creates proposal, design, and task documents in a single pass, avoiding manual artifact assembly.

What is the best way to turn a rough feature idea into implementation-ready planning artifacts?

The best way to turn a rough feature idea into implementation-ready planning artifacts is to scaffold a structured change package that outputs proposal, design, and task documents ready for immediate review and execution.

Do I need the OpenSpec CLI to create and resolve change package dependencies?

Yes, the OpenSpec CLI is required to create the change, resolve artifact dependencies, and generate apply-ready files with minimal back-and-forth when scaffolding a new proposal.

Can I use this approach to plan fixes and product enhancements before implementation begins?

Yes, you can use this scaffolding approach to plan fixes and product enhancements before implementation begins by translating user requests into structured proposal, design, and task documents.

Does generating a full change scaffold require multiple steps and manual document assembly?

No, generating a full change scaffold does not require manual document assembly; the workflow creates the complete package including proposal, design, and tasks in a single pass.