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. The tech-lead will: - Identify which specialist agents are needed - Determine the correct invocation order (sequential vs. parallel) - Surface whether devils-advocate should run before implementation - Produce a step-by-step plan with rationale for each step Present the plan clearly to the user. If it introduces a new pattern, a new dependency, or an irreversible architectural change, recommend running step 3 before proceeding. ## 3. devils-advocate — pressure-test (if warranted) Invoke devils-advocate with: - The full plan or proposal - Any alternatives already considered and why they were rejected - Any constraints, requirements, or deadlines that shaped the decision The devils-advocate will surface unconsidered alternatives, challenge hidden assumptions, and identify risks. After it completes: 1. Present the key concerns raised clearly. 2. Ask: "Proceed with th