Registry-as-ground-truth verification & autonomous research framework for agent-driven development.
Skill Claude CodeCodex
Implements verification claims — register.py, initfolder.py, frozen gates, tools/run.py, honest promotion. Use when adding a feature, creating a claim, promoting Planned to Verified/Failed, or following the lifecycle before writing feature code.
Skill Claude CodeCodex
Fast claim-harness iteration — reuse flags, single-job runs, cache discipline, honest labeling of dev shortcuts. Use when developing or debugging a claim gate before the official tools/run.py pass.
Skill Claude CodeCodex
Documents honest-negative verification outcomes when a claim fails — names the exact missing capability, updates the registry to Failed, sweeps dependent Planned claims, no shadow fixes. Use when tools/run.py exits 1, a claim fails its gates, or an experiment is terminal-negative although the mechanism is sound.
Skill Claude CodeCodex
Coordinates parallel agent sessions and git worktrees for verification work without colliding on registry.csv or shared config. Use when launching multiple background workers, parallel verification waves, worktree isolation, or merging claim branches.
Skill Claude CodeCodex
Fact-checks plans and architecture claims against registry.csv, claim lastrun.json evidence, and real code. Use when analyzing plans, verifying strategy documents, judging if a claim exists, checking Planned vs Verified status, or answering "does the code actually match this plan?".
Skill Claude CodeCodex
Reading map for substantive work — which big-picture and status docs to load before coding, verifying, or analyzing plans. Use when starting substantive edits, exploring architecture, onboarding to the repo, or before touching core modules.
Skill Claude CodeCodex
Queries the generated verification memory (tools/memory.py) — claims (ground truth) + plans (proposals), research fronts, per-claim dossiers, plan-to-claim links, BM25 search. Use when asking what was already tried, what plans exist for a topic, claim neighborhood, or before registering a new claim.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: