product-roadmap-now-next-later
Sub-skill of product-roadmap: Now / Next / Later (+3).
Best use case
product-roadmap-now-next-later is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of product-roadmap: Now / Next / Later (+3).
Teams using product-roadmap-now-next-later should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/now-next-later/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How product-roadmap-now-next-later Compares
| Feature / Agent | product-roadmap-now-next-later | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of product-roadmap: Now / Next / Later (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Now / Next / Later (+3) ## Now / Next / Later The simplest and often most effective roadmap format: - **Now** (current sprint/month): Committed work. High confidence in scope and timeline. These are the things the team is actively building. - **Next** (next 1-3 months): Planned work. Good confidence in what, less confidence in exactly when. Scoped and prioritized but not yet started. - **Later** (3-6+ months): Directional. These are strategic bets and opportunities we intend to pursue, but scope and timing are flexible. When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates. ## Quarterly Themes Organize the roadmap around 2-3 themes per quarter: - Each theme represents a strategic area of investment - Under each theme, list the specific initiatives planned - Themes should map to company or team OKRs - This format makes it easy to explain WHY you are building what you are building When to use: When you need to show strategic alignment. Good for planning meetings and executive communication. ## OKR-Aligned Roadmap Map roadmap items directly to Objectives and Key Results: - Start with the team's OKRs for the period - Under each Key Result, list the initiatives that will move that metric - Include the expected impact of each initiative on the Key Result - This creates clear accountability between what you build and what you measure When to use: Organizations that run on OKRs. ## Timeline / Gantt View Calendar-based view with items on a timeline: - Shows start dates, end dates, and durations - Visualizes parallelism and sequencing - Good for identifying resource conflicts - Shows dependencies between items When to use: Execution planning with engineering. NOT good for communicating externally (creates false precision expectations).
Related Skills
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
production-forecaster
Forecast oil & gas well production using decline curve analysis. Use when estimating EUR, generating type curves, fitting Arps models (exponential, hyperbolic, harmonic), or running reserve calculations. Supports conventional and unconventional wells, P10/P50/P90 probabilistic outputs, and multi-field type curve comparison.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
nextflow-pipelines
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data for gene expression, variant calling, and chromatin accessibility analyses.
github-roadmap-anchor-reuse
Reuse and reopen existing roadmap/epic GitHub issues instead of fragmenting work across duplicate replacement epics; retarget children and link active issues for continuity.
domain-gap-to-issue-roadmap
Deep multi-repo ecosystem audit → domain gap matrix → structured GitHub issue roadmap with epics. Use when the user wants to assess capabilities across repos and create a backlog of work items covering code, data, and documentation gaps.
testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
roadmap-to-github-issue-wave
Turn a roadmap/readiness review into a de-duplicated GitHub epic + child issue set with verification and explicit scope boundaries.
roadmap-issue-reopen-retarget-balance
Reopen existing roadmap anchors, close replacement epics, retarget new child issues, and add sequencing/de-dup comments so GitHub roadmap work preserves continuity and execution quality.
roadmap-anchor-issue-governance
Reopen and reuse the original roadmap/umbrella issue as the governance anchor; create new issues only for genuinely missing scoped work, then retarget/link all execution issues back to the anchor.
next-wave-handoff-bundle
Build a docs-only execution handoff bundle after a completed implementation wave — follow-up issue drafts, scoped authorization note, deploy checklist, operator note, copy/paste command bundle, and incremental commit hygiene.
llm-wiki-roadmap-integration
Integrate repo-ecosystem work into an existing llm-wiki / knowledge-roadmap issue without creating duplicate GitHub issues.