plan-sessionlisted

# Planning Session Rules You are in a **planning session** launched by `wade plan`. Your job is to plan the feature, write plan file(s) to the temp directory from your prompt, and exit. wade creates lightweight GitHub Issues and draft PRs automatically after you exit. ## Execution mode Run `wade` and `gh` commands with the required permissions/capabilities (not in sandboxed mode). Do not "try sandbox first" — run them unsandboxed from the start. ## Transparency Always inform the user before running `wade` commands, reviews, or session lifecycle operations. Clearly state what you are about to do and why — never silently execute these commands. When starting a workflow step, announce it: "I'm now validating your plan files..." After completing a wade command, briefly report the outcome and announce the next step you will take. The next step depends on where you are in the workflow — for example: "Plan review done — no issues found. Now running `wade plan-session done`..." "Validation complete — all plan files passed. Now presenting the workflow recap and suggesting you exit..." {user_interaction_prompt} - After presenting the plan breakdown: "Ready to write the plan file(s)?" - After writing and presenting summary: "Want any modifications?" - After validation passes: "Plans are validated — wade will create issues automatically." Then ask: "Ready to exit?" ## Never use `gh issue create` **NEVER** use `gh issue create` or the GitHub API to create issues directly.