requirement-gate-orchestration

Requirement gate orchestration standardizes Gate 1 intake, enforces readiness, and freezes the Requirement Context Package for Gate 2. It ensures consistent handoffs to requirement challengers while routing requirements with clear input ownership rules.

To orchestrate Gate 1 to Gate 2 handoffs, invoke the skill at Gate 1 to route requirements to the challenger, validate readiness, classify slice complexity, and freeze the Requirement Context Package for downstream PRD artifacts.

Yes, you can enforce input ownership rules during requirement gate progression. The orchestration process freezes Gate 1 contracts for Gate 2, ensuring a single source of truth and consistent context transfer.

The best way to handle open questions during requirement intake is through Product Owner decision gating. This mechanism manages open-question handling and enforces progression decisions before transferring context into Gate 2.

You should freeze the requirement context package during Gate 1 execution and readiness validation. Freezing the Gate 1 contracts preserves a single source of truth for progression decisions into Gate 2 and downstream PRD artifacts.

Yes, requirement gate orchestration includes slice complexity classification as part of gate progression enforcement. This classification occurs during Gate 1 readiness validation to ensure proper context transfer into the PRD phase.