openspec-propose

Generate proposal.md, design.md, and tasks.md artifacts in one step.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill openspec-propose-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/quaid-app/quaid/tree/main/.claude/skills/openspec-propose
Command: npx skills add https://github.com/quaid-app/quaid --skill openspec-propose-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes a new change and generates all artifacts (proposal.md, design.md, and tasks.md) in a single step, reducing back-and-forth and speeding up project scoping.

Core Features & Use Cases

  • Generates proposal, design, and task artifacts from a concise user description.
  • Determines a kebab-case change name and a structured task breakdown ready for implementation.
  • Integrates with the openspec CLI workflow to accelerate project scoping.

Quick Start

Provide a description of the change and run the openspec propose command to generate all artifacts in one step.

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 complete change proposal, design, and task breakdown in one step, provide a concise change description and run the openspec propose command to output proposal.md, design.md, and tasks.md simultaneously.

What artifacts are produced when scoping a change with openspec?

Scoping a change with openspec produces three structured artifacts: proposal.md, design.md, and tasks.md, which together fully document the change scope and implementation plan.

Does openspec-propose require the openspec CLI to generate proposal artifacts?

Yes, openspec-propose depends on the openspec CLI and its artifact templates to produce the structured proposal, design, and task outputs required for openspec-driven workflows.

What is the best way to speed up project scoping for openspec-driven workflows?

The best way to speed up project scoping is using the openspec propose command to generate proposal, design, and task artifacts from a concise description, reducing back-and-forth and accelerating end-to-end change scoping.

Can I determine a kebab-case change name and task breakdown automatically?

Yes, providing a concise change description to openspec-propose automatically determines a kebab-case change name and generates a structured task breakdown ready for implementation.