openspec-propose

Generate proposal, design, and task artifacts from a user description.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/cogidoo/sunchaser --skill openspec-propose-cogidoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/cogidoo/sunchaser/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/cogidoo/sunchaser --skill openspec-propose-cogidoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propose new changes and generate all artifacts in one step to accelerate planning and alignment between product and engineering.

Core Features & Use Cases

  • Generate a complete proposal with design, specs, and tasks from a user description.
  • Scaffold artifacts at openspec/changes/<name> and provide a clear status workflow.
  • Reuse or adapt artifacts with a seamless transition to implementation using /opsx-apply.

Quick Start

Describe the change you want to build, and I will generate a complete proposal with design, specs, 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 generate a complete change proposal with design and tasks in one step?

To generate a change proposal, describe the product development initiative and the skill outputs proposal, design, and task artifacts automatically. It scaffolds these files at openspec/changes/<name> to accelerate planning and engineering alignment.

What is an openspec change proposal and when do I need to create one?

An openspec change proposal is an end-to-end planning artifact covering design, specs, and tasks for a feature. You need one when rapid product development alignment and structured change management are required before implementation begins.

How do I track dependencies and readiness when planning product development changes?

Dependency tracking and readiness sequencing are handled automatically during artifact generation. The skill applies openspec CLI workflow constraints to produce a ready-to-apply sequence, ensuring all task dependencies are mapped before implementation.

Can I use this for complex feature planning or is it limited to small scope changes?

Complex feature planning is fully supported alongside small scope changes. The automated proposal generation scales from minor adjustments to complex engineering initiatives, generating appropriate design specs and task artifacts for any scope.

What's the best way to transition from change proposal artifacts to actual implementation?

Transition to implementation by using the /opsx-apply command after artifacts are generated. This provides a seamless workflow from the scaffolded openspec/changes/<name> directory directly into the engineering execution phase.

Does openspec workflow automation require any specific environment setup before proposing changes?

No specific environment setup is required beyond the openspec CLI workflow context. You simply provide a user description of the desired change, and the automation handles artifact generation, dependency tracking, and readiness sequencing internally.