{
  "skill": "wave-coordination",
  "note": "Trigger-routing suite. expect=trigger: the skill should fire on the prompt in a fresh session. expect=no-trigger: a near-miss owned elsewhere (owner named per case). Cases derived from evals/routing-corpus.json's phrases array plus the SKILL.md description's own trigger/NOT-fence language.",
  "cases": [
    {
      "id": "t01",
      "prompt": "How do two parallel screen-composition-agent branches come back together?",
      "expect": "trigger"
    },
    {
      "id": "t02",
      "prompt": "Who merges each screen's branch in this wave, and when?",
      "expect": "trigger"
    },
    {
      "id": "t03",
      "prompt": "What's the conflict rule when two screens in the same wave both touch app/shared/tokens.css?",
      "expect": "trigger"
    },
    {
      "id": "t04",
      "prompt": "How many screens should one GEAR-2 wave hold before we gate it with surface-qa-agent?",
      "expect": "trigger"
    },
    {
      "id": "t05",
      "prompt": "What does the PR from a parallel wave actually look like \u2014 one PR or many?",
      "expect": "trigger"
    },
    {
      "id": "n01",
      "prompt": "Pick the on-disk shape for this new rollup app",
      "expect": "no-trigger",
      "owner": "project-scaffolding"
    },
    {
      "id": "n02",
      "prompt": "Build the markup for this dashboard screen from primitives",
      "expect": "no-trigger",
      "owner": "screen-composition"
    },
    {
      "id": "n03",
      "prompt": "Classify this vague brief into an Orientation Record",
      "expect": "no-trigger",
      "owner": "app-planning"
    }
  ]
}