simq-audit

Runs the SimQ full-audit workflow to recalibrate anchors, classify drift, and sync parity docs.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill simq-audit-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simq-audit
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.claude/skills/simq-audit
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill simq-audit-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a deterministic simulation engine's calibration corpus, grade anchors, and parity documentation in sync is a repetitive, error-prone chore. This Skill automates the repeatable SimQ audit cycle so drift is detected, classified, and either resolved as a chore commit or escalated into a ticket without manual orchestration. ## Core Features & Use Cases - Calibration Recalibration: Runs make simq-full-audit in fast, full, or slow modes to refresh the calibration corpus and capture REGRESS rows, pytest counts, uncovered anchor keys, and parity ledger candidates. - Drift Classification & Anchor Updates: Classifies each flagged item as EXPECTED_DRIFT, REGRESSION, DA_NEEDED, or NO_ACTION, then updates grade_anchors.json and anchor key lists only for expected drift, re-running targeted pytest subsets as a gate. - Docs & Parity Sync with Governance Branching: Updates evaluation matrix, integration, and parity ledger docs, then either proposes a chore commit for clean passes or spawns a ticket via the ticket-scoper role for regressions. - Use Case: After merging simulation changes, invoke the audit in full mode to verify no regressions crept in; if anchors drifted intentionally, they are refreshed and a chore commit is suggested, while genuine regressions produce a ticket handed off to /implement-ticket. ## Quick Start Ask the AI to run the SimQ audit in full mode for the frontier_extended and wilderness_survival worlds and report whether any regressions were found.

Frequently Asked Questions about simq-audit

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

FAQPage Schema
How do I run the SimQ full-audit workflow?

Invoke /simq-audit with an optional mode parameter: fast (default, dry-run diff only), full (re-runs all fast <=500t scenarios first), or slow (adds the 1000t/2000t tier). You can also scope calibration re-runs with a comma-separated worlds list in full mode.

What is the difference between fast, full, and slow audit modes?

Fast mode assumes data/calibration/ is already populated and only runs a dry-run diff. Full mode re-runs the engine for all fast scenarios up to 500 ticks first. Slow mode additionally runs the 1000-tick and 2000-tick tier after the fast tier passes.

Does the SimQ audit create a ticket for every run?

No. Clean passes with no regression return DONE_NO_TICKET and only suggest a chore commit message. A ticket is spawned via the ticket-scoper role only when the drift classification verdict is regression or needs_da_decision, returning NEEDS_TICKET with a hand-off to /implement-ticket.

Can the audit workflow fix regressions or update anchors automatically?

It updates grade_anchors.json and anchor key lists only for items classified as EXPECTED_DRIFT, then re-runs targeted pytest as a gate. It never touches REGRESSION or DA_NEEDED items and never fixes regressions or makes design-acknowledgment rulings itself.

Why does the audit workflow report ANCHORS_STILL_FAILING?

That status appears when the Update Anchors gate fails, meaning the targeted pytest subset still fails after anchor edits. The workflow writes monitoring records first, then stops and reports the blocking status with a re-run instruction instead of proceeding.