zero-defect
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Activate maximum precision mode for the current session. This command establishes execution-time discipline — not for the workflow design, but for how the agent itself operates. Every response, every code change, every claim must pass the zero-defect gate.
This is model-agnostic. It works with Claude, Gemini, GPT, Codex, or any AI agent.
The 8 Precision Rules
Follow these for the entire session after this command is invoked:
| # | Rule | Why |
|---|---|---|
| 1 | Read before writing — Re-read the relevant code/context before every modification | Prevents edits based on stale mental models |
| 2 | Verify before claiming — Run verification before any success claim | Prevents false completion reports |
| 3 | One logical change at a time — Avoid sprawling multi-file edits that compound errors | Reduces cascading failures |
More from sharpdeveye/maestro
agent-workflow
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
147evaluate
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
145diagnose
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
145calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
141teach-maestro
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
139iterate
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
139