rigor-review

Reviews weekly build telemetry, judge scores, and DoD waivers to propose codified fixes for recurring corrections.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill rigor-review-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rigor-review
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/rigor-review
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill rigor-review-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Build-session feedback and corrections evaporate because nothing codifies them into durable improvements. This Skill runs a weekly, human-in-the-loop review (≤10 minutes) that turns recurring corrections into versioned fixes to rubrics, DoD rules, or skills. ## Core Features & Use Cases - Signal aggregation: Pulls build-session telemetry (JSONL shards), judge scores with human acknowledgment rates, DoD waiver logs, and tagged outcomes into one review. - Registry-driven thresholds: Reviews only the action-triggering metrics in the value-action registry (build-quality < 0.70, waiver rate, judge–human agreement ≥ 80%) and takes the named action when thresholds cross. - Correction-recurrence loop: Detects same-class corrections recurring across builds and proposes a codified fix (rubric bump, DoD tweak, skill edit) for human approval — never auto-applies. - Use Case: After a week of build sessions, run the review to spot that "orphan metric" corrections recurred three times, then approve a proposed rubric bump so the mistake stops recurring. ## Quick Start Run the weekly rigor review over the last 7 days of build sessions, judge logs, and DoD waivers, and propose fixes for any recurring correction classes.

Frequently Asked Questions about rigor-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a weekly build-quality review of AI coding sessions?

Run the rigor review over the last 7 days: it pulls build-session JSONL telemetry, judge scores, DoD waivers, and tagged outcomes, then checks them against the value-action registry's thresholds. It logs findings and proposes fixes for human approval.

How do I stop the same corrections from recurring across builds?

The review identifies same-class corrections recurring across builds, and once a class hits its threshold it proposes a codified fix such as a rubric bump, DoD tweak, or skill edit. The fix is applied only after explicit human approval, versioned so it sticks.

What metrics does the rigor review check?

It reviews only the action-triggering metrics in the value-action registry: build-quality scores below 0.70, corrective-rounds-to-value trend, DoD waiver rate, judge–human agreement of at least 80%, and acted-on outcome versus goal.

Does the rigor review apply fixes automatically?

No. It is strictly human-in-the-loop: the system proposes codified fixes and Alex approves or rejects them. Automating this loop is an explicitly deferred decision, and missing data is reported rather than fabricated.

What happens when there are no recurring corrections in a week?

The review logs "none — system holding" and ends without manufacturing work. It is designed to stay under 10 minutes so the ritual remains cheap enough to actually run every week.