openspec-propose

Generate proposal, design, and tasks artifacts for openspec changes.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/MiDouTech/myTapd --skill openspec-propose-midoutech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/MiDouTech/myTapd/tree/main/.cursor/skills/openspec-propose
Command: npx skills add https://github.com/MiDouTech/myTapd --skill openspec-propose-midoutech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many requests for product or engineering changes lack a complete, implementation-ready proposal that includes the why, the how, and the discrete tasks required for delivery. This Skill streamlines the creation of a scaffolded change with proposal, design, and task artifacts so teams can move from idea to implementation faster and with fewer handoffs.

Core Features & Use Cases

  • Create a new change scaffold using the openspec CLI and generate proposal.md, design.md, and tasks.md in the change directory.
  • Follow artifact dependencies and instructions, read completed dependency files for context, and iterate until apply-required artifacts are complete.
  • Use case: a product manager describes a feature request and receives a ready-to-implement change folder with specs and task breakdown for engineering.

Quick Start

Propose a change named add-user-auth with a short description of the feature so I can generate proposal.md, design.md, and tasks.md in openspec/changes/add-user-auth.

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 specs and tasks?

To generate a complete change proposal, you provide a feature name and description to create a scaffolded change directory containing proposal.md, design.md, and tasks.md. This process uses the openspec CLI to build implementation-ready artifacts in dependency order.

What is the best way to scaffold product change directories for engineering handoff?

Scaffolding product change directories is best handled by converting a high-level feature request into structured proposal, design, and task files. This approach reduces handoffs by giving engineering teams ready-to-implement artifact files within an organized openspec change folder.

Do I need the openspec CLI to create proposal, design, and task artifacts?

Yes, you need the openspec CLI installed to create proposal, design, and task artifacts. The Skill relies on openspec status and instructions commands to read dependencies, generate artifacts in the correct order, and prepare apply-ready tasks.

How does artifact dependency ordering work when scaffolding change proposals?

Artifact dependency ordering works by reading completed dependency files for context and following instructions to generate subsequent artifacts. This ensures proposal.md, design.md, and tasks.md are created sequentially until all apply-required artifacts are complete.

Can I use this approach to convert a high-level feature request into ready-to-implement tasks?

Yes, you can convert a high-level feature request into ready-to-implement tasks by running a propose command with a short description. The system scaffolds a change folder containing discrete task breakdowns alongside proposal and design specifications.

What limitations exist when generating change artifacts with openspec?

A key limitation is that artifact generation requires the openspec CLI environment to function. Additionally, the completeness of the generated proposal, design, and tasks depends entirely on the context provided in the initial high-level feature request description.