openspec-proposal-creation

Generate structured spec proposals with proposal.md, tasks.md, and spec-delta.md.

Updated Mar 31, 2026

Search Tags:#requirements #validation #scaffold #proposal #EARS #spec-delta

Ready to run

npx skills add https://github.com/Michael0520/milo.me --skill openspec-proposal-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-proposal-creation
Source: https://github.com/Michael0520/milo.me/tree/main/.claude/skills/openspec-proposal-creation
Command: npx skills add https://github.com/Michael0520/milo.me --skill openspec-proposal-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan and formalize feature changes by generating structured spec proposals with accompanying delta documentation.

Core Features & Use Cases

Generate a complete change proposal package including proposal.md, tasks.md, and spec-delta.md
Scaffold the change directory structure under spec/changes/{change-id}/ with clear naming and templates
Produce delta documents in ADDED/MODIFIED/REMOVED sections using the EARS format
Provide a ready-to-run Quick Start guide and validation guidance for end-to-end workflow

Quick Start

Describe a simple, repeatable workflow to create a new spec proposal:

Generate a unique change ID (e.g., add-feature-auth)
Create the directory structure: mkdir -p spec/changes/{change-id}/specs/{capability}
Populate proposal.md, tasks.md, and spec-delta.md using the included templates
Fill out the proposal and deltas following the guidelines, including at least one ADDED and one SCENARIO
Run the pre-submit validation steps to ensure structure and content correctness

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?▼

Spec delta documentation tracks changes using ADDED, MODIFIED, and REMOVED sections formatted with the EARS syntax. This structure ensures precise requirement validation and clear communication of breaking changes or architectural updates.

How do I scaffold a spec directory for requirements validation?▼

Use EARS-based delta formatting for spec proposals to ensure structured requirement validation. The EARS format organizes deltas into ADDED, MODIFIED, and REMOVED sections, requiring at least one ADDED entry and one SCENARIO for completeness.

What files do I need for an end-to-end spec proposal workflow?▼

For a spec proposal workflow, you must fill out proposal.md, tasks.md, and spec-delta.md following template guidelines. Include at least one ADDED section and one SCENARIO, then run pre-submit validation steps to ensure correctness.

Can I use spec-delta formatting for breaking changes and architectural updates?▼

Spec proposals accommodate breaking changes by generating structured delta documents categorized into ADDED, MODIFIED, and REMOVED sections. This ensures all architectural updates are formally tracked and validated before submission.