atomikpanda

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when working in a workspace with mothership.yaml — provides phase-based workflow, coordinated worktrees, dependency-ordered execution, healthchecks, and context recovery via the mship CLI

Use to receive and answer durable phone messages (the mship mailbox) while a session is idle — keep a background `mship inbox wait` armed and re-arm after each reply.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when executing implementation plans with independent tasks in the current session

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when you have a spec or requirements for a multi-step task, before touching code

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use at session start and before running shell commands involving Python, Node.js, file search, or HTTP requests.

Use when user asks to create a dotular module, add a tool to dotular, or manage a tool's config with dotular. Triggers on phrases like "create a module for X", "add X to dotular", "make a dotular module for X".