When to Use maestria
maestria adds structure through delegation, handoffs, and review. That structure costs model work, context transfer, and waiting time, so it is not the default.
Default Rule
Section titled “Default Rule”- Direct execution first. Familiar code, a clear scope, and easy verification make the platform’s normal agent the fastest and cheapest path.
- One specialist when one capability is missing. Unfamiliar code (adventurer), unknown cause (diagnose), a consequential choice (architect), or a second pair of eyes (reviewer). Then implement directly.
- Orchestrator only when the task needs staged handoffs, parallel work, or independent review: cross-module features, migrations, high-risk changes, unfamiliar systems, or durable handoffs across sessions.
Quick Decision
Section titled “Quick Decision”| Task | Start with |
|---|---|
| One or two known files and an obvious change | Direct execution |
| Small bug in unfamiliar code | adventurer or diagnose, then direct |
| UI, copy, or interactive iteration | Direct execution or blitz |
| Research or feasibility question | sonar (stop, no implementation) |
| Cross-module feature, migration, high-risk or long-running work | Orchestrator or fein |
| Sharing a workflow across clients | Portable Agent Plugin (the client owns activation and permissions) |
Mode keywords are defined in the mode table.
Each delegated stage adds a model turn, context transfer, waiting, and possible repair work. Strong or expensive models favor direct execution or one specialist; fast, inexpensive models can make narrow delegation a reasonable trade. Read the platform guide before assuming a route, permission, or lifecycle behavior transfers unchanged.