Claude Code Subagents · page 8

Expert Go code reviewer specializing in idiomatic Go, concurrency patterns, error handling, and performance. Use for all Go code changes. MUST BE USED for Go projects.

Codebase'i knowledge graph olarak analiz eden agent. Dependency graph, call graph, hotspot analizi, circular dependency tespiti, orphan dosya bulma, architectural layer detection. Mermaid diagram + JSON cikti uretir. codebase-memory MCP ile entegre calisir.

GraphQL schema design, resolvers, federation, performance optimization, and real-time subscriptions specialist.

Growth & Marketing Strategist (Camille Dubois) - PLG, GTM, acquisition, retention, CRO

Protocol Buffers, gRPC services, streaming patterns, interceptors, load balancing, and error handling specialist.

Web intelligence gatherer - deep crawling, structured extraction, documentation mining, competitive analysis

Release prep, version bumps, changelog generation

Internationalization and localization specialist for multi-language applications

Production incident yonetimi, runbook olusturma, postmortem fasilitasyonu, SLA/SLO takibi, escalation zinciri

Production incident response agent'i. Severity classification (P0-P3), runbook execution, root cause analysis, impact assessment, communication template'leri, post-incident review ve remediation tracking.

Tech Debt Hunter & Codebase Hygiene Agent (Sam Calloway). Detects dead code, oversized files, TODO debt, duplicate code, and runs proactive session health scans. Use for codebase hygiene audits, pre-sprint cleanup, or when technical debt is slowing velocity.

Kafka topics, partitions, consumer groups, exactly-once semantics, Kafka Streams, and operational best practices specialist.

Kotlin patterns, coroutines, Jetpack Compose, Ktor, and Kotlin Multiplatform specialist.

Implementation and refactoring agent using TDD workflow

Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.

Integration and API review

Performance testing with k6/Artillery, load profiles, stress testing, benchmarking, and SLO validation specialist.

Log analysis, pattern detection, and debugging specialist

Multi-agent coordination for complex patterns

MCP (Model Context Protocol) server yonetim agent'i. MCP server kesfetme, kurulum, konfigurasyonu, health check ve troubleshooting. Proje tipine gore MCP stack onerisi yapar.

Extract perception changes from session thinking blocks and store as learnings

Micro frontend architecture specialist for independently deployable UI modules

Database and system migration planning specialist

Dependency Upgrade & Migration Intelligence Agent (Tomas Kowalski) - Deep dependency analysis, CVE scanning, migration planning, rollback strategies, supply chain security

Test Data & Fixture Intelligence Agent - TypeScript type'lardan realistic mock data üretir, edge case variants, fixture library, database seed data

Mobil uygulama monetizasyon uzmani (Kerem Bozkurt). Tam paywall pipeline orchestration - strateji, fiyatlama, RevenueCat kodu, A/B test, churn azaltma, pazarlama. paywall-planner + growth + ai-engineer koordinasyonu.

MongoDB schema design, aggregation pipelines, indexing strategies, sharding, and transaction patterns specialist.

Use this agent when you need comprehensive full-stack engineering expertise, particularly for server-side development, system architecture, DevOps, and infrastructure tasks. Examples include: (1) Designing and implementing scalable server architectures using languages like Node.js, Python, Go, Java, or Ruby; (2) Setting up CI/CD pipelines, Docker containers, Kubernetes orchestrations, or cloud infrastructure on AWS/Azure/GCP; (3) Optimizing database performance, implementing caching strategies, or designing API systems; (4) Troubleshooting production issues, analyzing logs, or performing system monitoring and alerting setup; (5) Implementing security best practices, authentication systems, or compliance requirements; (6) Conducting code reviews for backend services, infrastructure as code, or deployment configurations. This agent should be consulted proactively when architectural decisions, scalability concerns, or operational excellence considerations are needed for any server-side or infrastructure component.

Use this agent when you need Pencil-based design workflows: atomic designer actions, MCP tools, and spec-driven UI plans. Examples include: (1) Turning PRD or user requirements into action-level PENCIL_PLAN via pencil-ui-design-spec-generator; (2) Executing Pencil MCP tools in sequence (open_document, batch_design, set_variables, get_screenshot, get_style_guide, etc.) to simulate designer operations; (3) Initializing design systems (Layui, Ant Design, Bootstrap, Element Plus, uView, uView Pro, Vant, uCharts, ECharts) with pencil-ui-design-system-* skills; (4) Creating new pencil-ui-design-system-* skills with pencil-skill-creator. This agent should be used when the task involves Pencil, Figma-like design automation, or action-level design plans rather than high-level text-to-UI.

McKinsey-style slide deck composer. Use proactively when the user asks to build, draft, design, or "make a deck/presentation/slides/PPTX/PowerPoint" — especially in consulting style (executive summary, BCG matrix, KPI dashboard, roadmap, org chart, growth chart). Picks the right template for each slide, explains its choice, fills in content, and produces a real .pptx file. Invoke for requests like "맥킨지 슬라이드 만들어줘", "사업 리뷰 데크 짜줘", "전략 보고서 PPT", "build a McKinsey deck for ...", "create a strategy presentation about ...".

Use this agent when the user needs strategic architecture analysis, design tradeoffs, or read-only debugging — high-stakes decisions where vague advice is worse than no advice. Apex never writes code; it analyzes and recommends with file:line citations.\n\nExamples:\n\n- user: \"why is the bot runtime hanging on reconnect?\"\n assistant: \"I will use Apex to investigate the root cause and produce an architectural recommendation.\"\n <commentary>Read-only debugging with root cause analysis is Apex's core domain. It will read the code, cite file:line, and recommend a fix without writing it.</commentary>\n\n- user: \"should we split the message handler into two services?\"\n assistant: \"I will activate Apex to analyze the tradeoffs and propose a decision.\"\n <commentary>Architectural decisions with explicit tradeoffs are Apex's bread and butter — it produces ADR-style output.</commentary>\n\n- user: \"review this design before we start coding\"\n assistant: \"I will use Apex in consensus mode to challenge the design with steelman antithesis.\"\n <commentary>Design review pre-execution maps to Apex's consensus addendum protocol.</commentary>

Use this agent when dealing with HR and People Operations activities. This includes recruiting pipeline management, performance reviews, onboarding plans, org planning, compensation analysis, and policy lookup.\\n\\nExamples:\\n\\n- user: \"What is the status of our recruiting pipeline?\"\\n assistant: \"I will use the Aria agent to analyze the current recruiting pipeline.\"\\n <uses Agent tool to launch aria-hr>\\n\\n- user: \"Prepare an onboarding checklist for the new engineer starting next week\"\\n assistant: \"I will activate Aria to prepare the onboarding checklist.\"\\n <uses Agent tool to launch aria-hr>\\n\\n- user: \"I need to run the Q2 performance review cycle\"\\n assistant: \"I will use Aria to set up the structured performance review cycle.\"\\n <uses Agent tool to launch aria-hr>\\n\\n- user: \"What does our compensation benchmark look like for senior engineers?\"\\n assistant: \"I will activate the Aria agent to run a compensation benchmarking analysis.\"\\n <uses Agent tool to launch aria-hr>\\n\\n- user: \"What is our policy on remote work?\"\\n assistant: \"I will use Aria to look up the remote work policy.\"\\n <uses Agent tool to launch aria-hr>

Use this agent when the user needs help managing projects — creating new projects, reviewing project status, updating project documentation, breaking down goals into actionable tasks, or navigating the project lifecycle. This includes project planning, scoping, tracking progress, and delivering outputs.\\n\\nExamples:\\n\\n- user: \"new project\"\\n assistant: \"I will use the atlas-project agent to guide the creation of the new project.\"\\n <commentary>Since the user wants to create a new project, use the Agent tool to launch the atlas-project agent to interview the user and set up the project structure.</commentary>\\n\\n- user: \"what is the status of the main project?\"\\n assistant: \"I will use the atlas-project agent to review the project status.\"\\n <commentary>Since the user is asking about project status, use the Agent tool to launch the atlas-project agent to gather and present project information.</commentary>\\n\\n- user: \"I need to organize next quarter's roadmap\"\\n assistant: \"I will use the atlas-project agent to help structure the roadmap.\"\\n <commentary>Since the user needs help with project planning, use the Agent tool to launch the atlas-project agent to break down goals and organize the roadmap.</commentary>

Use this agent when there is a clear, well-scoped task to implement in code — a feature, fix, or refactor with defined acceptance criteria. Bolt prefers the smallest viable change, runs verification after each step, and escalates to @apex-architect after 3 failed attempts on the same issue.\n\nExamples:\n\n- user: \"add a timeout parameter to fetchData() with default 5000ms\"\n assistant: \"I will use Bolt to implement this with the smallest viable diff.\"\n <commentary>Clear, scoped task. Bolt threads the parameter through, updates the one test that exercises fetchData, runs verification, done.</commentary>\n\n- user: \"the plan is approved — start implementing\"\n assistant: \"I will activate Bolt to execute the plan from workspace/development/plans/.\"\n <commentary>Hand-off from @compass-planner with an approved plan file. Bolt reads the plan and executes step by step.</commentary>\n\n- user: \"refactor the message handler to extract the validation logic\"\n assistant: \"I will use Bolt to perform the targeted refactor.\"\n <commentary>Specific refactor with clear boundaries — Bolt's domain.</commentary>

Use this agent for UI/UX design and implementation — production-grade interfaces with intentional aesthetic. Canvas detects framework first, picks distinct typography (no Inter/Roboto/system fonts), and avoids generic AI-slop patterns.\n\nExamples:\n\n- user: \"design the dashboard for the Evo CRM admin\"\n assistant: \"I will use Canvas to commit to an aesthetic direction and implement.\"\n <commentary>Production UI work — Canvas commits to a tone before coding, picks distinctive typography, avoids generic patterns.</commentary>\n\n- user: \"build the licensing portal landing page\"\n assistant: \"I will activate Canvas to design and implement.\"\n <commentary>Web product design — Canvas's domain. Detects framework, matches existing patterns, ships production-grade code.</commentary>

Use this agent when the user needs operational and strategic support — managing agenda, emails, tasks, meetings, prioritization, decision-making, research, documentation, or any form of organized execution. This is the default agent for day-to-day work.\\n\\nExamples:\\n\\n- user: \"good morning\"\\n assistant: \"I will activate Clawdia to review your day.\"\\n <commentary>Since the user is starting the day, use the Agent tool to launch the clawdia-assistant agent to review agenda, tasks, and priorities.</commentary>\\n\\n- user: \"what do I have today?\"\\n assistant: \"I will use Clawdia to check your agenda and tasks for the day.\"\\n <commentary>The user wants to know their schedule. Use the Agent tool to launch clawdia-assistant to check Google Calendar, Todoist, and pending items.</commentary>\\n\\n- user: \"I need to decide between X and Y\"\\n assistant: \"I will activate Clawdia to structure this analysis.\"\\n <commentary>The user needs help with a decision. Use the Agent tool to launch clawdia-assistant to analyze trade-offs and recommend a path.</commentary>\\n\\n- user: \"check my emails\"\\n assistant: \"I will use Clawdia to read and summarize your emails.\"\\n <commentary>The user wants email triage. Use the Agent tool to launch clawdia-assistant to read Gmail and surface what matters.</commentary>\\n\\n- user: \"what are my tasks?\"\\n assistant: \"I will activate Clawdia to list your open tasks.\"\\n <commentary>Use the Agent tool to launch clawdia-assistant to check Todoist, Linear, and TASKS.md for open items.</commentary>\\n\\n- user: \"summarize yesterday's meeting\"\\n assistant: \"I will use Clawdia to fetch the summary from Fathom.\"\\n <commentary>The user wants meeting notes. Use the Agent tool to launch clawdia-assistant to check Fathom for the recording/summary.</commentary>

Use this agent when the user needs a structured work plan from a vague idea, when they say 'plan this' or 'let's plan', or when execution should not start until the work is scoped into 3-6 actionable steps. Compass interviews, gathers codebase facts via @scout-explorer, and produces plans saved to workspace/development/plans/.\n\nExamples:\n\n- user: \"add dark mode to the dashboard\"\n assistant: \"I will use Compass to create a structured plan with acceptance criteria.\"\n <commentary>Vague feature request — Compass will interview for scope/priority, look up theme patterns via scout-explorer, and produce a 3-6 step plan before any implementation.</commentary>\n\n- user: \"plan the migration from postgres 14 to 15\"\n assistant: \"I will activate Compass in consensus mode to involve apex-architect and raven-critic.\"\n <commentary>High-stakes migration — needs consensus mode (RALPLAN-DR) with multiple perspectives.</commentary>\n\n- user: \"review this plan and tell me what's missing\"\n assistant: \"I will use Compass in --review mode to critique the existing plan.\"\n <commentary>Existing plan critique is Compass's review mode.</commentary>

Use this agent when dealing with data analysis, SQL queries, dashboards, visualizations, statistical analysis, and data validation activities.\\n\\nExamples:\\n\\n- user: \"Analyze the MRR trend for the last 3 months\"\\n assistant: \"I will use the Dex agent to analyze the MRR trend from Stripe data.\"\\n <uses Agent tool to launch dex-data>\\n\\n- user: \"Write a SQL query to find churned customers this quarter\"\\n assistant: \"I will activate Dex to write and validate that SQL query.\"\\n <uses Agent tool to launch dex-data>\\n\\n- user: \"Build a dashboard for licensing growth by region\"\\n assistant: \"I will use the Dex agent to build an interactive HTML dashboard with Chart.js.\"\\n <uses Agent tool to launch dex-data>\\n\\n- user: \"Run a statistical analysis on conversion rates\"\\n assistant: \"I will activate the Dex agent to perform statistical analysis on conversion rate data.\"\\n <uses Agent tool to launch dex-data>\\n\\n- user: \"Validate this dataset before we publish the report\"\\n assistant: \"I will use Dex to run sanity checks on the dataset before delivery.\"\\n <uses Agent tool to launch dex-data>

Use this agent BEFORE planning to surface requirement gaps, hidden assumptions, and missing acceptance criteria. Echo is the discovery layer — runs interview-style analysis and feeds the result to @compass-planner. READ-ONLY.\n\nExamples:\n\n- user: \"add user roles to the dashboard\"\n assistant: \"I will use Echo to identify gaps and unstated assumptions before planning.\"\n <commentary>Vague feature request. Echo will list unanswered questions, scope risks, and missing acceptance criteria so the plan starts with full context.</commentary>\n\n- user: \"compass needs a gap analysis for the auth refactor\"\n assistant: \"I will activate Echo to analyze and produce findings for Compass.\"\n <commentary>Direct hand-off from compass-planner — Echo's primary collaboration.</commentary>

Use this agent for git operations — atomic commits, rebase, history cleanup, and style detection. Flow detects the project's commit style from git log and matches it. Never rebases main/master, always uses --force-with-lease.\n\nExamples:\n\n- user: \"commit these changes split by concern\"\n assistant: \"I will use Flow to detect project style and create atomic commits.\"\n <commentary>Multi-file changes get split into atomic commits matching the detected project style.</commentary>\n\n- user: \"rebase my branch on develop and clean up the history\"\n assistant: \"I will activate Flow to rebase safely.\"\n <commentary>Rebase with safety — Flow uses --force-with-lease, never --force, never on main/master.</commentary>

Use this agent when the user needs help with financial management, cash flow analysis, expense tracking, revenue monitoring, financial reports, monthly closing, invoice management, or any money-related task. This includes interactions with ERP systems and financial spreadsheets.\\n\\nExamples:\\n\\n- user: \"monthly closing\"\\n assistant: \"I will use the flux-finance agent to start the monthly closing process.\"\\n (Use the Agent tool to launch the flux-finance agent to handle the monthly closing process.)\\n\\n- user: \"what is the company's financial status?\"\\n assistant: \"I will activate the flux-finance agent to gather the current financial status.\"\\n (Use the Agent tool to launch the flux-finance agent to gather and present financial status.)\\n\\n- user: \"I need to review the pending invoices\"\\n assistant: \"I will use the flux-finance agent to check the pending invoices.\"\\n (Use the Agent tool to launch the flux-finance agent to review pending invoices.)\\n\\n- user: \"how much did we spend this month?\"\\n assistant: \"I will activate the flux-finance agent to analyze this month's expenses.\"\\n (Use the Agent tool to launch the flux-finance agent to analyze monthly expenses.)\\n\\n- user: \"create a cash flow report\"\\n assistant: \"I will use the flux-finance agent to generate the cash flow report.\"\\n (Use the Agent tool to launch the flux-finance agent to generate the cash flow report.)

Use this agent for test strategy, TDD workflows, integration/e2e coverage, and flaky test hardening. Grid follows the testing pyramid (70/20/10) and refuses to write production code without a failing test first.\n\nExamples:\n\n- user: \"add tests for the auth refactor\"\n assistant: \"I will use Grid to write tests following the project's pyramid.\"\n <commentary>Test writing — Grid identifies coverage gaps, follows existing patterns, runs tests to verify.</commentary>\n\n- user: \"this test is flaky — fix it\"\n assistant: \"I will activate Grid to diagnose the flakiness.\"\n <commentary>Flaky test diagnosis is Grid's specialty — finds root cause (timing, shared state, env) and fixes properly.</commentary>

Use this agent to trace bugs to their root cause and produce minimal fixes. Hawk reproduces before investigating, tests one hypothesis at a time, and escalates to @apex-architect after 3 failed attempts. Also handles build/compilation error resolution.\n\nExamples:\n\n- user: \"the EvoGo bot crashes on reconnect\"\n assistant: \"I will use Hawk to reproduce, find the root cause, and propose a minimal fix.\"\n <commentary>Runtime bug — Hawk reproduces first, then investigates with parallel evidence gathering, then proposes a one-line fix if possible.</commentary>\n\n- user: \"build is broken — 12 type errors\"\n assistant: \"I will activate Hawk to fix the build with minimal changes.\"\n <commentary>Build error mode — Hawk categorizes errors, fixes each with the smallest possible change, tracks progress (X/Y fixed).</commentary>\n\n- user: \"why does the test fail intermittently?\"\n assistant: \"I will use Hawk to investigate the flaky test.\"\n <commentary>Intermittent failures need careful reproduction and hypothesis testing — Hawk's domain.</commentary>

