Files
agent-skills/evals/cases/planning-and-task-breakdown.json
T
Addy Osmani 194b2099c6 feat(evals): harden Tier 3 and make negatives pairwise routing tests
Per review from @federicobartoli and @nucliweb on #342:

Tier 3 (behavioral):
- Grade the execution trace, not the final output: executor runs with
  --output-format stream-json --verbose so the grader judges tool calls
  and file edits rather than the model's self-reporting.
- Run each eval in a throwaway workspace; files[] fixtures materialize
  from evals/fixtures/ so evals can operate on real code.
- Node-level timeouts on executor and grader calls; grader output parsed
  and shape-validated before writing (raw saved on failure); the trace is
  fenced as untrusted data in the grader prompt.
- All 24 behavioral evals flagged trust_level: "provisional" until they
  gain fixtures; the runner surfaces this and exits nonzero on failed
  expectations.

Tier 2 (deterministic):
- Negative triggers accept an "owner" skill that must outrank this one,
  turning them into pairwise routing tests that cannot pass vacuously;
  37 of 48 negatives now declare owners (the rest are tracked in #351).
- Warn when a case file is below the documented minimums (3 positive /
  2 negative / 1 behavioral); promotion to error tracked in #352.
- Stemmer: cluster trailing y/i ("simplify"/"simplifies").

Baseline holds: 120 checks, 0 errors, 85% trigger rank-1 rate.
2026-07-06 11:36:29 -07:00

43 lines
1.2 KiB
JSON

{
"skill_name": "planning-and-task-breakdown",
"trigger": {
"positive": [
{
"prompt": "Break this spec into small verifiable tasks with acceptance criteria",
"top_k": 3
},
{
"prompt": "Turn the PRD into an ordered task list we can execute",
"top_k": 3
},
{
"prompt": "Plan the work into implementable chunks before we start coding",
"top_k": 3
}
],
"negative": [
{
"prompt": "Debug the crash on startup",
"owner": "debugging-and-error-recovery"
},
{
"prompt": "Encode the output so it is safe against XSS"
}
]
},
"evals": [
{
"id": 1,
"prompt": "Break the attached notifications spec into an executable plan.",
"expected_output": "Ordered tasks in tasks/plan.md, each small, verifiable, with acceptance criteria and dependencies",
"expectations": [
"Every task has acceptance criteria",
"Tasks are ordered by dependency",
"Tasks are vertical slices rather than horizontal layers",
"No implementation code is written during planning"
],
"trust_level": "provisional"
}
]
}