openspec-propose

Create Openspec change proposals with proposal, design, and task artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting a new change by turning a user’s idea into a complete, structured proposal with the artifacts needed to move from concept to implementation.

Core Features & Use Cases

  • One-step change planning: Creates a new change and generates proposal, design, and task artifacts in a single workflow.
  • Dependency-aware orchestration: Checks artifact readiness and creates required outputs in the correct order.
  • Interactive clarification: Prompts for more detail when the requested change is too vague to plan safely.
  • Use case: A product or engineering lead can describe a feature or fix and receive an implementation-ready change package without manually assembling each document.

Quick Start

Use the openspec-propose skill to create a complete change proposal for adding user authentication.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I create implementation-ready plans from feature requests quickly?

The openspec-propose workflow generates a complete change package containing proposal, design, and task artifacts for feature requests. It applies dependency-aware orchestration to ensure outputs are created in the correct sequential order.

Do I need the openspec CLI to generate change proposals?

Yes, the openspec CLI is required to generate change proposals. The workflow depends on the CLI to orchestrate the sequential creation of proposal, design, and task artifacts and to perform dependency-aware status checks.

What happens if my change proposal request is too vague to plan?

If a change proposal request is too vague to plan safely, the workflow utilizes interactive clarification. It will prompt you to provide more detail so it can accurately generate the required implementation artifacts.

How does dependency-aware orchestration work for specification tasks?

Dependency-aware orchestration for specification tasks checks artifact readiness and creates required outputs in the correct order. This ensures that design and task artifacts are only generated once the proposal dependencies are met.

Can I use this for both bug fixes and new feature enhancements?

Yes, you can use this structured change proposal workflow for both bug fixes and new feature enhancements. It applies interactive clarification and sequential artifact generation to any implementation idea needing a structured plan.