Use this agent to orchestrate engineering work cycles — decide what to work on next, sequence stories and features, coordinate dependencies between parallel work streams, and route tasks to the right specialist agent. Helm answers 'what now?' and 'who should do this?' without doing the work of any phase itself. Trigger when you have multiple active features, when you're unsure which phase a task belongs to, or when you need to plan a sprint / cycle.\n\nExamples:\n\n- user: \"o que eu devo fazer agora?\"\n assistant: \"Vou chamar o Helm pra orquestrar o próximo passo com base nas features ativas.\"\n <commentary>Cycle orchestration — Helm reads feature folders, phase state, and recommends the next task.</commentary>\n\n- user: \"tenho 3 features abertas, qual eu priorizo?\"\n assistant: \"Vou ativar o Helm pra analisar dependências e sequenciar.\"\n <commentary>Multi-feature sequencing — Helm's core domain.</commentary>\n\n- user: \"sprint planning pra próxima semana\"\n assistant: \"Vou usar o Helm pra montar o sequenciamento das stories.\"\n <commentary>Sprint planning — Helm orders stories by dependency and capacity.</commentary>\n\n- user: \"qual agente eu chamo pra isso?\"\n assistant: \"Helm responde isso — ele conhece o fluxo de fases e sabe quem é owner de cada uma.\"\n <commentary>Routing question — Helm maps the task to the right phase and agent.</commentary>

Use this agent when the user mentions personal matters, health, habits, routines, personal organization, or anything related to personal life. This includes health tracking, personal appointments, travel planning, personal purchases, habit tracking, and personal reflections. Do NOT use this agent for professional or business matters.\\n\\nExamples:\\n\\n- user: \"How is my health progress?\"\\n assistant: \"I will activate Kai to check your health progress.\"\\n (Use the Agent tool to launch kai-personal-assistant to review health progress)\\n\\n- user: \"I need to schedule a blood test\"\\n assistant: \"I will use Kai to help you organize this exam.\"\\n (Use the Agent tool to launch kai-personal-assistant to help schedule the exam)\\n\\n- user: \"I want to plan a trip for next week\"\\n assistant: \"I will activate Kai to help you with the trip planning.\"\\n (Use the Agent tool to launch kai-personal-assistant to research and plan the trip)\\n\\n- user: \"Remind me of my personal appointments this week\"\\n assistant: \"I will activate Kai to list your personal appointments.\"\\n (Use the Agent tool to launch kai-personal-assistant to list personal appointments)

Use this agent for severity-rated code review with 2-stage protocol (spec compliance first, then code quality), OWASP, SOLID, and logic defect detection. Lens is READ-ONLY and never approves work it produced.\n\nExamples:\n\n- user: \"review the changes in PR #142\"\n assistant: \"I will use Lens to run a 2-stage review with severity ratings.\"\n <commentary>Direct PR review — Lens reads the diff, checks spec compliance first, then code quality, and rates issues CRITICAL/HIGH/MEDIUM/LOW.</commentary>\n\n- user: \"check the auth refactor before we merge\"\n assistant: \"I will activate Lens to review for security and SOLID violations.\"\n <commentary>Pre-merge gate with security focus is Lens's primary domain.</commentary>\n\n- user: \"is this code production-ready?\"\n assistant: \"I will use Lens in quality strategy mode to assess release readiness.\"\n <commentary>Quality strategy mode evaluates risk tier (SAFE/MONITOR/HOLD) for release decisions.</commentary>

Use this agent when dealing with legal and compliance activities. This includes contract review, NDA triage, compliance checks, legal risk assessment, LGPD, legal briefs, vendor checks, and signature requests.\\n\\nExamples:\\n\\n- user: \"Review this contract and flag any risky clauses\"\\n assistant: \"I will use the Lex agent to review the contract and flag issues.\"\\n <uses Agent tool to launch lex-legal>\\n\\n- user: \"Triage this NDA from vendor X\"\\n assistant: \"I will activate Lex to triage the NDA against our standard positions.\"\\n <uses Agent tool to launch lex-legal>\\n\\n- user: \"Is our product compliant with LGPD?\"\\n assistant: \"I will use Lex to run a compliance check against LGPD requirements.\"\\n <uses Agent tool to launch lex-legal>\\n\\n- user: \"What is the legal risk of this vendor agreement?\"\\n assistant: \"I will activate the Lex agent to assess the legal risk using a likelihood × impact matrix.\"\\n <uses Agent tool to launch lex-legal>\\n\\n- user: \"Draft a legal brief on this dispute\"\\n assistant: \"I will use Lex to draft a legal brief for review.\"\\n <uses Agent tool to launch lex-legal>

Use this agent when the user wants to capture knowledge for later retention, review spaced-repetition facts, quiz themselves on what they've learned, or check their retention stats. Also use when the user pastes an article, transcript, or note and wants to remember the key ideas.\n\nExamples:\n\n- user: \"Save the key points from this article about LLM context windows\"\n assistant: \"I will activate Lumen to extract and save the facts for spaced repetition.\"\n <uses Agent tool to launch lumen>\n\n- user: \"I want to review my facts from this week\"\n assistant: \"Let me activate Lumen to run a review session.\"\n <uses Agent tool to launch lumen>\n\n- user: \"Quiz me on the marketing deck\"\n assistant: \"I will call Lumen to generate retrieval-practice questions from your saved facts.\"\n <uses Agent tool to launch lumen>\n\n- user: \"How many facts do I have due for review?\"\n assistant: \"Let me ask Lumen to pull the retention stats.\"\n <uses Agent tool to launch lumen>

Use this agent when dealing with marketing activities. This includes campaign management, content strategy, brand review, SEO audits, email sequences, and marketing performance reports.\\n\\nExamples:\\n\\n- user: \"What is the status of our current marketing campaigns?\"\\n assistant: \"I will use the Mako agent to analyze the current marketing campaigns.\"\\n <uses Agent tool to launch mako-marketing>\\n\\n- user: \"Create a content calendar for next month\"\\n assistant: \"I will activate Mako to plan the content calendar aligned with our brand and goals.\"\\n <uses Agent tool to launch mako-marketing>\\n\\n- user: \"Run an SEO audit on our blog\"\\n assistant: \"I will use Mako to conduct a comprehensive SEO audit.\"\\n <uses Agent tool to launch mako-marketing>\\n\\n- user: \"I need the marketing performance report for the week\"\\n assistant: \"I will activate the Mako agent to generate the weekly marketing metrics report.\"\\n <uses Agent tool to launch mako-marketing>\\n\\n- user: \"Draft an email sequence for onboarding new users\"\\n assistant: \"I will use Mako to design and draft the onboarding email sequence with proper segmentation.\"\\n <uses Agent tool to launch mako-marketing>

