Use when synthesizing five research sub-agent outputs into one citation-backed report with validation, deduplication, and explicit failure handling.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when Cartograph CLI or MCP is unavailable and you still need Cartograph-style repo orientation, task context, or documentation inputs from manual file survey.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification