Menú
This skill should be used when classifying tasks, routing to agents, determining complexity, or handling task routing, agent selection, verification requirements, and multi-component changes.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Search prior session history to recall how similar work was handled before. Use when you want to leverage a past approach, check prior experience on a topic, answer "how was this handled before", or cross-verify current handling against precedent from earlier sessions.
This skill should be used when looking up which agents own or consume specific skills, understanding skill-agent relationships, or routing tasks based on skill ownership.
This skill should be used when the user provides a vague request, asks to clarify requirements, structure a task, or refine a prompt for multi-agent orchestration.
This skill should be used when handling verification steps, quality gates, pre-commit checks, test failures, lint errors, build verification, or mandatory validation before task completion.
This skill should be used when handling agent model selection, tool access permissions, behavioral guardrails, MCP tool preferences, or any question about what agents can/cannot do.
Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.
| name | task-classification |
| description | This skill should be used when classifying tasks, routing to agents, determining complexity, or handling task routing, agent selection, verification requirements, and multi-component changes. |
Task classification is the foundational skill that enables intelligent routing of user requests to the appropriate agent(s) within the multi-agent orchestration system. This skill analyzes incoming tasks to determine:
Apply task classification when:
Tasks are classified into five primary categories:
| Category | Files | Risk | Primary Agent | Verification |
|---|---|---|---|---|
| Trivial | 0-1 | Low | Direct | None |
| Exploratory | N/A | Low | Riko | None |
| Implementation | 2-5 | Medium | Loid | Alphonse |
| Complex | 5+ | High | Full orchestration | Alphonse + Lawliet |
| Research | N/A | Low | Riko + WebSearch | None |
For Implementation and Complex tasks that decompose into 2-4 independent subtasks with exclusive file ownership, consider parallel team execution instead of sequential orchestration. Use the team-decision skill to analyze:
See team-decision skill for detailed criteria.
Simple, low-risk tasks handled directly without agent delegation.
Examples: Answering code questions, single-line fixes, documentation comments
Indicators: "what", "why", "how" questions; localized changes; no logic changes
Read-only investigation focused on understanding code or gathering information.
Examples: Finding usages, tracing data flow, understanding architecture
Agent: Riko (Explorer) with Grep, Glob, Read tools
Standard development tasks involving code changes across a moderate number of files.
Examples: New API endpoints, feature flags, bug fixes, refactoring functions
Agents: Loid (Executor) -> Alphonse (Verifier)
High-impact changes affecting multiple components, requiring full orchestration.
Examples: Major refactoring, security changes, database migrations, cross-service features
Agents: Riko -> Senku -> Loid -> Alphonse + Lawliet
Information-gathering requiring external research or documentation lookup.
Examples: Best practices research, library evaluation, documentation lookup
Agent: Riko (Explorer) with WebSearch
| Agent | Role | Model | Key Tools |
|---|---|---|---|
| Riko | Explorer | Opus | Read, Grep, Glob, Bash*, WebSearch, WebFetch |
| Senku | Planner | Opus | Read, Grep, Glob, TodoWrite |
| Loid | Executor | Sonnet | Read, Write, Edit, Grep, Glob, Bash |
| Lawliet | Reviewer | Sonnet | Read, Grep, Glob, Bash |
| Alphonse | Verifier | Sonnet | Bash, Read, Grep |
| Speedwagon | Authoring | Sonnet | Read, Grep, Glob, Write†, Edit†, Bash‡ — dispatch for /explain authoring |
For detailed agent routing, see references/agent-selection-matrix.md.
These conditions force Complex classification:
For detailed classification steps, see references/classification-process.md.
| Domain | Risk Increase | Reason |
|---|---|---|
| Authentication | Critical | Security breach potential |
| Database schema | Critical | Data loss, migration complexity |
| API contracts | High | Breaking changes for consumers |
| Shared utilities | Medium | Wide blast radius |
| Payment/billing | Critical | Financial impact |
| Configuration | Medium | Runtime behavior changes |
| Task Type | Type Check | Lint | Unit Tests | Integration | Review |
|---|---|---|---|---|---|
| Trivial | - | - | - | - | - |
| Exploratory | - | - | - | - | - |
| Implementation | Required | Required | Required | Optional | Optional |
| Complex | Required | Required | Required | Required | Required |
| Research | - | - | - | - | - |
| Keywords | Likely Classification |
|---|---|
| "what", "why", "how", "explain" | Trivial or Exploratory |
| "find", "search", "where", "trace" | Exploratory |
| "fix", "update", "add", "change" | Implementation |
| "refactor", "redesign", "migrate" | Complex |
| "research", "best practices", "compare" | Research |
| "all", "every", "entire", "across" | Complex (scope indicator) |
