autoplan

# Autoplan One lazy entry point for the whole catalog. Classify the request, route it, apply defaults, and only stop for decisions that are genuinely the user's. Models and people do not hand-route across dozens of skills; this skill does. ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `/autoplan` followed by the request text | Classify and route the request | | `do it` | Classify and route the current request | | `handle it` | Classify and route the current request | | `figure this out` | Classify, then report the route before running | | `your call` | Classify, then report the route before running | The router also fires implicitly. Any concrete request that names no skill routes through the table below instead of defaulting to a bare answer, for example "why is CI failing", "investigate the flaky test", or "redo #1723 properly". These phrases are grounded in this repo's own Copilot and Claude session history. The dominant real openers are continue, proceed, investigate, fix the X, do it, and handle it, not ceremonial delegation phrases. Continue and proceed are deliberately excluded as hard triggers: they mean resume the in-flight work, so they route to whatever is already running rather than re-classifying from scratch. ## Process ### Phase 0: Recon the target Before you classify, establish the target repository's stack. Do not assume the stack of the repo this skill ships from (Python-first). The target may be C#, TypeScript, Go, Rus...