calibrate

MANDATORY PREPARATION

Calibration Dimensions

• Tool names follow consistent pattern (verb_noun, noun.verb, or camelCase — pick one)
• Agent names follow consistent pattern
• Configuration keys follow consistent pattern
• File names follow consistent pattern

• All prompts use the same structural pattern (4-zone)
• Consistent delimiter style (XML tags, markdown headers, triple-dash)
• Consistent output schema format (JSON schema, markdown template)
• Consistent instruction style (imperative, numbered steps)

• All tools return errors in the same format
• Error codes follow consistent scheme
• Error messages follow consistent tone
• Retry logic uses consistent strategy

• All logs use the same format (JSON structured, text, etc.)
• Consistent field names across all log entries
• Consistent log levels (debug, info, warn, error)
• Consistent PII redaction approach

Calibration Process

1. Identify the standard: What's the most common pattern in the existing codebase? That's the standard.
2. List deviations: Find all components that deviate from the standard.
3. Prioritize: Fix the most impactful deviations first (user-facing > internal).
4. Apply: Make the changes, ensuring tests still pass.
5. Document: Update

   .maestro.md

   with the established conventions.

Consistency Audit Table

Calibration Checklist

• Convention standard identified for each dimension
• All deviations listed with location
• Highest impact deviations fixed first
• Tests pass after each calibration change
• Updated

  .maestro.md

  with established conventions

Recommended Next Step

{{command_prefix}}refine

{{command_prefix}}evaluate

• Invent new conventions when existing ones work
• Calibrate in a way that changes behavior (this is standardization, not refactoring)
• Skip test verification after calibration
• Change naming conventions without updating all references