PROACTIVELY use this before a production release — "prepare to ship", "pre-launch check", "rollout plan needed". Runs the pre-launch checklist, plans staged rollout, defines rollback. Do NOT use for day-to-day deploys of a trusted pipeline (they should pass the checklist automatically).
PROACTIVELY use this before starting a new feature, project, or change that touches multiple files when no spec exists yet. Writes a structured spec, surfaces assumptions BEFORE any code, produces acceptance criteria. Do NOT use for typo fixes, single-line changes, or unambiguous small tasks.
PROACTIVELY use this when the user asks "what's untested", "find coverage gaps", "which symbols have zero tests", or wants to plan a testing sprint. Enumerates exported symbols, cross-checks against test-file references, returns a prioritised gap list.
PROACTIVELY use this when the user reports failing tests, asks to investigate a red CI, or says "these tests are broken / flaky". Identifies root cause and suggests minimal fix — no speculation. Do NOT use to write new tests (that's tp-test-writer).
PROACTIVELY use this when the user asks to write, add, or cover a SPECIFIC function / method / class with tests ("add test for X", "cover Y"). Mirrors project's existing test style; runs the tests before declaring done. Do NOT use for diagnosing failures (that's tp-test-triage).
Runs before the agent uses a tool for Read, Edit, MultiEdit, Bash, Grep and Task tool calls, executing run.sh via sh (6 commands). From Digital-Threads/token-pilot.