openspec-propose

Generate proposal.md, design.md, and tasks.md artifacts from a concise description.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a complete change proposal by generating all required artifacts in one step (proposal.md, design.md, tasks.md), eliminating manual assembly and coordination.

Core Features & Use Cases

  • Generates a complete set of artifacts from a concise description or kebab-case name
  • Produces ready-to-review materials including proposal, design, and tasks ready for implementation
  • Use Case: When a product team needs a fast, end-to-end proposal to kickoff a change initiative

Quick Start

Provide a kebab-case change name or a description of what you want to build to generate all artifacts.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I generate design docs and a task list for a change proposal at once?

You can generate a complete change proposal by providing a concise description or kebab-case name, which automatically scaffolds proposal.md, design.md, and tasks.md in one step.

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

Automating change management artifact generation requires a deterministic workflow with templates and validation, ensuring a ready-to-apply scaffold from a concise description without manual assembly.

Can I create a proposal, design doc, and tasks from just a kebab-case name?

Yes, providing a kebab-case change name triggers an end-to-end artifact-generation workflow that produces ready-to-review proposal, design, and tasks materials for implementation.

Do I need any dependencies to scaffold product change proposals?

No dependencies are required to scaffold product change proposals; the process operates independently to generate the complete set of artifacts from your initial description.

When do I need a deterministic scaffolding process for change proposals?

You need deterministic scaffolding when a product team requires a fast, end-to-end proposal to kickoff a change initiative and wants to eliminate manual coordination.

Why does manual assembly slow down the creation of change proposals?

Manual assembly slows down change proposals because it requires coordinating and creating multiple separate artifacts, whereas an automated workflow generates all required materials instantly.