openspec-propose

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes and generates all required specification and implementation artifacts from a brief user request so that ideas become implementation-ready changes without manual scaffolding and coordination.

Core Features & Use Cases

  • End-to-end artifact creation: Scaffolds a change directory and produces proposal.md, design.md, and tasks.md according to openspec templates.
  • Dependency-aware workflow: Queries openspec status and instructions, respects artifact dependency order, and iterates until apply-ready.
  • Interactive clarification & verification: Asks targeted questions when input is unclear, verifies files after writing, and reports progress for implementation handoff.

Quick Start

Propose a new change named add-user-auth and generate the proposal, design, and tasks in one pass.

Frequently Asked Questions about openspec-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate implementation-ready artifacts from a brief software change request?

Generating implementation-ready artifacts involves scaffolding a change directory and sequentially creating proposal.md, design.md, and tasks.md from a brief request. The workflow queries CLI status, respects artifact dependency order, and iterates until all files are apply-ready.

What is the correct dependency order for creating openspec change proposals?

The dependency order for openspec change proposals requires querying the CLI instructions endpoint first. It scaffolds the change directory, then sequentially generates the proposal, design, and tasks artifacts according to provided templates to ensure proper file verification.

Can I use the openspec CLI to scaffold a complete change directory in one step?

Yes, you can use the openspec CLI to scaffold a complete change directory in one step. It interacts with status and instructions endpoints to produce the proposal, design, and tasks markdown files end-to-end from a brief named request.

Does the openspec proposal workflow request user clarification for vague requests?

Yes, the openspec proposal workflow requests user clarification for vague requests. It asks targeted questions when input is unclear, verifies files after writing them, and reports progress to ensure the generated artifacts are implementation-ready.

What is the best way to automate software specification and task generation?

Automating software specification and task generation is best achieved by applying a dependency-aware workflow to a brief request. This scaffolds the change directory and iteratively creates proposal, design, and tasks artifacts while interacting with CLI status endpoints.

Why does the openspec artifact generation workflow query CLI status and instructions?

The openspec artifact generation workflow queries CLI status and instructions to respect artifact dependency order. This ensures the sequential creation of proposal, design, and tasks files follows templates correctly and produces apply-ready changes without manual coordination.