openspec-propose

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

6|1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/ilaziness/vexo --skill openspec-propose-ilaziness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/ilaziness/vexo/tree/main/.crush/skills/openspec-propose
Command: npx skills add https://github.com/ilaziness/vexo --skill openspec-propose-ilaziness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

It solves the problem of slow and fragmented change planning by producing a full set of implementation-ready artifacts (proposal, design, and tasks) from a single user request.

Core Features & Use Cases

  • One-step change proposal generation: Creates the change and generates multiple artifacts in the correct dependency order.
  • Artifact-driven workflow: Builds outputs based on schema instructions and existing completed artifacts.
  • Implementation handoff: Stops when the artifacts required for apply-ready are done, then tells you the next command to run.
  • Use Case: When you need to propose a feature or fix and want the proposal, design, and implementation task breakdown ready for execution without manual document assembly.

Quick Start

Tell the skill what you want to build or fix and provide a change name in kebab-case when possible, then let it generate all proposal artifacts and finish when everything needed for implementation is ready.

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 software change proposal with task breakdown in one step?

To generate a software change proposal, you describe the feature or fix and provide a kebab-case change name. This produces a complete implementation-ready package containing the proposal, design, and tasks in dependency order.

What is the best way to automate change management artifact generation for implementation handoff?

Automating change management artifact generation uses schema-driven instructions and templates to build required documents. It stops when the proposal, design, and tasks are apply-ready and outputs the next command to run for implementation.

Do I need openspec installed to draft implementation-ready proposals and task lists?

Yes, you need the openspec CLI installed as a dependency. The workflow relies on openspec to create the change, inspect artifact prerequisites via JSON status, and generate each document through schema-driven instructions.

Can I generate design documents and task breakdowns from a single feature request?

Yes, generating design documents and task breakdowns from a single feature request is the core workflow. You provide the requested software change, and the system outputs multiple artifacts in the correct dependency order for execution.

Why does the proposal generation workflow stop before applying the changes?

The proposal generation workflow stops when apply-ready artifacts are done to ensure proper implementation handoff. It completes the proposal, design, and task breakdown generation, then tells you the next command to run.