openspec-propose

Generate proposal.md, design.md, and tasks.md via the openspec CLI.

6|1|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/rezics/rezics --skill openspec-propose-rezics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/rezics/rezics/tree/main/.cursor/skills/openspec-propose
Command: npx skills add https://github.com/rezics/rezics --skill openspec-propose-rezics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes a complete change with all artifacts generated in one step, eliminating manual, multi-tool drafting and reducing cycle time for project initiation.

Core Features & Use Cases

  • End-to-end change proposal: generates proposal.md, design.md, and tasks.md in a single workflow.
  • Change-name-driven scaffolding: accepts a user-provided description or kebab-case name to tailor artifacts.
  • Quick iteration: lets teams quickly validate scope and next steps before implementation.

Quick Start

Provide a change description or name to 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 task artifacts in one step?

Generate a complete change proposal with design and task artifacts in one step by providing a change description or kebab-case name to automatically scaffold proposal.md, design.md, and tasks.md in a single workflow.

What is the fastest way to automate scaffolding for new project specifications and tasks?

Automating scaffolding for new project specifications and tasks is fastest done through a single-step generation workflow that outputs proposal.md, design.md, and tasks.md, eliminating manual multi-tool drafting and reducing project initiation cycle time.

Can I use my own change name to generate proposal artifacts with openspec?

Yes, you can use your own change name to generate proposal artifacts with openspec by supplying a user-provided description or kebab-case name, which the system uses to tailor the generated proposal.md, design.md, and tasks.md files.

Does the openspec change proposal workflow require manual drafting of design documents?

No, the openspec change proposal workflow does not require manual drafting of design documents, as it automates the creation of design.md and tasks.md alongside the proposal.md file to provide an end-to-end proposal in one step.

What's the best way to quickly validate scope and next steps before implementation?

The best way to quickly validate scope and next steps before implementation is to generate a complete change proposal with all artifacts, allowing teams to iterate and review the proposal.md, design.md, and tasks.md files rapidly.

Are there limitations to end-to-end change proposal automation for task management?

Limitations of end-to-end change proposal automation for task management include relying on the openspec CLI for artifact generation and requiring a user-supplied change name to scaffold the proposal.md, design.md, and tasks.md files effectively.