battery

Runs multi-agent stress-test audits on game specs and builds through independent review lenses.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill battery-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: battery
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/battery
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill battery-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-reviewer audits of a game's spec, design, or build miss whole classes of defects because one perspective cannot cover fun, economy math, UI polish, save integrity, and canon drift at once. This Skill orchestrates independent fresh-eyes agents that each attack the subject through a different lens, then a convergence critic de-duplicates and scores the findings. ## Core Features & Use Cases - Three audit sizes: a full battery (6-13 lenses for milestone or pre-ship gates), a mini battery (~3 lenses to validate one fix or scenario), and a diff re-audit (~3 lenses over just the delta after a locked-ADR execution or large refactor). - Structured lens pipeline: lens agents read the subject cold and return structured findings (severity, evidence, proposed fix, new-vs-carryover), with adversarial refutation checks for large claims and a convergence critic that assembles the scorecard. - Full archiving and routing: raw verdicts are snapshotted, synthesis reports land in project/audit/reports/, a lens registry enforces novelty, and every actionable finding becomes an ADR or human-in-the-loop ledger row. - Use Case: Before calling a large refactor done, run a diff re-audit so three independent lenses verify the change matches the ADR, introduced no new failure modes, and did not silently alter an approved design pick. ## Quick Start Run a mini battery on the latest combat rebalance to validate the fix before I call it done.

Frequently Asked Questions about battery

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

FAQPage Schema
How do I run a stress-test audit on a game design or build?

Invoke the battery skill and pick a size: full battery for milestone or pre-ship gates, mini battery to validate one fix, or diff re-audit after a large refactor. Independent lens agents review the subject cold and a convergence critic scores their findings.

What is the difference between a full battery, mini battery, and diff re-audit?

A full battery runs 6-13 registry-tracked lenses for milestone or pre-ship gates. A mini battery runs about 3 lenses to validate one fix or scenario. A diff re-audit checks only the delta after a locked-ADR execution or large refactor.

When should I not use a multi-agent battery audit?

Skip the battery for taste or judgment calls, which need conversation rather than agents. Also avoid re-running unchanged areas; the registry enforces that each full battery includes at least one lens not yet run on the subject.

Can battery agents fix the design problems they find?

Agents may only self-resolve doc hygiene fixes and log new findings as open ledger rows. Changing locked decisions, promoting items into the spec, or resolving design questions always requires the human's approval.

Where do battery audit reports and findings get stored?

Raw verdicts are snapshotted into project/brainstorms/raw/, synthesis reports go to project/audit/reports/, the lens registry is updated with run dates, and actionable findings become ADR entries or human-in-the-loop ledger rows.