Context Intelligence Evaluation Design

Phase 3 specialist skill for context-intelligence mode. Called by context-intelligence-tool-designer agent via self-delegation with context_depth="none", scoped to one concept at a time.

---

Scope

In scope:

• Derive success criteria from domain-concepts.md
• Design one evaluation scenario per concept
• Populate DTU profile templates including mandatory Gitea URL rewrite block

Out of scope:

• Investigating signals
• Classifying detection strategies
• Running evaluations

Note: The evaluation runner is amplifier-bundle-evaluation invoked inside a DTU built from this scenario.

---

Criteria Derivation Rule

Success criteria MUST come from the user-confirmed concept definition in domain-concepts.md — specifically the Agreed definition, Boundary conditions, Data availability, and Explicitly excludes fields. NEVER derive from implementation details.

What a detector returns is not the criterion; what correct detection looks like in plain terms from the user's domain perspective is the criterion.

If the definition is too vague to produce a testable criterion, return a structured gap entry rather than guessing.

---

Per-Concept Evaluation Scenario Format

Each scenario is ready for insertion into evaluation-scenarios.md:

## Scenario [N]: [Concept] — [description]

**Derived from:** [field reference in domain-concepts.md — Agreed definition / Boundary conditions / Data availability / Explicitly excludes]

**Success criterion:** [Plain-language statement of what correct detection looks like from the user's domain perspective. Not what the detector returns — what it means.]

**Failing scenario:** [Concrete example of a case where detection fails or produces a false positive, derived from Explicitly excludes or Boundary conditions.]

**DTU environment:** [Reference to DTU profile template produced by this skill for this concept.]

**Pass threshold:** [Quantitative or qualitative threshold — e.g., "detects in ≥8 of 10 representative sessions" or "no false positives on the Explicitly excludes examples".]

**Iteration question:** [The question this scenario answers. Used to route delta back through Phase 4. E.g., "Does the signal correctly distinguish X from Y as the user defined it?"]