Agent
Use on flagship work for the reliability review dimension — offline behaviour, retries, idempotency, sync conflict resolution, state restoration, and recovery from interruption. Conditional role. Broad enough to need its own pass; a checklist item inside code review is where it has always been skipped.
Agent
Use before /app-ship to audit the codebase for shippable-state security issues — credential handling, network safety, data-at-rest, third-party SDKs, OS permissions, auth flows, OWASP MASVS basics. Produces a written verdict with severity-classified findings.
Agent
Use to translate architecture into per-platform implementation specs, to design module boundaries, to set patterns the dev pod will reuse, and to make hands-on technical calls during execution. Hands-on senior engineer. Pairs with the dev pod, unblocks them on design questions, and owns the impl specs.
Agent
Use to stand up the dev pod, plan sprints, assign work in parallel, run standups, unblock ICs, and track progress. The orchestration layer between executives and ICs. Owns the sprint plan, the kanban board, and the daily report. Spawns parallel dev agents and the code-reviewer; escalates blockers to tech-lead or CTO.
Agent
Use on flagship work to build and own test infrastructure — the harness, the device and state matrix, CI test execution, evidence-bundle capture, and flake detection. Conditional role, distinct from qa-engineer's exploratory and acceptance passes. Writes code, so it runs the IC workflow.
Agent
Use to turn PRD user journeys into information architecture, navigation model, flows, and the screen-and-state inventory the dev pod builds against. Owns docs/12-flows.md. Hands the screen inventory to product-designer, who composes each screen.
Agent
Use to certify anything the team asserts but nobody executed — a threshold or constant that makes a real-world claim, a new guard rule/lint rule/architecture test, a "swept every instance" claim, or a batch of agent reports. Runs the thing instead of reading it. Triggered before /app-ship, at the end of /app-audit…
Agent
Use to implement web features from a ticket — TypeScript, a React/Next-shaped stack, and the browser platform. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a PR-equivalent (git branch + commit). Multiple instances run in parallel on independent tickets. This is the IC that makes product type…
Command
Grade an existing app against the Mobify Studio House KB and Axiom standards — fan out the specialist auditors, produce a severity-ranked gap report, build a remediation backlog, then fix (safe fixes automatically, risky changes only with your approval).
Command
Run the sprint — launch developer agents in parallel, review each PR, gate to QA, surface bugs back into the loop.
Command
Check a role before granting an operation on a path.
Command
Create a deterministic provenance manifest before an agent starts work.
Command
Open the full control room — five screens (Mission Control, Communications, Board, Team, Founder Inbox) in the browser.
Command
Open the emergency/diagnostic dashboard — zero-dependency, single file, works when the build stack is broken.
Command
Evaluation manifests define reproducible cases with an executable command, expected exit code, and required evidence text.
Command
Before merge, map every changed file to declared downstream consumers.
Command
Use the incident ledger for production or release-health events, not a normal ticket completion.
Command
Start a new mobile app project — runs requirements intake, then CEO vision, then PRD + architecture in parallel.
Command
Mine a shipped app's conventions into the living House Knowledge Base — adds net-new learnings to knowledge/.md, harvests its failures into knowledge/failure-corpus.md, and flags conflicts for human decision.
Command
Before respawning or replacing a manager, inspect its durable lease.
Command
Run the same persisted-state scenario in both modes.
Command
Agents may propose memory, but only a named reviewer can promote it.
Command
Adopt an EXISTING app — detect the stack, reverse-engineer the as-built architecture, and generate the baseline docs + CLAUDE.md so the team understands the codebase before auditing or extending it.
Command
Plan the next sprint — tech-manager turns backlog + impl specs into a parallelizable board.