What problem does it solve? When implementing an OpenSpec change across multiple repositories, an agent can start coding against the wrong repository or an unconfirmed scope. This Skill runs a mandatory preflight that verifies the repository assignment before any implementation begins, blocking execution when the scope is missing, mismatched, or unconfirmed. ## Core Features & Use Cases - Repository Scope Preflight: Fetches change context via MCP get_change_context with include_assignment: true and validates the nested assignment_scope against the accepted Repository Impact table. - Strict Consistency Checks: Compares Repository Impact with Tasks repository sections, rejects unknown repository-ids or capabilities, and treats any unmet condition as a BLOCKER that stops execution. - Controlled Handoff: Returns a structured apply_scope result (change, repository, impact, selected tasks, scope status) and delegates exactly once to the standard OpenSpec Apply entry point. - Use Case: A team implements a change spanning a specs repository and two code repositories; the agent runs this preflight to confirm which checkout it is assigned to before writing any code. ## Quick Start Ask the agent to run the apply-context preflight for change-id "add-user-auth" and confirm the assigned repository scope before starting implementation.
