Skip to content

feat: harden SKILL.md evidence structure into an explicit output format - #17

Merged
doulos76 merged 1 commit into
developfrom
feature/skillmd-format-hardening
Aug 21, 2026
Merged

feat: harden SKILL.md evidence structure into an explicit output format#17
doulos76 merged 1 commit into
developfrom
feature/skillmd-format-hardening

Conversation

@doulos76

Copy link
Copy Markdown
Owner

Summary

  • Both Haiku 4.5 and Sonnet 5 rubric runs found the with-skill condition frequently skipping the skill's own FACT/ASSUMPTION/UNKNOWN structure on scenario A (Stack Trace Anchoring), while unprimed baseline spontaneously produced it — a real, cross-tier instruction-following gap, not a one-off.
  • Converts the relevant prose guidance ("Establish What Is Known", "Classify the Conclusion") into an explicit, harder-to-skip output format: a required FACTS:/ASSUMPTIONS:/INFERENCES:/UNKNOWNS:/CONFLICTING EVIDENCE:/CLAIMS: block and a required Conclusion: VERIFIED | STRONGLY SUPPORTED | INFERRED line for any non-trivial diagnosis, with an explicit statement that a bare stack trace/crash report counts as non-trivial by default.
  • No other section of SKILL.md changed.

Test plan

  • Re-ran scenario A and B with-skill only (Sonnet 5, verbatim) against the new SKILL.md text and graded with the existing rubric: A went 8.0→19/20, B went 11.0→20/20 — both now above their baseline scores (16.5, 16.0).
  • Spot-checked scenario E (trivial edit) to confirm the tightened requirement doesn't add unwanted ceremony to genuinely trivial tasks — response stayed appropriately terse and explicitly reasoned that the FACTS block wasn't needed.
  • Full two-pass verbatim re-run of all 12 scenarios against v2 (both Sonnet 5 and Haiku 4.5) — recommended as a follow-up per tests/results/2026-08-21-skillmd-format-hardening.md, not done in this PR (this PR verifies the specific fix, not a full re-characterization).

Both the Haiku 4.5 and Sonnet 5 rubric runs found a consistent
instruction-following gap on scenario A (Stack Trace Anchoring) and,
more mildly, scenario B: with-skill responses often skipped the
skill's own FACT/ASSUMPTION/UNKNOWN labeling and confidence
classification when given a bare stack trace or crash report, while
unprimed baseline responses to the identical prompt frequently
produced that structure spontaneously. Both prior reports recommended
converting the prose guidance into an explicit, harder-to-skip output
format.

Rewrites "Establish What Is Known" and "Classify the Conclusion" to
require an exact FACTS/ASSUMPTIONS/INFERENCES/UNKNOWNS/CONFLICTING
EVIDENCE/CLAIMS block and an explicit "Conclusion: VERIFIED |
STRONGLY SUPPORTED | INFERRED" line for any non-trivial diagnosis,
and states explicitly that a bare stack trace or crash report is
non-trivial by default even when the eventual fix is small. Adds a
matching "Never" entry. No other section changed.

Verified against Sonnet 5: scenario A went from 8.0/20 to 19/20 and
scenario B from 11.0/20 to 20/20 on the same rubric (both now above
their baseline scores of 16.5 and 16.0). Spot-checked scenario E
(trivial edit) to confirm the tightened format doesn't add unwanted
ceremony to genuinely trivial tasks — it doesn't.
@doulos76 doulos76 added the enhancement New feature or request label Aug 21, 2026
@doulos76
doulos76 merged commit 6805386 into develop Aug 21, 2026
4 checks passed
@doulos76
doulos76 deleted the feature/skillmd-format-hardening branch August 21, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant