What problem does it solve? Timeline-based Gantt roadmaps force teams to commit to fixed dates and unvalidated features, creating feature-factory dynamics and broken stakeholder trust. This Skill reframes product planning around customer problems and measurable outcomes across three horizons of decreasing certainty. ## Core Features & Use Cases - Three-Horizon Structuring: Organizes initiatives into Now (high certainty, active build), Next (medium certainty, discovery), and Later (low certainty, strategic bets) with WIP limits of 2-4 items per pod. - Problem-Oriented Roadmap Cards: Enforces a 5-point card anatomy covering problem statement (JTBD), strategic theme/OKR, target metric lift, and non-binding candidate solutions. - Progression & Pruning Governance: Defines graduation criteria between horizons and anti-pattern repairs for hidden Gantt charts, feature dumping, and frozen Later columns. - Use Case: A SaaS team replaces its quarterly Gantt chart by reframing feature requests like "Add CSV export" into problem cards such as "Resolve manual reporting bottlenecks for finance teams" with target metric lifts. ## Quick Start Ask the agent to create an outcome-driven Now-Next-Later roadmap for your product using your current feature backlog and strategic OKRs.
