tavaresgmg

MUST use for substantial evidence-driven research, analysis, decisions, planning, review, artifact, operational, or software work. Use native subagents for independent branches that save wait or isolate noise. Skip simple calculations or transformations, stable facts, free ideation, and tiny known paths.

Calculate campaign contribution from revenue, direct spend, and refunds, then compare options using current data.

Persist or resume unfinished Groundcraft work only for explicit cross-thread handoff or when native thread continuity is unavailable. Never scan it per task or use it for completed work.

Code refactoring engine that improves clarity, consistency, and maintainability while preserving exact functionality. Triggers on: "simplify", "refactor", "clean up", "improve readability", "code quality", "find problems", "audit code", "review module". Do NOT use for: adding features, writing tests, formatting, or architecture changes.

Routes software development work in or around a repo/workspace to the lightest safe workflow that still protects correctness. ALWAYS invoke for build, change, fix, refactor, plan, investigate, research, cleanup, reduce complexity, align with repo patterns, spec, implement, greenfield-in-repo work, or any card/issue/ticket/link/screenshot/bug/rough idea (pt-BR: implementar, criar, corrigir, refatorar, ajustar, planejar, pesquisar, investigar, limpar, reduzir complexidade, analisar). Skip pure/read-only Q&A, explain/summarize/list/open-only requests, one-off shell commands, or tasks owned by a more specific active skill.