feat(pr-workflow): add /mms-debug orchestrator - #98
Conversation
`pr-validate` is handed a claim and looks for the observation that would falsify it. Debugging starts from a symptom and has to generate the hypothesis first, which is where the expensive failure lives: the theory is yours, nobody else is positioned to challenge it, and confirmation is cheap. Routes the symptom to the engine that owns its defect class rather than reimplementing any investigation, so both orchestrators share one set of engines. Carries `pr-validate`'s trust gates, which bind harder here — a weak instrument in review yields a claim someone challenges, in debugging it yields a theory nobody checks.
MajorLift
changed the title
/mms-debug orchestrator
Context budgetWhat this PR costs an agent, measured from an install rather than read from the diff. Three tiers, and only the first is unavoidable.
Frontmatter is the only tier paid unconditionally — every agent loads it on every run once the skill is installed, used or not, because it is what the agent reads to decide relevance. The 28 skills across the eleven open skill PRs sit at a median of ~1,716 tokens selected and ~1,860 with references followed. All are within the 1,536-character description budget. Selected is paid only when the agent picks the skill. + refs & knowledge is the ceiling if every bundled reference is then read; it is a worst case, not an expectation. Method
These figures are pinned to the commit above and drift on every push; #96 tracks automating them. |
1 participant
Summary
debug, the symptom-first sibling ofevidence.evidenceis handed a claim and looks for the observation that would falsify it;debugis handed a symptom and has to generate the hypothesis before anything can falsify it.memory-leak,race-condition-repro,react-render-delta,sentry-grafana-correlation,extension-errors-debugging,tsc-blindspots,supply-chain-audit. It chooses among engines; it does not reimplement any investigation, so both orchestrators share one engine set.evidence's trust gates, which bind harder here: a weak instrument in review produces a claim someone challenges, in debugging it produces a theory nobody checks.Note:
extension-errors-debugging(#44) is currently routed to by no orchestrator, since it is not evidence for a PR claim. This gives it an entry point.Test plan
node .github/scripts/lint-skill-entry.mjs domains/pr-workflow/skills/debug/skill.md— 0 errors, 0 warningsnamematches directory,maturity: experimental, description within the 1536-char budget