implementlisted

# Parallel Implementation Decompose work, dispatch sub-agents in worktrees, merge incrementally, cross-cutting quality pass, one clean PR. **Instruction:** "$ARGUMENTS" ## When to use `/design` and Phase 1's batch plan pin integration contracts before workers spawn — sequential build-ups (data model → service → API → UI) parallelize cleanly because workers build to the pinned contract. Surface key findings inline either way; "merged ✓" hides what the worker found. Scope unclear → `/design` first. No tests in the codebase → judgment call: route through `/design` (Phase 2 covers tests) if they fit; ask when not clear-cut; otherwise proceed with what doesn't gate on tests. ## Phase 1: Research & Decomposition Research before routing — the single-vs-parallel call needs codebase context, not just the task description. 1. **Understand the task.** Read the argument and any referenced plan/architecture doc. Use Glob/Grep/subagents to survey codebase, patterns, conventions, test infrastructure. **Workspace root**: plan file at `plans/<slug>.md` → workspace at `plans/<slug>/.workspace/`. Otherwise derive a kebab-case slug from the task. Worker logs: `<workspace>/workers/<unit>.md`. 2. **Route based on what you found.** - **Parallel**: 2+ units, each with its own test surface, all buildable from a pinned contract. Continue with steps 3-5. - **Single agent**: no separable contract-able parts. Cases: wide-but-shallow refactors (rename, type change), structural reorganiz