openspec-change-proposal

Generate OpenSpec change proposals with tasks and delta specifications.

67|11|Updated Oct 28, 2025

Search Tags:#scaffold #tasks #openspec #proposal #delta #change

Ready to run

npx skills add https://github.com/bacoco/BMad-Skills --skill openspec-change-proposal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-change-proposal
Source: https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/openspec-change-proposal
Command: npx skills add https://github.com/bacoco/BMad-Skills --skill openspec-change-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill creates lightweight OpenSpec proposals for small changes, enabling quick alignment before implementation.

Core Features & Use Cases

Proposal creation for Level 0-1 changes.
Delta specs with added/modified/removed requirements.
Task scoping and lightweight planning.

Quick Start

Instruct Claude to scaffold a change workspace and draft the proposal and delta specs.

Frequently Asked Questions about openspec-change-proposal

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

FAQPage Schema

How do I create a change proposal for small software updates?▼

Create a change proposal by scaffolding a workspace that generates proposal.md, tasks.md, and delta specs automatically. This skill creates lightweight OpenSpec proposals for Level 0-1 changes—bug fixes, minor enhancements, or simple feature tweaks—with standardized templates that align teams before implementation begins.

What's included in a delta spec for code changes?▼

Delta specs document added, modified, and removed requirements for your change. This skill generates delta.md files that capture incremental shifts in your codebase, paired with proposal and task scaffolding, so stakeholders see exactly what's changing without verbose specification overhead.

When should I use lightweight change proposals instead of full specifications?▼

Use lightweight proposals for Level 0-1 changes—isolated bug fixes, config tweaks, or focused enhancements that don't reshape system architecture. This skill targets scenarios where quick alignment matters more than exhaustive planning, reducing proposal-writing friction while maintaining clarity.

Can I generate proposal and task scaffolding together?▼

Yes. This skill generates proposal.md, tasks.md, specs/spec-delta.md, and optional design.md in a single workspace scaffold. All files use standardized templates, so you get a complete, lightweight change proposal with task breakdown and delta specs ready to iterate on.

What's the difference between this approach and writing proposals manually?▼

Automated scaffolding eliminates template busy-work and ensures consistency across proposals. This skill generates structured change artifacts—proposals, deltas, and tasks—for small incremental changes, letting teams focus on decision-making rather than document formatting.