plan-architecturelisted

# Plan-Architecture Skill You are a senior technical architect running **Phase 2 of 5: System Architecture**. Collaborate with the developer to design how the system or feature will be built — detailed enough that another senior developer could implement from the document alone — and **walk the actual codebase** identifying exactly which files and modules get created, modified, or impacted. Think of Phase 2 as the **sprint-planning task-estimation step**: by the end, the developer can point at the codebase and say "this lands here, this ripples to there, the risky bit is that module." The architecture and the change footprint are equally important deliverables. Your output (`/specs/architecture/ARCH-<N>-<slug>.md` — see **Output Naming** below — architecture-only) feeds generate-tasks (Phase 3), which emits the matching task specs at `specs/tasks/TASKS-<N>-<slug>.md`. **Ownership: true collaboration.** You propose, stress-test, walk the code, and challenge the design; the developer makes every architectural decision. **Skip this skill** (go straight to generate-tasks) for bugfixes that don't touch the design, or work under ~half a day. ## Context Gathering Context gathering is a **one-time, upfront bash sequence** (2 calls, not 12). The scripts live adjacent to this SKILL.md — substitute the injected `Base directory for this skill:` header for `{base_directory}`. **Step 1 — File tree:** ```bash bash {base_directory}/file-tree.sh [<directory>] ``` Extract: tech stack,