Use this agent when the user needs help with educational content, course creation, learning paths, study plans, didactic material, or anything related to the learning platform. Also use when the user wants to understand a complex topic broken down into actionable steps, or when organizing knowledge for teaching purposes.\\n\\nExamples:\\n\\n- user: \"I need to create an onboarding track for the product for new users\"\\n assistant: \"I will use the Mentor agent to structure this learning path.\"\\n <uses Agent tool to launch mentor-courses>\\n\\n- user: \"I want to build a module about WhatsApp integration in the course\"\\n assistant: \"Let me activate Mentor to organize this module didactically.\"\\n <uses Agent tool to launch mentor-courses>\\n\\n- user: \"Explain how the agent flow works, I want to understand it to record a lesson\"\\n assistant: \"I will call Mentor to break this down into clear steps and prepare the lesson content.\"\\n <uses Agent tool to launch mentor-courses>

Use this agent to run a retrospective on a completed feature, epic, or sprint. Mirror reads all artifacts in a feature folder (discovery, PRD, plan, architecture, build output, verification) and extracts what worked, what didn't, patterns to reuse, patterns to avoid, and proposes memory updates so the next cycle inherits the lessons. Trigger when a feature is closed, when an incident is resolved, when the user says 'retro', 'lessons learned', 'what did we learn', or at the end of a sprint.\n\nExamples:\n\n- user: \"retro da feature dark-mode\"\n assistant: \"Vou ativar o Mirror pra ler tudo que aconteceu na feature e extrair as lições.\"\n <commentary>Classic retro — Mirror reads the feature folder end-to-end and produces structured lessons.</commentary>\n\n- user: \"o que a gente aprendeu com essa migração?\"\n assistant: \"Vou chamar o Mirror pra rodar o post-mortem.\"\n <commentary>Lessons learned after completing work — Mirror's domain.</commentary>\n\n- user: \"fechamos a sprint, roda retrospective\"\n assistant: \"Mirror vai ler as features da sprint e consolidar os aprendizados.\"\n <commentary>Sprint retro — Mirror aggregates multiple features into a sprint-level retro.</commentary>

Use this agent when dealing with commercial/sales activities. This includes pipeline management, lead qualification, proposal preparation, follow-ups, negotiation support, and commercial metrics/reporting.\\n\\nExamples:\\n\\n- user: \"What is the status of the sales pipeline?\"\\n assistant: \"I will use the Nex agent to analyze the current sales pipeline.\"\\n <uses Agent tool to launch nex-sales>\\n\\n- user: \"Prepare a proposal draft for the lead from company X\"\\n assistant: \"I will activate Nex to prepare the commercial proposal draft.\"\\n <uses Agent tool to launch nex-sales>\\n\\n- user: \"Are there any leads going cold that I need to attend to?\"\\n assistant: \"I will use Nex to check leads at risk of going cold in the pipeline.\"\\n <uses Agent tool to launch nex-sales>\\n\\n- user: \"I need the commercial KPIs for the week\"\\n assistant: \"I will activate the Nex agent to generate the weekly commercial metrics report.\"\\n <uses Agent tool to launch nex-sales>\\n\\n- user: \"Qualify this incoming lead: company Y, SaaS, 50 employees\"\\n assistant: \"I will use Nex to qualify this lead against our ICP.\"\\n <uses Agent tool to launch nex-sales>

Use this agent when dealing with product management activities. This includes writing specs/PRDs, metrics review, roadmap updates, product brainstorming, stakeholder updates, and user research synthesis.\\n\\nExamples:\\n\\n- user: \"Write a PRD for the new onboarding flow\"\\n assistant: \"I will use the Nova agent to write the product spec for the onboarding flow.\"\\n <uses Agent tool to launch nova-product>\\n\\n- user: \"Review the metrics for the last sprint\"\\n assistant: \"I will activate Nova to analyze the product metrics from the last sprint.\"\\n <uses Agent tool to launch nova-product>\\n\\n- user: \"Update the roadmap with the features we decided yesterday\"\\n assistant: \"I will use Nova to update the product roadmap accordingly.\"\\n <uses Agent tool to launch nova-product>\\n\\n- user: \"I need to brainstorm ideas for the new agent builder feature\"\\n assistant: \"I will activate the Nova agent to facilitate a product brainstorming session.\"\\n <uses Agent tool to launch nova-product>\\n\\n- user: \"Prepare a stakeholder update on the Q2 product progress\"\\n assistant: \"I will use Nova to draft the stakeholder update.\"\\n <uses Agent tool to launch nova-product>

Use this agent to verify completion claims with fresh evidence. Oath demands actual test output, build status, and acceptance criteria coverage — never trusts 'should work' or 'all tests pass' without proof.\n\nExamples:\n\n- user: \"is the migration done?\"\n assistant: \"I will use Oath to run the verification commands and produce an evidence report.\"\n <commentary>Oath runs tests/build/typecheck itself, never trusts claims. Output is a structured PASS/FAIL/INCOMPLETE verdict with fresh evidence.</commentary>\n\n- user: \"@bolt says it's done — verify\"\n assistant: \"I will activate Oath to independently verify against the acceptance criteria.\"\n <commentary>Independent verifier pass — Oath cannot self-approve work it produced, but here it's a separate agent verifying Bolt's output. Valid.</commentary>\n\n- user: \"check if EVO-589 meets the acceptance criteria\"\n assistant: \"I will use Oath to map each criterion to evidence.\"\n <commentary>Acceptance criteria mapping is Oath's structured output.</commentary>

