plan-preparationlisted

# Plan Preparation Skill Phases 1.0 through 1.4: take a ticket from raw requirements to a fully researched, impact-analyzed, user-approved foundation ready for planning. Every phase builds on the previous one. No shortcuts — gaps discovered here prevent rework during execution. --- ## Phase 1.0: Assessment **Actor**: plan-advisor **teammate** (resumed, NOT a new sub-agent) If you don't have `plan_advisor_id` yet (skipped Phase 0 or session recovery), spawn the teammate first (see Phase 0 in the governed-workflow skill), then resume it. ### Goal Produce a structured assessment that maps the ticket to the codebase and surfaces everything that needs investigation before planning. ### Prompt Resume the plan-advisor teammate with an explicit structure requirement: ``` Agent( resume: {plan_advisor_id}, prompt: "Begin assessment. Read workspace_get_state for context (ticket, working_dir, context notes). Produce a STRUCTURED assessment with these sections: 1. TICKET RESTATEMENT — rephrase the ticket in your own words. This catches misunderstandings early. If your restatement doesn't match the ticket intent, the orchestrator will correct you before research begins. 2. AFFECTED AREAS — not file paths, but concepts: which APIs, which user flows, which data pipelines, which business domains are touched. Think in terms of what the system does, not where the code lives. 3.