openspec-proposal-creation

Generate change IDs and scaffold proposal.md, tasks.md, and spec-delta.md files.

9|4|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/forztf/open-skilled-sdd --skill openspec-proposal-creation-forztf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-proposal-creation
Source: https://github.com/forztf/open-skilled-sdd/tree/main/skills/openspec-proposal-creation
Command: npx skills add https://github.com/forztf/open-skilled-sdd --skill openspec-proposal-creation-forztf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting and maintaining formal specification proposals and deltas to guide feature work, reduce ambiguity, and prevent scope creep across teams.

Core Features & Use Cases

  • Generate change IDs and scaffold proposal.md, tasks.md, and spec-delta.md for planned changes.
  • Provide templates, validation hooks, and example delta formats to ensure consistent proposals.
  • Use cases include planning new capabilities, planning breaking changes, and architecture updates.

Quick Start

Run openspec-proposal-creation to scaffold a new change proposal with proposal.md, tasks.md, and spec-delta.md.

Frequently Asked Questions about openspec-proposal-creation

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

FAQPage Schema
How do I create structured spec proposals for feature changes?

Use the openspec-proposal-creation Skill to scaffold a proposal.md, tasks.md, and spec-delta.md trio. This enforces structured outputs and reduces ambiguity across teams planning new capabilities or breaking changes.

What is a spec-delta and when do I need it for architecture updates?

A spec-delta represents formal changes to existing specifications during architecture updates. You need it when planning migrations, API changes, or updating existing behavior to prevent scope creep across codebases.

Does this spec-driven scaffolding tool provide templates for change proposals?

Yes, this spec-driven scaffolding tool provides templates, validation hooks, and example delta formats. These components ensure consistent change proposals for both breaking changes and standard feature work.

What's the best way to manage formal specification deltas across codebases?

The best way to manage formal specification deltas is generating a change ID and using a structured trio of proposal, tasks, and spec-delta files. Built-in validation ensures consistent proposals across codebases.

Can I use EARS format for spec-deltas when planning deprecations?

Yes, you can use EARS format for spec-deltas when planning deprecations. The Skill supports EARS format to enforce structured outputs and guide formal specification proposals for removing features.