Grill-me interrogation discipline: convert context gaps into a relentless, adversarial, gap-closure-driven question set. Defines P0/P1/P2 tagging, gap-closure termination (no tight cap; large structural safety bound), the MC-vs-freeform rubric (2-6 choices + a 'Not sure / decide later' deferral, no 'Other'), do-not-invent-answers, and the bounded re-grill loop ending in [TBD]+OQ-NN. Triggers on: interview the user, grill me, structured PRD interview, gap questions, P0 questions.
Critic scoring rubric for drafted specs. Defines dimensions D1–D4 (both modes) and D5–D8 (update mode only), per-dimension scoring guidance, weighted aggregation, verdict thresholds (pass/revise/block). Replaces literal-diff-based rubric. Triggers on: score the spec, critic rubric, D1 mandatory coverage, D2 gated appropriateness, verdict thresholds.
Adaptive PRD section catalogue and complexity heuristic. Declares each section as mandatory or complexity-gated:<axis>, with industry-neutral names. Single source of truth for which sections to include and how to name them. Triggers on: PRD section list, PRD template, complexity heuristic, mandatory vs gated sections, adaptive sectioning.
Distilled spec-driven-development and PRD best practices: PR/FAQ framing (Working Backwards), structure-before-prose, outcome-over-output, P0/P1/P2 prioritisation, testable acceptance criteria, open-questions discipline. Triggers on: PRD best practices, spec-driven development, working backwards, PR/FAQ, outcome-over-output, testable acceptance criteria.
Entry workflow for creating evalpilot evals for Copilot agents and skills. Bootstraps evals/, discovers targets, scaffolds Markdown *.eval.md or TypeScript *.eval.ts specs, and hands off to eval-runner. Trigger keywords: create evals, author evals, test my agent, test my skill, evalpilot, eval.md, eval.ts, rubric, metric, regression.
Templates and patterns for creating GitHub Copilot CLI artifacts. Use when generating custom agents or skills. Keywords: agent.md, SKILL.md, implementation.
Multi-agent system design patterns and guidance. Use when designing agent architectures, planning agent boundaries, determining communication patterns, or evaluating single vs multi-agent approaches. Keywords: architecture, topology, orchestration, agent design.
Use evalpilot numeric metrics over time: JSONL history, baseline strategies, regression gates, evalpilot metrics reports, HTML trend charts, and CI checks. Trigger keywords: eval metrics, metric regression, history.jsonl, baseline, rolling mean, tolerance, trend, evalpilot metrics.