openspec-propose

Convert change requests into proposal, design, and tasks artifacts via openspec CLI.

Updated Apr 20, 2026

Search Tags:#agent orchestration #spec generation #task planning #openspec #software planning #implementation readiness #change proposal

Ready to run

npx skills add https://github.com/thistleknot/skills --skill openspec-propose-thistleknot

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of turning a rough idea into a ready-to-implement change package by producing proposal, design, and task artifacts in a single guided flow.

Core Features & Use Cases

One-step change proposal generation: Creates proposal.md, design.md, and tasks.md for a new change so implementation can begin immediately.
Artifact orchestration and dependency ordering: Queries openspec status and instructions, then generates required artifacts in the correct order until apply-ready.
Light clarification when needed: Asks follow-up questions when the user’s intent or change context is unclear, then continues.

Quick Start

Describe what you want to build or fix, then ask the system to propose the change so it generates proposal, design, and tasks artifacts and tells you to run /opsx:apply.

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 software change proposal from a rough idea?▼

Software change proposal generation converts a rough change request into an implementation-ready package by creating proposal, design, and tasks artifacts in a single guided flow. It queries openspec status to orchestrate and order the required artifacts until the package is apply-ready.

What is the best way to plan software implementation tasks from partial requirements?▼

Planning software implementation tasks from partial requirements involves orchestrating artifact generation to produce an ordered set of specs and work items. The system asks light clarification questions when intent is unclear, then generates the necessary proposal, design, and tasks files.

Do I need to manually order spec artifacts when preparing a change package?▼

You do not need to manually order spec artifacts when preparing a change package. The generation process applies dependency ordering by querying openspec CLI status and per-artifact instructions, automatically writing outputs to the correct paths until the package is apply-ready.

How to create proposal, design, and tasks files for a new software feature in one step?▼

To create proposal, design, and tasks files for a new software feature in one step, describe what you want to build and ask the system to propose the change. It generates the three markdown artifacts and instructs you to run the apply command to begin implementation.

What happens if my change request lacks enough detail for spec generation?▼

If your change request lacks enough detail for spec generation, the system asks follow-up questions to clarify your intent and change context. Once clarified, it continues the guided flow to produce the proposal, design, and tasks artifacts.

Can I use openspec-propose for fast planning of an unordered set of work items?▼

Yes, you can use openspec-propose for fast planning from an idea or partial requirements to an ordered set of specs and work items. It is designed for scenarios where you need to quickly turn a rough concept into an implementation-ready change package.