openspec-proposal

/openspec-proposal — Creating a change proposal

Guardrails

• Minimal implementations — add complexity only when requested
• Strictly within the requested outcome
• Read openspec/AGENTS.md for OpenSpec conventions
• Identify ambiguities and ask clarifying questions BEFORE editing files
• Do NOT write code at the proposal stage. Only documents (proposal.md, tasks.md, design.md, spec deltas)

Steps

1. Read openspec/project.md, check openspec/changes/ и openspec/specs/, study related code via Grep/Glob
2. Choose a unique change-id (verb-noun) and create a scaffold in openspec/changes/<id>/:
   • proposal.md — what, why, impact
   • tasks.md — an ordered task checklist
   • design.md — architectural decisions (if needed)
3. Map the change to specific capabilities, break it down into spec deltas
4. Draft spec deltas в changes/<id>/specs/<capability>/spec.md:
   • Use ## ADDED|MODIFIED|REMOVED Requirements
   • At least one #### Scenario: per requirement
5. Draft tasks.md — an ordered list of verifiable tasks
6. Validate via openspec validate <id> --strict (if CLI is available) or manual verification

Reference

• Search for existing requirements: Grep "Requirement:|Scenario:" openspec/specs/
• Study the codebase via Grep/Glob for alignment with the current implementation