planlisted

# Plan Decompose or challenge a task before implementation begins. ## 1. Determine what the user needs - **"I have a task I don't know how to approach"** → decompose with tech-lead (step 2) - **"I have a plan I want to pressure-test"** → challenge with devils-advocate (step 3) - **"Both"** → run tech-lead first (step 2), then devils-advocate on the result (step 3) If unclear, ask: "Do you have a plan already, or do you need one decomposed first?" ## 2. tech-lead — task decomposition (if needed) Invoke tech-lead with the full task description. Pass any constraints, related files, or architectural context. tech-lead reads `memory/architecture/repo-map.md` (if present) to accelerate routing and blast-radius assessment — if you already know the repo structure has changed a lot recently, suggest `/repo-map refresh` first so the plan is built against an accurate map. **Instruct tech-lead to write a plan file, and pass it the resolved plan directory.** tech-lead writes a plan file only when told to, so this instruction is what creates the artifact. Resolve the directory first: ```bash grep -m1 '^- \*\*Plan directory:\*\*' docs/CONVENTIONS.md 2>/dev/null | sed 's/^.*\*\*Plan directory:\*\*[[:space:]]*//' ``` Fall back to `docs/plans` when that returns nothing, or when the value fails **any condition in the guard table in `agents/tech-lead.md`** — read that table rather than working from a list here. It is the single authority on what is rejected, and a copy in this file woul