Default memory-backed workflow router for every coding, planning-before-coding, debugging, code review, refactoring, or implementation conversation. Always load it once per new coding session, select specialized workflows first, and use the general fallback otherwise. Handles th0th recall/search, durable memory, context compaction, handoff, audits, specs, ADR/RFC/TDD, and evidence gates. Do NOT use for generic non-coding chat or bulk-loading every workflow/reference.
Automatically select and apply a cataloged conversation persona at the start of every conversation and when task ownership changes. Use after massa-th0th in coding sessions, directly in non-coding sessions, or whenever the user explicitly selects, switches, rejects, or asks to route a persona. Do NOT use automatic inference when the AGENTS.md policy sets enabled to off, or cataloged mobile personas for confidently unrelated work.
Turn the current conversation into a PRD. Use when the user asks to create, synthesize, or convert existing discussion and codebase context into a Product Requirements Document without another interview. Do NOT use for implementation plans, architecture design docs, RFCs, TDDs, or discovery interviews that require new product questioning.
Expert guide for designing and building high-quality skills from scratch through structured conversation. Use when someone wants to create a new skill, build a skill, design a skill, or asks for help making Agents do something consistently. Also use when someone says "turn this into a skill", "I want to automate this workflow", "how do I teach my Agent to do X", or mentions creating SKILL.md files. Covers standalone skills and MCP-enhanced workflows. Do NOT use for specialized runtime subagent definitions or technical design documents; use massa-th0th's tdd workflow.
Generate a lean, high-value continuation package for AI-to-AI engineering handoffs. Use when another agent, model, chat, or session must continue active project work with limited context or quota. Preserve implementation intent, constraints, decisions, progress, and next steps while removing repetition and low-value history. Do NOT use for general project documentation, user-facing summaries, or handoffs that do not need implementation continuity.
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs". Do NOT use for production implementation, durable architecture, or polishing an already-approved design.
Refactor existing Node.js CLIs toward a layered or vertical-slice, command-driven architecture with thin entrypoints, focused command handlers, application services, pure domain logic, isolated infrastructure adapters, and characterization tests. Use when someone asks to refactor a CLI, separate command parsing from business logic, move logic out of the entrypoint, split work into src/commands src/services src/domain src/infrastructure, use a domain-first CLI or vertical slice layout, or perform a behavior-preserving CLI refactor. Do NOT use for greenfield scaffolding, non-CLI applications, or general infrastructure provisioning.