dungeonmaster

Find deepening opportunities across the codebase — refactors that turn shallow pass-through modules into deep ones, for testability and AI-navigability. Informed by architecture.md and the ADRs in docs/decisions/; never re-litigates a decided ADR. Use when Tobi wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a part of the bot more testable. Whole-codebase altitude — not /simplify or /code-review (those are diff-scoped).

Turn the current conversation context — ideally after a /grill-me session — into a PRD written to the repo. Do NOT interview; synthesize what's already been decided. Use when Tobi wants to turn a grilled-out plan into a written spec, or says "to-prd" / "schreib den Plan".

Interview Tobi relentlessly about a plan or design decision until reaching shared understanding, resolving each branch of the decision tree one fork at a time. Use when he wants to stress-test a plan before building, asks to "get grilled", or says "grill me". For design/architecture forks — not for mechanical edits.

Use when changing the deterministic core (dmbot/rules/, engine.py, marker.py, any new pure function with verifiable behaviour) and you want the change driven by a failing test first. Enforces red-green-refactor against the repo's fixed-seed pytest setup: write one failing test, confirm red, implement minimal green, refactor. Not for prose/persona/prompt edits or RAG ingestion.

Use when the user pastes a live Discord session log, transcript, or annotated complaints from a play session and wants a fix round. Diagnoses the failure chain from the logs, extracts player improvement-wishes, applies deterministic fixes, runs the test suite, commits per round, and updates progress.md (and an ADR when a real trade-off was decided).

Use at the start of a working session for the handshake (read CLAUDE.md → progress.md → the latest ADR, then state where we are and what's next), and at the end of a session or on "wrap up" / "update progress" to update progress.md and scaffold the next-numbered ADR. Keeps continuity across context clears and model switches.

Use when a player's Imperium Maledictum character JSON comes in and needs validating + deploying, when building a new IM character from scratch, or when backfilling backstory onto an existing sheet. Validates budgets/formulas/psyker powers/augmetics against the active profile, writes data/party/<player>.json, generates the PDF sheet, and proposes (confirm first) the merge into the session characters.json + aliases.

Use when ingesting a new PDF or curated source into the RAG store, or when recalibrating retrieval. Converts PDF→markdown with page/spoiler control, inspects a real chunk, ingests with a source tag, wires the source into retrieval, calibrates the distance threshold, and verifies a sample question hits while a spoiler probe stays silent.

Use when adding a new profile-driven rules subsystem to a system profile (in the style of the psyker or augmetics subsystems) — e.g. a new test type, resource, combat mechanic, or character-data block. Scaffolds the profile data block, pure engine functions, fixed-seed tests, state-summary integration, an optional in-band marker + button, and a persona hint.