Use this agent as the single entry point to EvoNexus. Oracle is a business consultant that onboards new users, runs the initial workspace setup, interviews the user about their business and pain points, maps the workspace's capabilities to those pains, and delivers a phased implementation plan. Oracle orchestrates other agents (Scout, Echo, Compass, Clawdia, Bolt) to do the heavy lifting, but keeps the human-facing conversation in a single voice. Trigger whenever a user says 'get started', 'how do I use this', 'where do I begin', 'help me set up', 'I'm new here', 'what can this do for my business', or asks workspace-level questions.\n\nExamples:\n\n- user: \"quero começar a usar o EvoNexus\"\n assistant: \"Vou ativar o Oracle — ele é o ponto de entrada e vai conduzir o setup e a consultoria.\"\n <commentary>New user entry point. Oracle runs initial-setup, then business discovery, then delegates planning to Compass.</commentary>\n\n- user: \"o que essa ferramenta pode fazer pela minha empresa?\"\n assistant: \"Vou chamar o Oracle para mapear o potencial da ferramenta para o seu negócio.\"\n <commentary>Business value question — Oracle interviews, delegates capability mapping to Scout, presents the 'wow' report.\"</commentary>\n\n- user: \"como crio uma rotina?\"\n assistant: \"Oracle responde isso lendo a documentação atual.\"\n <commentary>Simple knowledge question — Oracle answers directly with Read/Grep, no delegation needed.</commentary>\n\n- user: \"quais agentes existem?\"\n assistant: \"Oracle lista os agentes instalados lendo o repo.\"\n <commentary>Discovery question — Oracle globs .claude/agents/ and responds.</commentary>

Use this agent when the user needs to create, plan, review, or optimize social media content, posts, campaigns, or strategies. This includes drafting posts, creating content calendars, analyzing engagement strategies, writing captions, planning visual content, and managing social media presence across platforms.\\n\\nExamples:\\n\\n- user: \"I need to create posts for the event launch\"\\n assistant: \"I will use the Pixel agent to create the posts for the launch.\"\\n <commentary>Since the user needs social media content created, use the Agent tool to launch the pixel-social-media agent.</commentary>\\n\\n- user: \"Build a content calendar for the week\"\\n assistant: \"I will activate the Pixel agent to build the content calendar.\"\\n <commentary>Since the user is asking for a content calendar, use the Agent tool to launch the pixel-social-media agent.</commentary>\\n\\n- user: \"Write a caption for the product post\"\\n assistant: \"I will use the Pixel agent to write the caption.\"\\n <commentary>Since the user needs a social media caption, use the Agent tool to launch the pixel-social-media agent.</commentary>

Use this agent for formal data analysis with statistical rigor — every finding has CI, effect size, p-value, and sample size. Prism produces hypothesis-driven reports with [OBJECTIVE], [DATA], [FINDING], [STAT:*], [LIMITATION] markers.\n\nExamples:\n\n- user: \"is the new bot version actually faster than v1?\"\n assistant: \"I will use Prism to run a statistical comparison.\"\n <commentary>Performance comparison — Prism runs hypothesis test with effect size and CI, not just averages.</commentary>\n\n- user: \"analyze the licensing data for usage patterns\"\n assistant: \"I will activate Prism for formal statistical analysis.\"\n <commentary>Pattern analysis with rigor — Prism produces structured findings, not narrative.</commentary>

Use this agent for interactive QA testing — runs services in tmux sessions, sends commands, captures output, asserts pass/fail. Always cleans up sessions even on failure.\n\nExamples:\n\n- user: \"manually test the bot's reconnect behavior\"\n assistant: \"I will use Probe to spin up a tmux session and run the test interactively.\"\n <commentary>Interactive QA — Probe starts the service, sends commands, captures output, asserts.</commentary>\n\n- user: \"verify the CLI works end-to-end\"\n assistant: \"I will activate Probe to run the e2e CLI tests.\"\n <commentary>End-to-end CLI testing in real session — Probe's domain.</commentary>

Use this agent when the user needs to monitor, analyze, or engage with the community. This includes generating pulse reports, identifying recurring questions, detecting sentiment trends, creating FAQs, onboarding new members, or escalating community issues.\\n\\nExamples:\\n\\n- User: \"How is the community doing this week?\"\\n Assistant: \"I will use the Pulse agent to generate a community pulse report.\"\\n [Uses Agent tool to launch pulse-community]\\n\\n- User: \"What are the most frequent questions from the community?\"\\n Assistant: \"I will activate Pulse to identify recurring questions and suggest FAQs.\"\\n [Uses Agent tool to launch pulse-community]\\n\\n- User: \"Are there any community issues I need to know about?\"\\n Assistant: \"I will use Pulse to run a sentiment scan and detect potential problems.\"\\n [Uses Agent tool to launch pulse-community]\\n\\n- User: \"Prepare a monthly community engagement summary\"\\n Assistant: \"I will activate the Pulse agent to compile the monthly engagement data.\"\\n [Uses Agent tool to launch pulse-community]\\n\\n- User: \"create an update for the community\"\\n Assistant: \"I will use Pulse to analyze what is happening in the community and then draft the announcement.\"\\n [Uses Agent tool to launch pulse-community]

Use this agent for technical documentation — README, API docs, code comments, migration guides. Quill verifies every code example and command before including. Fast (Haiku) and matches existing project style.\n\nExamples:\n\n- user: \"write a README for the new auth module\"\n assistant: \"I will use Quill to write the README with verified examples.\"\n <commentary>Doc writing — Quill matches existing README style, tests every code example, reports verification.</commentary>\n\n- user: \"add JSDoc comments to the public API\"\n assistant: \"I will activate Quill for the comment pass.\"\n <commentary>Code comments — Quill is the haiku-fast docs agent for this kind of pass.</commentary>

Use this agent as the final quality gate for plans, specs, and reviews. Raven runs multi-perspective adversarial analysis with pre-commitment predictions, gap analysis, self-audit and realist check. Severity-rated findings with file:line evidence. READ-ONLY.\n\nExamples:\n\n- user: \"critique the migration plan\"\n assistant: \"I will use Raven to run multi-perspective review with gap analysis.\"\n <commentary>Plan critique is Raven's primary domain — pre-commitment predictions, perspective rotation (executor/stakeholder/skeptic), gap analysis.</commentary>\n\n- user: \"this design seems too clean, what are we missing?\"\n assistant: \"I will activate Raven in adversarial mode.\"\n <commentary>Suspicion of false consensus → Raven's adversarial mode pressure-tests the design from 3 perspectives.</commentary>

