openspec-propose

Generate proposal.md, design.md, and tasks.md for OpenSpec changes.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill openspec-propose-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/openspec-propose
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill openspec-propose-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting change proposals and project artifacts is slow and error-prone. This skill automates the end-to-end process by generating a complete proposal and associated design and task artifacts in one step.

Core Features & Use Cases

  • Generates a cohesive change proposal by producing proposal.md (what & why), design.md (how), and tasks.md (implementation steps).
  • Integrates with the OpenSpec workflow: reads the canonical slice at docs/openspec-slice.md, respects gate constraints, and supports ad-hoc changes with --no-slice and batch mode.
  • Produces ready-to-implement artifacts that can be reviewed and then applied via /opsx:apply for rapid execution in an engineering project.

Quick Start

Call the openspec CLI to create a new change and 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 auto-generate change proposal artifacts for software engineering projects?

Auto-generating change proposal artifacts is done by producing proposal.md, design.md, and tasks.md simultaneously in a single step. This enforces artifact sequencing, dependency handling, and adherence to the OpenSpec template.

What is the OpenSpec workflow and how does it handle change management?

The OpenSpec workflow handles change management by reading the canonical slice at docs/openspec-slice.md and respecting gate constraints. It automates generating cohesive proposals and ready-to-implement project artifacts.

Can I create ad-hoc change proposals without using the canonical slice file?

Creating ad-hoc change proposals without the canonical slice file is supported using the --no-slice flag. Batch mode is also available to align multiple proposals with gate approvals when canonical slicing is not required.

How do I apply generated design and task artifacts after creating a proposal?

Applying generated design and task artifacts happens via /opsx:apply for rapid execution in an engineering project. The generated files are ready-to-implement and can be reviewed before this execution step.

Do I need dependencies installed to scaffold project artifacts with this workflow?

No dependencies are required to scaffold project artifacts with this workflow. The process operates independently to generate the required proposal, design, and tasks files while enforcing artifact sequencing and template adherence.

Why does manual drafting of project artifacts cause errors and how to fix it?

Manual drafting of project artifacts causes errors because it is slow and lacks enforced sequencing or dependency handling. Automating the end-to-end process fixes this by generating a complete proposal and associated artifacts in one step.