메뉴
Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
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.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Capture a session summary — what was done, what decisions were made, and what to do next.
| name | onboard-agent |
| description | Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch. |
| argument-hint | [project or agent name] |
| category | utility |
| version | 2.0.0 |
| user-invocable | true |
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.
## 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]
- Description template: [What → When → When Not → Returns]
- Error format: [{ code, message, details }]
### Logging
- Format: [JSON structured]
- Required fields: [workflow_id, step, timestamp, level]
### File Structure
- Prompts: [prompts/workflow-name/v1.md]
- Tools: [tools/tool-name.{ext}]
- Config: [config/environment.yaml]
- Tests: [tests/workflow-name/]
project/
├── prompts/ # System prompts, versioned
├── tools/ # Tool definitions
├── config/ # Environment-specific configuration
├── tests/ # Golden test sets and evaluation suites
├── logs/ # Runtime logs (gitignored)
└── .maestro.md # Workflow context
After onboarding, run /diagnose for a baseline health check, then /fortify to add production-grade error handling.
NEVER: