planning▌

Transform strategy into a sequenced, outcome-driven roadmap that aligns stakeholders and guides execution. \n \n Orchestrates five phases over 1-2 weeks: gather inputs (business goals, customer problems, technical constraints), define epics with hypotheses and success metrics, prioritize using frameworks like RICE, sequence by quarter with dependency mapping, and communicate with strategic narrative \n Emphasizes outcome-driven epics over feature lists, with each initiative tied to business metr

You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandi

Navigate product planning in uncertain environments using adaptive frameworks from 44 product leaders. \n \n Emphasizes optionality over prediction: maintain flexibility to pivot when new information emerges rather than committing to rigid roadmaps, especially critical in fast-moving AI/ML contexts \n Teaches decision frameworks including type one/two decisions (reversible vs. irreversible), data as compass not GPS, and explicit decision triggers tied to learning rather than calendar dates \n Co

Work like Manus: Use persistent markdown files as your "working memory on disk."

Turn a user request into a single, actionable plan with atomic steps.

Persistent file-based planning system for organizing complex multi-step tasks and maintaining context across sessions. \n \n Creates three markdown files (task_plan.md, findings.md, progress.md) in your project directory to serve as persistent working memory \n Includes session recovery via script to sync context after /clear commands and resume interrupted work \n Enforces structured workflows: plan first, update after each phase, log all errors, and never repeat failed actions \n Provides temp

File-based task organization and progress tracking for complex multi-step projects. \n \n Creates and maintains three persistent markdown files (task_plan.md, findings.md, progress.md) to preserve context across sessions and tool calls \n Automatically detects active plans on startup and prompts context recovery; supports session restoration after /clear via catchup script \n Enforces structured workflow: plan phases upfront, log discoveries and errors immediately, update progress after each act

Structured task planning with user stories, sprint organization, and backlog prioritization for agile teams. \n \n Provides templates for writing INVEST-compliant user stories with acceptance criteria, technical notes, estimation, and dependencies \n Includes epic decomposition patterns breaking features into stories and granular tasks with time estimates \n Supports MoSCoW prioritization (Must/Should/Could/Won't Have) and sprint planning with capacity planning and Definition of Done checklists

Cloud migration planning involves assessing current infrastructure, designing migration strategies, executing migrations with minimal downtime, and validating outcomes. Support lift-and-shift, replatforming, and refactoring approaches for smooth cloud adoption.

Agile sprint planning provides a structured approach to organize work into time-boxed iterations, enabling teams to deliver value incrementally while maintaining flexibility and responding to change.