openspec-proposal

To create formal specification proposals for architecture changes, you formalize the requested update into OpenSpec proposal documents. This generates proposal.md, tasks.md, and design.md files to ensure formal traceability and cross-cutting alignment.

Tracking cross-cutting updates with formal traceability involves scaffolding a dedicated change folder with proposal, task, and design documents. This approach aligns spec deltas to specific capabilities for safe team coordination and outcome verification.

Mapping requirement deltas to existing OpenSpec capabilities is done by reading existing project specifications and generating scenario-based requirements. This breaks the requested change into capability-aligned spec deltas for strict validation.

Yes, OpenSpec validates strict rules for scenario-based requirements by applying manual checks or strict validation commands. This ensures the generated proposal, tasks, and design notes satisfy guardrails and verify outcomes correctly.

You need an OpenSpec proposal for task planning when coordinating architectural updates that require verifiable outcomes. It transforms vague change ideas into a formal, ordered checklist of verification-ready tasks to prevent team debate.

No, using openspec-proposal requires existing project specifications because it reads openspec/project.md and existing change specs. It selects a unique change-id based on this context to generate valid proposal deltas.