planninglisted

# `/dotclaude:planning` — pre-implementation discipline kit You are setting up the pre-impl half of the validation loop. The output is a `.claude/` subset focused on what happens BEFORE code is written: territory mapping, integration-point analysis, parallel-path detection, cross-boundary verification, and the routing rule that decides which audit agent fires for which question once the user's `.claude/` accumulates more than 2-3 of them. `/dotclaude:coding` ships the post-impl reviewer; this skill ships its pre-impl companion + the routing layer that organizes them. ## Phase 1 — Read the project's coupling shape Before any question: 1. **Module / package layout** — top-level structure: ```bash ls -la ls packages/ workspaces/ apps/ services/ lib/ src/ 2>/dev/null ``` Count the modules. Note whether this is a monorepo (multiple `package.json` / `Cargo.toml` / `pyproject.toml`), a workspace, or a flat single-package project. 2. **Cross-module change frequency** — read the git log for multi-module PRs: ```bash git log --merges --oneline -30 git log --oneline --stat -50 | head -200 ``` Look for commits / merges that touch files in 3+ different top-level directories. These are the kinds of changes pre-flight earns its keep on. 3. **Revert / rollback history** — design mistakes that shipped: ```bash git log --oneline --grep="revert" -30 git log --oneline --grep="rollback" -30 ``` Each revert is a pre-flight gap that wasn't caught.