openspec-plan

Generate OpenSpec change proposals with proposal.md, tasks.md, and specs from codebase analysis.

19|5|Updated Jan 26, 2026

Search Tags:#workflow #planning #documentation #code-analysis #openspec #spec-generation #change-proposals

Ready to run

npx skills add https://github.com/digital-stoic-org/agent-skills --skill openspec-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-plan
Source: https://github.com/digital-stoic-org/agent-skills/tree/main/dstoic/skills/openspec-plan
Command: npx skills add https://github.com/digital-stoic-org/agent-skills --skill openspec-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec Plan provides a structured workflow to turn codebase analysis into formal OpenSpec change proposals, reducing ambiguity and accelerating decision-making.

Core Features & Use Cases

Analysis + reasoning engine for change proposals that assumes a decision has been made (via brainstorming or direct request)
Workflow: Analyze → Reason → Generate to produce artifacts like proposal.md, rationale, and scope-defining content
Outputs include openspec/changes/{change-id}/proposal.md and related artifacts (tasks.md, specs) to guide implementation and testing

Quick Start

Ask the AI to generate a change proposal by analyzing the repository and then review the proposal before confirmation.

Frequently Asked Questions about openspec-plan

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

FAQPage Schema

How do I generate a formal change proposal from codebase analysis?▼

You can create structured change proposals by analyzing your repository to produce proposal.md, tasks.md, and specification files. The workflow assumes a decision has already been made and focuses on generating the rationale, scope, and implementation guidance for the proposed changes.

What is the best way to document the rationale and impact analysis for software changes?▼

The best way to document rationale and impact is by generating formal OpenSpec proposal artifacts. This Skill creates proposal.md and tasks.md files that capture the reasoning, scope, and implementation steps required for multi-file software modifications.

Can I use this to plan changes across multiple files in my codebase?▼

Yes, this Skill applies directly to software projects needing formalized change proposals across multiple files. It analyzes the codebase to generate scope-defining specs and tasks.md files that guide the implementation process.

How does the openspec-plan workflow generate specification artifacts?▼

The workflow generates specification artifacts by applying an Analyze, Reason, and Generate engine to your codebase. It outputs structured files including proposal.md and tasks.md to the openspec/changes directory to guide implementation and testing.

Do I need to brainstorm before generating an OpenSpec change proposal?▼

Yes, you need a prior decision via brainstorming or a direct request because this Skill assumes a decision has already been made. It focuses on analyzing the codebase and producing the formal proposal, rationale, and scope rather than initial ideation.