What problem does it solve? Coordinating a shared initiative across multiple teams is hard: proposals drift, repository impact is guessed instead of traced to a registry, and verification is claimed without evidence. This Skill guides an AI agent through planning and verifying a multi-team initiative in an OpenSpec Store, keeping requirements, repository impact, and evidence aligned. ## Core Features & Use Cases - Initiative Proposal: Defines the problem, expected outcome, boundaries, and team participation, with Repository Impact tied to exact code/specs IDs from the registry. - Delta Specs Authoring: Formulates shared requirements and observable scenarios while preserving standard OpenSpec headers and full requirement content, without imposing technical design. - Evidence-Based Verify: Matches requirements against evidence, distinguishes planning checks from acceptance of delivered results, and records "not verified" when evidence is missing. - Use Case: A platform lead needs three teams to deliver a shared API change. The agent creates a Change with the initiative schema, writes the Proposal and Delta Specs referencing the participant registry, then verifies the outcome against concrete evidence before reporting open questions. ## Quick Start Ask the agent to plan a new cross-team initiative in the OpenSpec Store using the initiative schema and then verify it against available evidence.
