drain-inbox

Processes playtest capture inbox entries by reproducing bugs and proposing fixes interactively.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Playtest sessions generate a backlog of bug reports and questions stored as markdown captures in a pending inbox, and this Skill turns that raw feedback into verified, human-approved fixes without losing or mis-triaging any entry. ## Core Features & Use Cases - Lane claiming for parallel drains: Claims one or more buckets via inbox-claim.ts so multiple agents can drain concurrently without collisions, relaying live-lane announcements to the human. - Reproduction before fixing: Replays each capture headlessly from its embedded base64 save and viewport to confirm the symptom against the running game before proposing anything. - Interactive proposal gate: Presents the whole lane as one wholesale proposal (fix, route, or answer per item) and waits for human approval before committing any change. - Durable logging and archival: Logs F-entries per lane, stamps sidecar JSON files with status, and archives fully-drained buckets. - Use Case: After a playtest session leaves captures in project/playtest-inbox/pending/, run the drain to claim the map-feedback bucket, reproduce all five entries, propose fixes, and land them one commit per entry after approval. ## Quick Start Run /drain-inbox with a bucket name like map-feedback to claim that lane, reproduce its captures, and propose fixes for my approval.

Frequently Asked Questions about drain-inbox

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

FAQPage Schema
How do I process playtest bug reports from an inbox folder?

Run /drain-inbox with a bucket name to claim that lane, then the workflow reproduces every capture from its embedded save, proposes a fix or answer per item, and waits for your approval before committing anything.

Can multiple agents drain the playtest inbox in parallel?

Yes, parallel drains are sanctioned under ADR-171. Each agent claims its own lane via inbox-claim.ts, which reserves an F-number block and announces collisions so agents never touch the same captures.

How are playtest captures reproduced before fixing?

Each capture's sidecar JSON contains a base64 save, viewport, and context. The game is driven headlessly with pnpm run dev, the save is loaded via __qa.load, and the symptom is confirmed before any fix is proposed.

What happens to question captures versus bug captures?

Question captures get an answer or discussion in the proposal rather than a reflexive code fix, while bug captures are triaged into mechanical fixes, taste items routed to human review, or design forks surfaced as HD-items.

When is a playtest inbox bucket archived?

A bucket is archived only when every sidecar in it is stamped done; parked items hold it open. The markdown file and JSON metadata are moved with git mv while git-ignored screenshots move separately.