Maestro:scrutiny Validator
Run code scrutiny validation during mission checkpoints. Spawns review subagents, synthesizes results, and produces validation reports.
Maestro Design
Use when the user wants to brainstorm, design, plan, choose wording, or decide a workflow, skill, harness, card/task/feature, architecture, UX, or agent-process change in a project using Maestro before implementation.
Mcp For Agents
>-
Cli For Agents
>-
Maestro Setup
Use when a project using or adopting Maestro needs init/install/sync/doctor, global skills, hooks, harness setup, or agent integration diagnosis or repair.
Maestro:mission Planning
Plan and structure new missions. Brainstorm raw ideas into decomposed missions with milestones, features, agent types, constraints, and the exact `maestro handoff` command for the first external agent.
Maestro Card
Use when the user wants to implement, fix, verify, QA, close, release, continue, use loop, keep looping, work while away, or work while asleep on Maestro cards/features/tasks in a project using Maestro after design is approved.
Gitnexus Refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\
Gitnexus Cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\
Docs
>-
Maestro:user Testing Validator
Run user testing validation during mission checkpoints. Determines testable assertions, sets up test environment, spawns flow validators, and synthesizes results.
Maestro
Agent harness for codebases. Gives Claude Code, Codex, and CI a shared task system, verdict ledger, and state store so agent work is traceable and auditable.
Maestro Dev
Development workflow for maestroCLI itself. Encodes the hexagonal architecture pattern (port -> adapter -> use-case -> command -> MCP tool -> test) and project-specific conventions. Use when implementing new maestro features, adding CLI commands, extending the MCP server, creating new adapters, modifying ports, writing use-cases, or debugging maestro's own code. Also use when you need to understa…
Maestro V2 Migration
Guide for working with maestroCLI's v2 architecture. Covers the context-to-memory rename, 4-state task model, plain file backend, pre-agent hooks, research phase, and memory promotion. Use when touching v2 code, encountering legacy patterns (e.g. 'context' instead of 'memory', old task states), adding new v2 features, or debugging v2 behavior. Also use when you see imports from adapters/fs/contex…
Gitnexus Debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\
Gitnexus Impact Analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
Maestro:define Mission Skills
Define and register custom skills for use in Mission Control missions. Create skill definitions with frontmatter, procedures, and validation rules.
Maestro Audit
Use when the user wants a read-only audit, code review, backlog proposal, or harness improvement finding for a project using Maestro, without applying fixes.
Gitnexus Exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\
Maestro:conduct
Enter conductor mode: plan, decompose, and dispatch -- sub-agents implement, not you. Use when user says 'you orchestrate', 'conduct this', 'delegate this', 'don't code yourself', 'break this into sub-agents', 'run this milestone without doing it yourself', or wants to stay in the driver seat while you manage agents. Works for formal mission/milestone execution and ad-hoc decomposition.
Maestro:blueprint
Generate visual HTML blueprint pages and structured plan specs for maestro project features. Explores the codebase, produces a `.md` plan in maestro format (Context, Critical Files, Design Decisions, Phases with Tasks and acceptance criteria) saved to `.maestro/plans/`, plus a visual HTML presentation. Use when the user asks to blueprint a maestro feature, plan an implementation for this project,…
Maestro Lifecycle Test
Validate a built maestro binary end to end (install/init completeness + the feature->task->QA lifecycle + standalone tasks + real-use edge cases + agent-UX) in an isolated throwaway repo, emitting a machine-aggregatable NDJSON report. Run as one sub-agent of a swarm fix-loop, or standalone to smoke-test a change.
Maestro:agent Base
Base procedures for all mission agents: startup, cleanup, and handoff. REQUIRED skill for all mission feature implementations.
Prompt Leverage
Strengthen a raw user prompt into an execution-ready instruction set for Amp, Claude Code, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
Gitnexus Guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\
Maestro Skill Author
Create, update, or debug maestro built-in skills. Covers SKILL.md frontmatter, reference directory structure, step-file architecture, build-time embedding, naming conventions, alias management, and registry validation. Use when creating a new maestro built-in skill, modifying an existing SKILL.md, adding reference files, debugging skill loading failures, updating the skills registry, or working o…