{
  "schema_version": "spec-first.workflow-eval-fixtures.v1",
  "skill": "spec-brainstorm",
  "description": "Examples-as-context for spec-brainstorm trigger and near-neighbor routing boundaries.",
  "source_refs": [
    "skills/spec-brainstorm/SKILL.md",
    "skills/spec-ideate/SKILL.md",
    "skills/spec-prd/SKILL.md",
    "skills/spec-plan/SKILL.md",
    "skills/spec-work/SKILL.md",
    "skills/spec-debug/SKILL.md",
    "skills/spec-doc-review/SKILL.md",
    "skills/using-spec-first/SKILL.md"
  ],
  "source_ref_authority": "source",
  "coverage_tags": ["routing"],
  "cases": [
    {
      "id": "selected-feature-what-unclear",
      "input": "I want to add saved filters to our dashboard, but help me define who it is for and what counts as success before planning.",
      "coverage_tags": ["trigger"],
      "expected_outcome": "Stay in spec-brainstorm and clarify WHAT before planning.",
      "boundary_note": "A selected direction exists, but user behavior, scope, and success criteria still need clarification.",
      "extensions": {
        "expected_route": "spec-brainstorm"
      }
    },
    {
      "id": "problem-frame-needs-scope",
      "input": "Users keep losing track of review follow-ups; brainstorm the scope, non-goals, and success criteria before we write a plan.",
      "coverage_tags": ["trigger"],
      "expected_outcome": "Stay in spec-brainstorm and settle the problem frame, scope, and success criteria.",
      "boundary_note": "The user supplies a problem frame, not an open request for arbitrary ideas.",
      "extensions": {
        "expected_route": "spec-brainstorm"
      }
    },
    {
      "id": "chosen-idea-needs-boundaries",
      "input": "I picked the Slack digest idea. Help me decide the MVP behavior, non-goals, and handoff context.",
      "coverage_tags": ["trigger"],
      "expected_outcome": "Stay in spec-brainstorm and define the chosen idea enough for planning.",
      "boundary_note": "A candidate idea has already been chosen; the remaining work is WHAT clarification.",
      "extensions": {
        "expected_route": "spec-brainstorm"
      }
    },
    {
      "id": "open-idea-generation-routes-to-ideate",
      "input": "Give me ideas for what we should improve next.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-ideate instead of starting brainstorm.",
      "boundary_note": "Open-ended idea generation belongs to ideation before one direction is selected for brainstorm.",
      "forbidden_signals": ["writes a requirements doc", "enters Phase 1 dialogue"],
      "extensions": {
        "expected_route": "spec-ideate",
        "reason_code": "idea_generation"
      }
    },
    {
      "id": "brownfield-prd-routes-to-prd",
      "input": "Refine this brownfield PRD and validate if it is ready for planning: docs/brainstorms/payment-retry-requirements.md",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-prd for PRD refinement or validation.",
      "boundary_note": "Brownfield PRD authoring/refinement/validation is owned by the PRD workflow.",
      "forbidden_signals": ["restarts discovery dialogue", "creates a duplicate brainstorm artifact"],
      "extensions": {
        "expected_route": "spec-prd",
        "reason_code": "brownfield_prd"
      }
    },
    {
      "id": "clear-plan-request-routes-to-plan",
      "input": "The requirements are settled; create an implementation plan for docs/brainstorms/saved-filters-requirements.md.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-plan for HOW planning.",
      "boundary_note": "The user asks for an implementation plan from settled requirements, not WHAT discovery.",
      "forbidden_signals": ["asks product discovery questions", "writes a new requirements doc"],
      "extensions": {
        "expected_route": "spec-plan",
        "reason_code": "clear_plan_request"
      }
    },
    {
      "id": "single-doc-cleanup-stays-direct",
      "input": "Clean up this Markdown document's headings and bullets; do not change product scope.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Handle directly without entering spec-brainstorm.",
      "boundary_note": "Single-document cleanup or summarization is a direct task when no WHAT discovery is requested.",
      "forbidden_signals": ["routes to brainstorm", "creates a requirements artifact"],
      "extensions": {
        "expected_route": "direct",
        "reason_code": "direct_cleanup"
      }
    },
    {
      "id": "debug-request-routes-to-debug",
      "input": "This test fails with TypeError; reproduce it and find the root cause.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-debug.",
      "boundary_note": "Failure reproduction and root-cause work is diagnostic, not brainstorm discovery.",
      "forbidden_signals": ["asks product-scope questions before reproducing", "writes a requirements doc"],
      "extensions": {
        "expected_route": "spec-debug",
        "reason_code": "debug_request"
      }
    },
    {
      "id": "doc-review-routes-to-doc-review",
      "input": "Review this requirements document for gaps before planning.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-doc-review.",
      "boundary_note": "Independent critique of a requirements artifact is document review, not brainstorm.",
      "forbidden_signals": ["rewrites the document without review posture", "enters Phase 1 discovery"],
      "extensions": {
        "expected_route": "spec-doc-review",
        "reason_code": "doc_review"
      }
    },
    {
      "id": "execution-ready-routes-to-work",
      "input": "Implement the plan in docs/plans/2026-06-21-001-refactor-spec-brainstorm-boundary-plan.md and run the tests.",
      "coverage_tags": ["boundary"],
      "expected_outcome": "Route out to spec-work.",
      "boundary_note": "An existing plan or implementation-ready task belongs to execution.",
      "forbidden_signals": ["re-opens product discovery", "writes a new requirements doc"],
      "extensions": {
        "expected_route": "spec-work",
        "reason_code": "execution_ready"
      }
    }
  ]
}