Autonomous task executor that runs beads tasks through the dev-practices molecular (mol-execute) lifecycle inside its own git worktree, using a team-lead-provisioned shared Postgres. Use for any beads task that requires code changes and testing.
Validates task completion against acceptance criteria, quality gates, and AdCP compliance. Use after completing a beads task to verify everything meets standards before closing.
Spawn a team of agents to write per-obligation behavioral tests in parallel. Each agent researches, writes, runs, and fixes their test independently. Leader consolidates verified tests, runs quality gates, and commits.
Start an isolated PostgreSQL container for integration testing. Each worktree gets its own container on a unique port — no mutex, no conflicts. Use this before running integration tests in a worktree agent.
Run a repeatable code review audit on migration changes. Inventories files by architectural layer, reviews each layer against #1050/#1066 principles, and files beads issues for findings. Re-run after remediation batches to track progress.
Derive obligation tests using the test harness. First checks for harness availability, then generates compact tests using domain-specific test environments. Hard gate: no harness -> no tests (stops immediately). Replaces obligation-test for harness-enabled domains.
Apply the Google developer documentation style guide to everything this repo writes in prose: beads epic/task titles and descriptions, YAML formula step names and descriptions, .claude/notes/.md engineering notes, commit messages, docstrings, and code comments. Use before writing or reviewing any of those artifacts…
Create structural guard tests that enforce architecture principles on every make quality run. Guards are AST-scanning tests that prevent categories of violations automatically. Available guards: schema-inheritance, boundary-completeness, query-type-safety, no-error-dicts.
Two-pass BDD step assertion completeness inspector. Pass 1 (Sonnet): triage all Then steps — FLAG or PASS. Pass 2 (Opus): deep trace flagged steps with full production context, producing architectural judgment on what the correct assertion should be. Use after writing or modifying BDD step definitions to catch…
Map the complete test surface for domain entities by cross-referencing test-obligations with existing tests. Produces one canonical test module per entity with real tests + skip stubs for gaps. Every obligation maps to exactly one test. Run this before /remediate.
Verify every test expectation in entity test suites against the authoritative adcp spec and library sources. Adds spec permalinks to each test for traceability. Flags discrepancies where our tests assume behavior the spec doesn't define. Run this after /surface and before /remediate.
Claude Code instructions for prebid/salesagent, covering prebid sales agent - development guide, 🤖 for claude (ai assistant), working with this codebase, common task patterns and key files to know.