openspec-propose

Name: openspec-propose
Availability: InStock
Author: Anthony

Generate an OpenSpec change proposal with design and task artifacts.

8|Updated Jan 19, 2026

Search Tags:#workflow #openspec #proposal #change-management #task-generation #design-spec

Ready to run

npx skills add https://github.com/OiAnthony/.agents --skill openspec-propose-oianthony

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/OiAnthony/.agents/tree/main/skills/openspec-propose
Command: npx skills add https://github.com/OiAnthony/.agents --skill openspec-propose-oianthony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting a structured OpenSpec change by turning a rough idea into a complete proposal package with the right artifacts prepared up front.

Core Features & Use Cases

One-step change setup: Creates a new OpenSpec change directory and scaffolds the initial planning workflow.
Artifact coordination: Builds proposal, design, and task artifacts in dependency order so implementation can begin cleanly.
Guided clarification: Asks for missing details when a change name or request is unclear, preventing incomplete proposals.
Use Case: A product engineer wants to add authentication support and needs a ready-to-implement change proposal without manually managing the OpenSpec process.

Quick Start

Ask the AI to create an OpenSpec change for your feature idea 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 create a complete OpenSpec change proposal with design and task artifacts in one step?▼

To create an OpenSpec change proposal, you need a structured change scaffold that generates the proposal, design, and task artifacts in the correct dependency sequence. This allows implementation to begin cleanly without manual artifact management.

What is the best way to scaffold an OpenSpec change directory for a new feature addition?▼

Scaffolding an OpenSpec change directory involves creating the initial planning workflow and coordinating artifact dependencies. This turns a rough idea into a ready-to-implement proposal package with the correct design and task files prepared up front.

Do I need the OpenSpec CLI to generate design specs and task artifacts for a change proposal?▼

Yes, you need OpenSpec CLI access to create the change, inspect artifact dependencies, and assemble the proposal, design, and tasks in the correct sequence. The CLI provides the necessary commands to scaffold the complete change package.

Can I use this workflow for fixing bugs and workflow updates, or is it only for new features?▼

You can use this change proposal workflow for product and engineering requests including feature additions, fixes, and workflow updates. Any structured change that requires a design spec and task generation before implementation is supported.

Why does my OpenSpec change proposal have missing details or incomplete artifacts?▼

Incomplete OpenSpec change proposals occur when the change name or request is unclear. The guided clarification process asks for missing details to prevent incomplete proposals, ensuring the design and task artifacts are properly generated.

How does artifact dependency coordination work when generating an OpenSpec proposal?▼

Artifact dependency coordination builds the proposal, design, and task artifacts in dependency order. This ensures that the OpenSpec change scaffold is assembled correctly so implementation can begin cleanly without missing structural components.