mister-anderson

Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks ("do this thoroughly", "be systematic", "deep work mode") OR when the task objectively spans multiple files, multiple sources, or multiple sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine.

Bootstrap project orchestration with beads task tracking.

Core engineering principles for implementation tasks

Create beads from a spec (full decomposition) or from user input (ad-hoc issues). Single entry point for all bead creation.

Dispatch the implementation supervisor for a bead task. Resolves the correct supervisor from the assignee field, checks branch state, and dispatches with full context.

QA finalization gate — validates spec conformity, runs tests/build/lint, produces a structured QA report. Auto-dispatches the supervisor for rework on FAIL. Last gate before human merge.

Code review gate — dispatches the code-reviewer agent to analyze an implementation branch, tracks findings, and auto-dispatches the supervisor for rework when verdict is NEEDS-REWORK.

Update mister-anderson plugin and clean up legacy local copies that are now provided by the plugin system.

Stage 2 orchestrator — guides Specification for a phase: plan → research → spec → tasks. Requires a phase number. Scans phase artifacts, skips completed steps, dispatches sub-skills in sequence.

Create high-level product architecture — system design, tech stack, structural decisions. Stage 1 only. For phase specs use /spec.

Meta-orchestrator — shows project state across all 3 stages, suggests next step, and routes to stage orchestrators or individual skills.

Create a new implementation supervisor for a specific technology. Invokes the Discovery agent in on-demand mode to fetch, filter, and inject the beads workflow into a specialist agent. Use when adding a new tech stack to the project (e.g., new package in monorepo).

Dispatch codebase investigation for a bead task. Resolves bead context, runs the research agent, and flags spec drift before implementation.

Create a phase/feature plan that scopes work, defines high-level tasks, and identifies dependencies. Dispatches Ada for planning.

Transform a raw idea into a structured PRD (Product Requirements Document). Dispatches Grace (product-manager) to elicit, structure, and validate requirements.

Validate technical assumptions from the plan against real APIs, libraries, and codebase before spec creation. Dispatches Smith to produce structured research docs.

Create a detailed technical spec grounded in validated research. Dispatches Ada with PRD + Plan + Research as inputs. Only after plan and research exist.

Stage 3 orchestrator — guides Implementation for a phase: shows task progress, routes through investigate → do → review → quality per task.

Stage 1 orchestrator — guides Product Discovery: manifesto → requirements → architecture. Scans artifacts, skips completed steps, dispatches sub-skills in sequence.

Guide the creation of a product manifesto — vision, principles, and governing laws that shape all downstream decisions.