The evidence side of after-action reviews: analyzes Claude Code agent transcripts to establish what actually happened — checking a subject agent's self-debrief testimony against the record, autopsying dead/stalled/oversized runs, and clustering recurring failure patterns across sessions. Also dispatched to recover a…
Runs the promode methodology audit end-to-end: fans out parallel read-only assessors (one per alignment dimension) and synthesises their findings into a prioritised, actionable improvement plan for the main agent to ratify. Dispatch when the user wants to assess promode alignment/fit, audit a repo against the…
Cheap bulk generic executor (Haiku) for simple, well-specified non-code tasks — routine gathering, formatting non-source artifacts, file operations, running existing scripts. NOT for production code changes — those ride TDD in the engineer defs. Haiku has no effort control, so carries no effort field.
Plans and decides the crucial, hard-to-reverse marketing work: positioning and messaging strategy, brand/category strategy, the channel portfolio, growth strategy, launch strategy, the marketing-plan artifact, and pricing presentation/packaging (pricing level belongs to chief-product-officer /…
Plans and decides the crucial, hard-to-reverse product work: the goal hierarchy, establishing or majorly revising a persona, kill/build calls, and the evidence backing what users actually need. Marketing one-way doors — positioning, growth, channel strategy — belong to chief-marketing-officer. Drafts recommendations…
Reviews implementation work. Marks tasks done or requests rework. Pinned to Opus / high effort — review is a judgement seat, not mechanical execution; pass model: sonnet for simple mechanical diffs.
Walks the knowledge graph (rooted at CLAUDE.md) and ensures every crucial design constraint — invariants, prohibitions, required patterns, load-bearing decisions — is guaranteed-loaded into the nearest loaded CLAUDE.md orientation that governs the affected area. Dispatch when constraints are buried in ADRs, knowledge…
Investigates failures, analyzes logs, and finds root causes. Produces a reproduction test and reports findings. Does NOT implement fixes unless explicitly asked. Use for debugging, logging analysis, and error investigation. Defaults to Opus (deep-reasoning tier); pass model: sonnet for simple bugs.
Generic executor at the orchestrator's own tier (inherits the session model): the hardest non-code execution — judge/synthesis-grade grunt-work, deep research, gathering, non-source artifact assembly, running existing scripts. NOT for production code changes — those ride TDD in the engineer defs. Carries no effort…
Manages dev environments: health checks, docker, services, scripts. Ensures environments are healthy and easily manageable, and commits script/config changes before reporting.
General-purpose generic executor (Sonnet, medium effort) for routine non-code tasks — research, gathering, formatting non-source artifacts, file operations, doc assembly, running existing scripts. NOT for production code changes — those ride TDD in the engineer defs.
Drives browsers and GUIs with selector-based discipline: traversals, form-driving, visual checks, and exploratory driving that leave behind deterministic map/graph/recognizer artifacts. Does not change production code — flags code-lane work for engineer re-dispatch. Pinned to Sonnet.
Deep-reasoning generic executor (Opus, high effort) for non-code tasks that need strong judgement — complex research, synthesis, gathering, non-source artifact assembly, running existing scripts. NOT for production code changes — those ride TDD in the engineer defs.
Mechanical engineer rung for well-specified execution: boilerplate, straightforward changes, simple edits, repetitive work. Implements via TDD when the task changes code, and commits changes before reporting. Pinned to Sonnet.
Deep-reasoning engineer rung for reasoning-heavy phases: architecture-adjacent implementation, complex or multi-system changes, debugging fixes, algorithm design. Implements via TDD and commits changes before reporting. Pinned to Opus so the orchestrator's frontier model is reserved for orchestration.
Executes marketing artifacts: campaigns, ads and creative, copy and copy-editing, cold/outbound email, landing-page content, SEO/AI-search artifacts, launches at execution level, customer/VOC research runs, and recurring marketing loops. Grounds every asset in real source material and cites the docs/marketing/…
Executes user-facing product design: UX, psychology, behavioural economics, network effects, growth — thought through holistically. Maintains the design system and product knowledge in docs/product/ (incl. PERSONAS.md). Grounds every decision in realistic, evidence-backed personas and returns Approve/Refine/Reject…
Verifies a change works by exercising the running app/feature from the outside (via the /verify skill) and reporting PASS/FAIL with evidence. Does not write code or fix failures.