openspec-propose

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

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/paradox123/shared-ai-docs --skill openspec-propose-paradox123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/paradox123/shared-ai-docs/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill openspec-propose-paradox123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes a new change by generating all required artifacts (proposal.md, design.md, tasks.md) in one step, saving time and aligning stakeholders early.

Core Features & Use Cases

  • End-to-end proposal generation: Creates a complete change package from a user description.
  • Consistent artifact outputs: Produces proposal, design, and tasks documents ready for review and implementation.
  • Deterministic workflow: Integrates with the openspec CLI to derive a kebab-case name and manage artifact dependencies in a repeatable way.

Quick Start

Describe the change you want to build, and I will generate a complete proposal package.

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 change proposal with design and tasks in one step?

To generate a change proposal in one step, provide a description of your intended change. The automation creates a complete package containing proposal.md, design.md, and tasks.md artifacts for immediate review.

What is included in an end-to-end project change proposal package?

An end-to-end change proposal package includes three structured artifacts: proposal.md, design.md, and tasks.md. These documents align stakeholders across project management, engineering, and task planning early in the development lifecycle.

How do I ensure consistent naming and repeatable artifact generation for change proposals?

To ensure repeatable artifact generation, the workflow integrates with the openspec CLI. It applies a deterministic build order and derives a kebab-case name to manage proposal, design, and task document dependencies consistently.

Do I need the openspec CLI to automate change proposal artifacts?

Using the openspec CLI is required to automate the deterministic build order for change proposals. It manages the artifact dependencies and derives the kebab-case naming convention to ensure repeatable, structured outputs.

When should I use automated proposal generation for development projects?

Use automated proposal generation when your development projects require quick, structured change proposals to accelerate implementation. It is designed to align design, engineering, and task planning across stakeholders efficiently.