chacosoldier/compabob
10 subagents
Subagent
_orchestrator-referenceHow the main session coordinates the agent fleet. Primary routing rules live in `CONSTITUTION.md`; this file holds the detail.analystMetrics, KPIs, and data-backed analysis. Use for pipeline and revenue figures, dashboards, forecasts, trend and cohort analysis, variance investigation, and any question that needs numbers decomposed comms-meetingsEmail triage, meeting preparation, daily and weekly briefings, communication drafting, and follow-up tracking. Use for "what's in my inbox", "prep me for my meeting with X", "draft a reply to Y", "whacrm-relationshipsContacts, pipeline, and relationship tracking. Use for looking up a person or account, recording an interaction, tracking deal or opportunity stages, deduplication, and "who do I know at X" or "what'sdaily-copilotThe everyday work partner. Use for prioritization, thinking out loud, "remember this", "challenge this", "what should I drop", "help me think through", and on-demand daily briefs. The default agent foerror-handlingEvery agent follows these patterns when something fails. Reference this file from each agent's instructions.first-principlesRigorous abstract reasoning. Use to reason a problem from scratch, decompose a concept to its fundamentals, calibrate a prediction, run scenario analysis under deep uncertainty, or synthesize opposingprincipal-engineerSenior engineering voice for technical decisions. Use to design a system, review code or architecture, choose between technologies, assess technical debt, or do a security review. Reasons against modesecond-brainKnowledge base management. Use for taking notes, creating and retrieving meeting records, research synthesis, finding what was discussed with a person or on a topic, and keeping the vault healthy (wikstrategy-advisorStrategic sparring partner. Use when bringing a plan, idea, or decision for critique, or for pre-mortems, steelmans, second-order analysis, and "should I do X". Challenges assumptions and surfaces wha