openspec-propose

Generate proposal.md, design.md, and tasks.md for a new change.

208|148|Updated Oct 27, 2021
One-click install
npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-propose-elastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-propose-elastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes a change and generates all required artifacts (proposal.md, design.md, tasks.md) in a single step to accelerate planning and handoff.

Core Features & Use Cases

  • Single-step proposal generation for new changes
  • Artifacts included: proposal.md (what & why), design.md (how), tasks.md (implementation steps)
  • Ready-to-handoff workflow via /opsx:apply when artifacts are complete

Quick Start

Describe the change you want to build and I will generate a complete proposal with design, specs, and tasks.

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 complete change proposal in one step, describe your intended change to automatically produce proposal.md, design.md, and tasks.md artifacts with ready-to-implement guidance.

What is included in the artifacts when proposing a new change?

The proposal artifacts include proposal.md for the what and why, design.md for the how, and tasks.md for implementation steps, providing a complete package for rapid ideation and handoff.

Do I need the openspec CLI to generate proposal, design, and tasks files?

Yes, generating proposal.md, design.md, and tasks.md artifacts requires the openspec CLI to read your input and produce the structured change proposal files automatically.

What's the best way to automate product change ideation and implementation planning?

Automating product change ideation is best handled by generating structured artifacts in a single step, yielding a proposal, design specifications, and a task list for clear implementation planning.

Can I use this for rapid product team handoff with ready-to-implement tasks?

Yes, product teams can use the generated tasks.md file for rapid handoff, applying the ready-to-implement guidance once the proposal, design, and tasks artifacts are complete.

Are there limitations when generating design specifications and task lists for new changes?

Limitations include relying entirely on user input quality to generate the design specifications and task lists, meaning vague descriptions will produce less actionable implementation guidance.