kwplanlisted

<plan_request> #$ARGUMENTS </plan_request> # Plan Research what you already know, then structure a plan grounded in data and past learnings. Lead with the answer. ## When to Use * After brainstorming, when you're ready to commit to a direction * Starting a new strategy doc, campaign plan, or brief * "Plan the March campaign", "I need a brief for X", "Let's structure this" * Any non-trivial knowledge work that benefits from past context ## Process ### Step 1: Classify the work type (auto-detect, don't ask) Determine the work type from the user's description: | Type | Signals | | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | **Strategy** | Roadmap, architecture, long-term, layers, phases | | **Campaign** | Launch, promotion, timeline, channels, audience | | **Brief** | Directive for someone else, scope, deliverables | | **Research** | Investigation, competitive, analysis, synthesis | | **Operations** | Playbook, runbook, SOP, recurring process | Pick the best fit and proceed. Do not ask the user to classify. Also determine the **detail tier** from scope signals: | Tier | Signals | Output | |------|---------|--------| | **Quick** | "should we?", "gut check", single question, <30 min scope | Title, recommendation, 2-3 bullets of reasoning, one success metric | | *