openspec-propose

Generate proposal.md, design.md, and tasks.md for a change proposal.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-propose-yager-42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-propose-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes a change and generates all required artifacts in a single step, enabling teams to capture a clear rationale, design, and implementation plan without multiple handoffs.

Core Features & Use Cases

  • Generates a complete change proposal including proposal.md (what & why), design.md (how), and tasks.md (implementation steps).
  • Keeps artifacts in sync with a single command flow and integrates with the openspec CLI for applying when ready.
  • Ideal for product managers and engineers who need a fast, end-to-end planning artifact to share with stakeholders.

Quick Start

Describe the desired change and run the tool to generate a complete proposal with design 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 complete change proposal in one step, you describe the desired change and run the openspec CLI. This produces proposal.md, design.md, and tasks.md simultaneously, capturing the rationale, design, and implementation plan without multiple handoffs.

What is included in an end-to-end change proposal for project planning?

An end-to-end change proposal includes three core artifacts: proposal.md for the what and why, design.md for the how, and tasks.md for the implementation steps. This ensures teams capture clear rationale, design, and plans together.

Do I need the openspec CLI to apply generated planning artifacts?

Yes, you need the openspec CLI to orchestrate the creation and apply the generated change management artifacts. It keeps the proposal, design, and tasks files in sync with a single command flow when you are ready to implement.

Can I use this approach to create planning artifacts for fast engineering handoffs?

Yes, this approach is ideal for product managers and engineers who need fast, end-to-end planning artifacts. It eliminates multiple handoffs by generating a complete proposal ready to share with stakeholders for immediate implementation.

What is the best way to keep proposal, design, and tasks documents in sync?

The best way to keep proposal, design, and tasks documents in sync is using a single command flow through the openspec CLI. This ensures the generated change management artifacts remain aligned and ready for application.

Why does generating change proposals individually create workflow bottlenecks?

Generating change proposals individually creates bottlenecks because it requires multiple handoffs to capture the rationale, design, and implementation plan separately. End-to-end artifact generation solves this by producing all three documents in one step.