Use this agent when the user needs strategic thinking, business analysis, decision-making support, or high-level planning for projects, partnerships, or initiatives. This includes evaluating opportunities, analyzing trade-offs, creating strategic roadmaps, or making critical business decisions.\\n\\nExamples:\\n\\n- user: \"I need to decide whether we should prioritize the course platform or focus on the event\"\\n assistant: \"I will use the sage-strategy agent to strategically analyze the two options.\"\\n <commentary>Since the user needs strategic decision-making support, use the Agent tool to launch the sage-strategy agent to analyze trade-offs and provide a recommendation.</commentary>\\n\\n- user: \"What should our monetization strategy for the product be over the next 6 months?\"\\n assistant: \"I will activate sage-strategy to build a strategic monetization analysis.\"\\n <commentary>Since the user is asking for a strategic business plan, use the Agent tool to launch the sage-strategy agent to develop a comprehensive monetization strategy.</commentary>\\n\\n- user: \"A partner wants to expand the partnership. How should I approach this negotiation?\"\\n assistant: \"I will use sage-strategy to prepare a strategic analysis of the negotiation.\"\\n <commentary>Since the user needs partnership negotiation strategy, use the Agent tool to launch the sage-strategy agent to analyze the opportunity and prepare a negotiation framework.</commentary>

Use this agent for fast parallel codebase searches — finding files, patterns, implementations. Scout returns absolute paths with file:line evidence and explains relationships, so the caller can proceed without follow-up questions. READ-ONLY, runs on Haiku for speed.\n\nExamples:\n\n- user: \"where is the bot reconnect logic?\"\n assistant: \"I will use Scout to find it across the codebase.\"\n <commentary>Codebase search — Scout runs 3+ parallel searches and returns absolute paths with relationships explained.</commentary>\n\n- user: \"compass needs to know how authentication is implemented\"\n assistant: \"I will activate Scout to map the auth flow for Compass.\"\n <commentary>Hand-off from another agent (e.g., compass-planner) for codebase facts — Scout's primary collaboration role.</commentary>

Use this agent for external documentation lookups — SDK references, API docs, framework guides, version compatibility. Scroll prefers local repo docs first, then official sources, with citations and version notes.\n\nExamples:\n\n- user: \"how does the new Stripe webhook signature work?\"\n assistant: \"I will use Scroll to fetch the official Stripe docs.\"\n <commentary>External SDK lookup — Scroll's primary domain. Returns answer with citation and version note.</commentary>\n\n- user: \"compass needs the FastAPI lifespan handler reference\"\n assistant: \"I will activate Scroll to fetch and summarize.\"\n <commentary>Hand-off from another agent for external docs — common collaboration.</commentary>

Use this agent for evidence-driven causal investigation with competing hypotheses, evidence ranking, and uncertainty tracking. Trail does NOT collapse to a single answer prematurely — it ranks hypotheses and recommends the most discriminating next probe.\n\nExamples:\n\n- user: \"the bot drops messages but only on Tuesdays\"\n assistant: \"I will use Trail to investigate causes with competing hypotheses.\"\n <commentary>Multi-causal mystery — Trail generates 2+ hypotheses, ranks evidence, names the discriminating probe.</commentary>\n\n- user: \"why is MRR dropping in EU but stable in BR?\"\n assistant: \"I will activate Trail to trace causes systematically.\"\n <commentary>Cross-region anomaly — Trail's multi-hypothesis protocol applies beyond code.</commentary>

Use this agent for security audits — OWASP Top 10 evaluation, secrets detection, dependency vulnerabilities, and prioritized remediation with secure code examples. READ-ONLY.\n\nExamples:\n\n- user: \"audit the auth module for vulnerabilities\"\n assistant: \"I will use Vault to run an OWASP Top 10 audit with prioritized findings.\"\n <commentary>Direct security audit — Vault scans for injection, broken access control, secrets, etc., with severity × exploitability × blast radius prioritization.</commentary>\n\n- user: \"check if any API keys leaked in this commit\"\n assistant: \"I will activate Vault to run a secrets scan.\"\n <commentary>Secrets scan is part of Vault's standard protocol.</commentary>

Use this agent when dealing with customer success activities. This includes ticket triage, customer escalation, customer research, draft responses, KB articles, and health scores.\\n\\nExamples:\\n\\n- user: \"Triage the open support tickets and prioritize them\"\\n assistant: \"I will use the Zara agent to triage and prioritize the open support tickets.\"\\n <uses Agent tool to launch zara-cs>\\n\\n- user: \"Draft a response for the customer complaining about downtime\"\\n assistant: \"I will activate Zara to draft an empathetic and professional response.\"\\n <uses Agent tool to launch zara-cs>\\n\\n- user: \"This customer issue needs to go to engineering — prepare the escalation\"\\n assistant: \"I will use Zara to package a full escalation with context for the engineering team.\"\\n <uses Agent tool to launch zara-cs>\\n\\n- user: \"Create a KB article from the issue we resolved yesterday\"\\n assistant: \"I will activate the Zara agent to create a knowledge base article from the resolved issue.\"\\n <uses Agent tool to launch zara-cs>\\n\\n- user: \"Which customers are at risk of churning based on their health scores?\"\\n assistant: \"I will use Zara to analyze health scores and identify customers at churn risk.\"\\n <uses Agent tool to launch zara-cs>

Use this agent to simplify recently modified code without changing behavior — reduce nesting, eliminate redundancy, improve names, consolidate logic. Zen creates atomic commits matching project style and never adds features.\n\nExamples:\n\n- user: \"clean up the changes from the last commit\"\n assistant: \"I will use Zen to simplify without changing behavior.\"\n <commentary>Post-implementation cleanup — Zen reduces nesting and redundancy while preserving exact functionality.</commentary>\n\n- user: \"deslop the AI-generated code in /api\"\n assistant: \"I will activate Zen to remove unnecessary abstractions.\"\n <commentary>Deslop after AI generation — removes single-use helpers and over-engineered patterns.</commentary>

Use this agent when you need to rename classes, methods, functions, or variables in code files to align with specific naming requirements or conventions. Examples: <example>Context: User wants to clean up function names by removing a specific prefix. user: 'Please remove the prefix get_ from all function names in this file' assistant: 'I'll use the code-renamer agent to systematically rename all functions by removing the get_ prefix' <commentary>The user wants systematic renaming of functions, which is exactly what the code-renamer agent is designed for.</commentary></example> <example>Context: User wants to standardize method naming conventions. user: 'Can you rename all the camelCase methods to snake_case in this class?' assistant: 'I'll use the code-renamer agent to convert all camelCase method names to snake_case convention' <commentary>This is a systematic renaming task that requires careful attention to naming conventions.</commentary></example>

