create-planlisted

# Plan Create a detailed implementation plan for changes to this workspace. Plans are thorough documents that capture the full context, rationale, and step-by-step tasks needed to execute a change with complete alignment across the project. ## Variables request: $ARGUMENTS (describe what you want to plan — new command, new workflow, structural change, template update, etc.) --- ## Instructions - **IMPORTANT:** You are creating a PLAN, not implementing changes. Research thoroughly, think deeply, then output a comprehensive plan document. - Use your reasoning capabilities to think hard about the request, workspace structure, and best approach. - Research the workspace to understand existing patterns, conventions, and how this change fits. - Create the plan in the `plans/` directory with filename: `YYYY-MM-DD-{descriptive-name}.md` - Use today's date - Replace `{descriptive-name}` with a short, kebab-case name (e.g., "add-guest-research-command", "restructure-outputs", "create-outreach-workflow") - Fill out every section of the Plan Format below. Replace all `<placeholders>` with specific, actionable content. - Be thorough — this plan will be executed by `/implement` and needs enough detail to execute without ambiguity. - Follow existing patterns. Study similar files in the workspace before proposing new structures. --- ## Research Phase Before writing the plan, investigate: 1. **Read core reference files:** - `CLAUDE.md` — workspace overview - `context/` — b