onboard-agent
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.
Bootstrap a new agent workflow from scratch, or add a new agent to an existing system.
Step 1: Establish Conventions
## Workflow Conventions
### Prompt Format
- Delimiter style: [XML tags / markdown headers / triple-dash]
- Section order: [System → Context → Instructions → Input]
- Output format: [JSON with schema / markdown template]
### Tool Conventions
- Naming: [verb_noun / noun.verb / camelCase]
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