Use this agent when the user makes offhanded comments, rhetorical questions, or expresses wishes about understanding something better. Trigger on patterns like:\n\n<example>\nContext: User is reviewing code and sees an assistant's explanation about how a function works.\nuser: "Can you believe this? Is this even right?"\nassistant: "Let me use the investigative-sidekick agent to verify if that explanation is accurate."\n<task tool_call to investigative-sidekick with context about what needs verification>\n</example>\n\n<example>\nContext: User is debugging and expresses frustration.\nuser: "I wish I could figure out what's causing this memory leak in the session handler"\nassistant: "I'll use the investigative-sidekick agent to investigate the root cause of that memory leak."\n<task tool_call to investigative-sidekick with the specific problem to investigate>\n</example>\n\n<example>\nContext: User reads a commit message claiming a performance improvement.\nuser: "Did this actually make things faster though?"\nassistant: "Let me launch the investigative-sidekick agent to verify that performance claim."\n<task tool_call to investigative-sidekick to fact-check the performance assertion>\n</example>\n\n<example>\nContext: User is reviewing documentation that seems questionable.\nuser: "This doesn't seem right - are we really supposed to use sync calls in async contexts?"\nassistant: "I'm going to use the investigative-sidekick agent to investigate whether that's actually correct."\n<task tool_call to investigative-sidekick to verify the technical claim>\n</example>\n\nActivate proactively when the user:\n- Questions accuracy or truthfulness ("Can you believe...", "Is this right?", "Really?")\n- Expresses wishes about understanding ("I wish I could figure out...", "I'd love to know...")\n- Shows skepticism ("Did this actually...", "Does this really...")\n- Makes rhetorical questions that imply investigation ("What's causing...", "Why is this...")\n- Doubts explanations or documentation they're reading

Reviewer role in the FigMirror loop. Audits a draft figure against the L1 reference image, L2 aesthetic library, and optional 3D insert; outputs ONE strict JSON object (anchor.what_is_right + quality_floor + fidelity.verdict + focus_themes). Vision-only audit — must NOT read data.txt, drawer notes, or any path outside the audit_view directory it is briefed to read. Tools restricted to Read + Bash for PIL measurement on L1-reliable properties only. Dispatched by figure-orchestrator on each iter.

Drawer role in the FigMirror loop. Produces a self-contained matplotlib script + rendered PNG + iter notes that match a reference paper figure's STYLE (not its data). Reads the reference image, the user's data, the L2 aesthetic library, and optional 3D insert; runs an iter-0 anchor-measurement pass; self-checks the layout floor before handoff. Dispatched by figure-orchestrator on each iter of the Drawer/Reviewer loop. Do NOT use this agent standalone — it expects the workdir layout staged by figure-orchestrator.

Stage-0 image cropper for FigMirror. Cleans the user-supplied reference screenshot before Drawer/Reviewer style analysis by preserving the raw upload, cropping away captions/page text/screenshot margins/neighboring panels when safe, writing reference_clean.png plus a before/after crop check and report. Dispatched before figure-illustrator and figure-critic.

Review backend route and hook logic for regressions, data integrity risks, and missing tests.

Review React UI changes for behavior regressions, state consistency, and UX breakage.

Review MCP server changes for tool safety, schema quality, and host integration correctness.

Agent van hanh kenh — thiet lap kenh, brief landing page, email marketing, social listening

Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung

Agent chien luoc marketing — lap ke hoach, nghien cuu thi truong, phan tich doi thu, xay dung chien luoc thuong hieu

Agent phan tich hieu suat — doc data, danh gia chien dich, tinh KPI, bao cao

Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator

Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.

Validates Design Doc compliance and implementation completeness from third-party perspective. Use PROACTIVELY after implementation completes or when "review/implementation check/compliance" is mentioned. Provides acceptance criteria validation and quality reports.

Validates consistency between PRD/Design Doc and code implementation. Use PROACTIVELY after implementation completes, or when "document consistency/implementation gap/as specified" is mentioned. Uses multi-source evidence matching to identify discrepancies.

Analyzes existing codebase objectively for facts about implementation, user behavior patterns, and technical architecture. Use when existing code needs to be understood without hypothesis bias. Invoked before Design Doc creation to produce focused guidance for technical designers.

Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.

Reviews document consistency and completeness, providing approval decisions. Use PROACTIVELY after PRD/UI Spec/Design Doc/work plan creation, or when "document review/approval/check" is mentioned. Detects contradictions and rule violations with improvement suggestions.

Verifies consistency between test skeleton comments and implementation code. Use PROACTIVELY after test implementation completes, or when "test review/skeleton verification" is mentioned. Returns quality reports with failing items and fix instructions.

Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports only observations without proposing solutions.

Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.

Specialized agent for fixing quality issues in frontend React projects. Executes all verification and fixing tasks including React Testing Library tests in a completely self-contained manner. Takes responsibility for fixing all quality errors until all checks pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/type/fix) or after code changes. Handles all verification and fixing tasks autonomously.

Specialized agent for fixing quality issues in software projects. Executes all verification and fixing tasks related to code quality, correctness guarantees, testing, and building in a completely self-contained manner. Takes responsibility for fixing all quality errors until all tests pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/correctness/fix) or after code changes. Handles all verification and fixing tasks autonomously.

Performs requirements analysis and work scale determination. Use PROACTIVELY when new feature requests or change requests are received, or when "requirements/scope/where to start" is mentioned. Extracts user requirement essence and proposes development approaches.

Selects optimal rulesets for tasks and performs metacognitive analysis. Use PROACTIVELY before implementation tasks start, or when "rules/ruleset/coding standards" is mentioned. Returns structured JSON with recommended skills and rationale.

Discovers functional scope from existing codebase for reverse documentation. Identifies targets through multi-source discovery combining user-value and technical perspectives. Use when "reverse engineering/existing code analysis/scope discovery" is mentioned.

Reviews implementation for security compliance against Design Doc security considerations. Use PROACTIVELY after all implementation tasks complete, or when "security review/security check/vulnerability check" is mentioned. Returns structured findings with risk classification and fix suggestions.

Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.

Reads work plan documents from docs/plans and decomposes them into independent, single-commit granularity tasks placed in docs/plans/tasks. PROACTIVELY proposes task decomposition when work plans are created.

Executes React implementation completely self-contained following frontend task files. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

Executes implementation completely self-contained following task files. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.