Work

When you need Claude to actually ship something, this skill orchestrates the full cycle: parse your request, decide if it's simple enough to handle directly or complex enough to warrant spinning up a team of subagents, implement across however many files it touches, then run a mandatory code-polish pass at the end. The complexity heuristic is practical: file count, cross-module changes, new dependencies, risk surface. It's opinionated about when parallelism actually helps versus just adding coordination overhead. The team coordination logic handles conflicts and integration checks after subagents finish. Always ends with polish, no exceptions. Good for when you want to hand off a feature or refactor and trust the orchestration to handle scope creep and verification.