tbh-companion

Feature planning and implementation with 4 adaptive phases — Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, and requirement traceability. Features an independent Verifier (author != verifier, evidence-or-zero), persistent decision log (STATE.md), and test-coverage-matrix-driven tests, plus a self-improving lessons layer that turns verification failures into reusable project-local guidance. Stack-agnostic. Use when (1) Planning features (requirements, design, task breakdown), (2) Implementing with verification and atomic commits, (3) Validating or verifying an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (use create-technical-design-doc).

Multi-agent PR reviewer for TBH Companion. Use ONLY when explicitly asked to review a pull request: "review PR #N", "review this PR", "code review", "check this pull request", "/review-pr N". Coordinates 6 specialized subagents then consolidates findings into a unified GitHub PR comment. Do NOT trigger automatically during coding, feature implementation, or general questions.

Capture screenshots (and optionally a short video) of a new TBH Companion feature and compose a player-facing announcement. Run after a feature is implemented and QA passes. Produces screenshots saved under docs/showcase/ and a Discord-ready announcement draft. Pairs with docs/agent/CHANGELOG-RELEASE.md for release notes. Not for internal docs, speculative/unreleased work, or reproducing screenshots that already exist in docs/.