now-next-later
Now-Next-Later Roadmap
Create a Now-Next-Later roadmap using Janna Bastow's framework.
Works with:
- Linear MCP - Reads your projects and generates roadmap automatically
- GitHub MCP - Reads your projects/milestones and generates roadmap automatically
- Manual - Describe your projects directly
Entry Point
When this skill is invoked, start with:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NOW-NEXT-LATER ROADMAP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Roadmaps should communicate sequence and certainty, not dates.
What do you want to do?
1. Generate roadmap from Linear/GitHub
→ I'll fetch your projects and categorize them
2. Create roadmap from description
→ Tell me about your projects
3. Review existing roadmap
→ Paste your current roadmap for analysis
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
What This Does
Transforms your projects into a roadmap that communicates sequence and certainty without false dates.
Usage
/now-next-later
Optional parameters:
/now-next-later --team [team-name]- Roadmap for specific team/now-next-later --export- Generate markdown/mermaid diagram/now-next-later --send-to-linear- Create Linear issues from roadmap
What Happens
- Fetches projects from Linear or GitHub (if MCPs configured)
- Applies Janna Bastow's framework:
- NOW: High certainty, committed work (current sprint/cycle)
- NEXT: Medium certainty, exploring solutions (next 1-2 cycles)
- LATER: Low certainty, ideas and options (future, TBD)
- Categorizes projects based on:
- Certainty level
- Dependencies
- Discovery state
- Team capacity
- Generates roadmap showing sequence without dates
Linear Integration
When you use --send-to-linear, the command creates Linear issues with clear categorization:
How Issues Are Categorized
Each issue gets:
- Title prefix:
[NOW],[NEXT], or[LATER]for instant visibility - Description: Includes priority category, rationale, dependencies, and success criteria
- Priority level: Set appropriately (1 for NOW, 2 for NEXT, 0 for LATER)
Finding Your Roadmap Issues in Linear
Create saved views to organize roadmap items:
- Go to your team's Issues page in Linear
- Click Filters button
- Add filter: Select Content → type
[NOW](or[NEXT]or[LATER]) - Click "Save as View" - Name it "🎯 NOW Roadmap Items"
- Repeat for NEXT and LATER
Recommended views:
- 🎯 NOW Roadmap Items - Filter:
Content: [NOW] - ➡️ NEXT Roadmap Items - Filter:
Content: [NEXT] - 🔮 LATER Roadmap Items - Filter:
Content: [LATER]
Example Output
📅 Now-Next-Later Roadmap
🎯 NOW (High certainty - we're building this)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ [PROJ-12] Mobile app redesign
Status: In progress, 60% complete
Why Now: User research done, designs validated, eng capacity allocated
✓ [PROJ-18] Payment flow optimization
Status: Ready to build
Why Now: Critical for Q1 revenue goal, solution de-risked
➡️ NEXT (Medium certainty - we're exploring)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
○ [PROJ-24] AI recommendation engine
Status: Discovery phase
Why Next: Technical feasibility confirmed, need to validate value
Dependencies: Waiting on data pipeline completion
○ [PROJ-31] Team collaboration features
Status: Solution being explored
Why Next: Customer demand validated, choosing between 3 approaches
🔮 LATER (Low certainty - we're considering)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
◌ API v3 rewrite
Why Later: Need to validate API v2 usage first
◌ Enterprise SSO
Why Later: Depends on enterprise market traction
◌ Mobile widgets
Why Later: Interesting idea, needs customer validation
💡 Roadmap Principles:
- NOW = Committed (we're doing this)
- NEXT = Probable (we're likely doing this if discovery goes well)
- LATER = Possible (we might do this, many options)
- No fake dates - communicate sequence and certainty instead
Integration Options
With Linear MCP: Automatically fetches Linear projects and roadmap data.
With GitHub MCP: Automatically fetches GitHub Projects and Milestones.
Manual mode: Describe your projects and the command will organize them:
Help me organize these projects into a Now-Next-Later roadmap: [paste projects]
Learn More
See the full Now-Next-Later framework at:
frameworks/planning/now-next-later.md
Framework: Janna Bastow (ProdPad, Mind the Product) Best for: Roadmap communication, stakeholder alignment, embracing uncertainty AI-era adaptation: Roadmaps update faster with rapid prototyping - keep them flexible
More from breethomas/pm-thought-partner
agent-workflow
Expert system for designing and architecting AI agent workflows based on proven Meta methodologies. Use when users need to build AI agents, create agent workflows, solve problems using agentic systems, integrate multiple tools into agent architectures, or need guidance on agent design patterns. Helps translate business problems into structured agent solutions with clear scope, tool integration, and multi-layer architecture planning.
9context-engineering
[ARCHIVED] Full 4D Context Canvas reference. For new AI features, use /spec --ai. For debugging, use /ai-debug. For quality checks, use /context-check.
6spec
Write specifications at the right depth for any project. Progressive disclosure from quick Linear issues to full AI feature specs. Embeds Linear Method philosophy (brevity, clarity, momentum) with context engineering for AI features. Use for any spec work - quick tasks, features, or AI products.
2competitive-research
Systematic competitive intelligence with parallel agent analysis. Analyzes competitors thoroughly and synthesizes into actionable insights.
2pmf-survey
Create and analyze a PMF survey using Rahul Vohra's Superhuman framework. The magic 40% benchmark for product-market fit.
2four-risks
Run Marty Cagan's Four Risks assessment on an issue (value, usability, feasibility, viability). Use when evaluating features before building.
2