skill-orchestrationlisted

# Skill Orchestration Match the task to the right skills and MCP tools **before** acting. Do not start implementation until you have identified and loaded the relevant skills. ## Procedure 1. **Ground in global principles.** Apply SYSTEM.md and AGENTS.md first — think before acting, trace state/feedback/blast-radius, plan, minimal changes. These are always-on and never overridden by skills. 2. **Classify** the task using the matrix below (one or more domains may apply). 3. **Load** every matching skill's `SKILL.md` via the `read` tool. 4. **Route** to MCP tools where the matrix indicates — especially `search-docs` before writing framework code. 5. **Act** following global principles + the loaded skill's domain-specific instructions. 6. **Verify** per SYSTEM.md / AGENTS.md — tests, type-check, lint, build. ## Decision Matrix ### Backend — Laravel / PHP | Task Signal | Skills to Load | MCP Route | |-------------|---------------|-----------| | Controller, model, migration, form request, policy, job, service class | `laravel-best-practices`, `laravel-conventions` | `search-docs` (Laravel version-specific syntax) | | Eloquent query, N+1, slow query, eager loading | `database-optimization`, `eloquent-best-practices` | `database-query` (read-only verification), `database-schema` (before migrations) | | Filament resource, page, widget, relation manager | `cms-development` | `search-docs` (Filament), `list-artisan-commands` | | Writing or fixing Pest/PHPUnit tests | `pest-testin