Teamwork Update
Use when updating Teamwork package version, refreshing installed skills/agents/global policy, checking install freshness, or release metadata.
Using Teamwork
Use when Teamwork is explicitly requested, work must cross Teamwork stages, or the correct next stage is unclear; route to native/research/debug/plan/execute/review/goal/init/update.
Grill Me
Use when the user explicitly asks to be grilled, requests question-first plan or design stress-testing, or continues an active grill session; ask zero to three material user-owned decision questions and never manufacture implementation trivia.
Teamwork Debug
Use when the user reports a failure, flaky test, CI error, runtime log, crash, UI symptom, regression, or suspected bug where a repro, hypotheses, instrumentation, browser/CI evidence, or human observation must decide root cause before a fix is safe.
Teamwork Plan
Use when the user asks for plan/design or a non-trivial research, engineering, or implementation change needs scope, requirements, protected boundaries, verification, dispatch, memory, or acceptance before action.
Teamwork Review
Use when the user asks to review/check a plan, artifact, diff, implementation, research output, completion claim, strict quality, deslop pass, PR walkthrough, or acceptance evidence.
Teamwork Init
Use when setting up, auditing, or slimming project agent instructions; integrating Teamwork artifacts, MCP/CodeGraph policy, AGENTS/CODEX/CURSOR/CLAUDE rules, install readiness, or reusable workflow-rule migration.
Teamwork Goal
Use when the user asks to keep going, run until it passes, fix until green, iterate until done, converge on a verifiable target, or work within an explicit budget.
Teamwork Execute
Use when an accepted plan, checklist, approved scope, or known root-cause fix should be implemented, continued, resumed, or verified with focused action.
Teamwork Research
Use when the next safe step is to learn before acting: source-of-truth lookup, current API behavior, repro-surface framing, option comparison, stale-assumption refresh, or risk/evidence gathering before planning/debugging.