Roadmap Generation Flow
Product Manager Official v1.1.35Full product roadmap generation from vision through to themed, time-bound initiatives with dependency mapping, resource allocation, and stakeholder-ready output
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 20 nodes
Roadmap Generation Flow
Multi-stage pipeline that generates a complete product roadmap from vision, OKRs, and customer feedback through themed initiatives, dependency mapping, resource allocation, and stakeholder-ready output
Dependency Mapping
Mapping technical and business dependencies between product initiatives to identify critical paths, sequencing constraints, and risk concentrations
Initiative Breakdown
Breaking strategic roadmap themes into concrete, scoped, single-quarter initiatives with clear outcomes, strategic classification, and confidence levels
Resource Planning
Planning resource allocation across teams and quarters, identifying gaps, conflicts, and capacity constraints
Roadmap Assembly
Assembling the narrative, themes, initiatives, dependencies, timeline, and resource plan into a single complete, consistent, stakeholder-ready roadmap document
Roadmap Narrative
Weaving strategic themes, initiatives, dependencies, timelines, and resource allocations into a compelling stakeholder-ready roadmap narrative
Theme Extraction
Extracting strategic themes from product vision, OKRs, and customer feedback to organize and structure a product roadmap
Timeline Estimation
Estimating realistic timelines for product initiatives accounting for complexity, risk, capacity, and historical velocity
Dependency Graph Generator
Generate a dependency graph narrative and matrix for a set of product initiatives, identifying critical paths and sequencing constraints
Initiative Breakdown Prompt
Break strategic roadmap themes into concrete, scoped initiatives with clear outcomes, strategic classification, and confidence levels
Resource Mapper
Map initiatives to teams and individuals, identifying resource gaps, conflicts, and allocation decisions
Roadmap Assembler
Assemble all roadmap components into a complete, structured document ready for stakeholder review
Roadmap Narrative Writer
Write a compelling roadmap narrative that connects strategic themes, initiative choices, and timelines to the product vision
Timeline Calculator
Calculate realistic timelines for product initiatives based on effort estimates, capacity, dependencies, and historical velocity
Vision to Themes Prompt
Translate product vision, OKRs, and customer feedback into strategic roadmap themes
Roadmap Methodology Guide
Reference guide to product roadmap methodologies including NOW-NEXT-LATER, timeline-based, outcome-based, and theme-based approaches
Roadmap Communication Guide
Guide to communicating product roadmaps effectively to different audiences — executives, teams, customers, and partners
Roadmap Governance Framework
Framework for roadmap governance including review cadence, change management process, decision authority, and escalation paths
Quarterly Planning Template
Template for quarterly planning breakdowns, mapping initiatives to teams, timelines, and capacity within a single quarter
Roadmap Template
Master template for the final roadmap document, providing the structure and placeholder sections for assembly
Requirements 1 service, 5 data types
- LLM Service
- pii
- product roadmap
- business strategy
- resource plans
- technical specifications
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling: pii
Version history 21 releases
GH#863 Wave 1 (#858-A1 class) — K-045 intent/output-mismatch fix. The workflow shipped three producer prompts that were never invoked, so it emitted polished intermediate analysis (executive summary) rather than the promised roadmap document. This release wires the never-invoked `roadmap-assembler` (final assembler), `roadmap-narrative-writer`, and `initiative-breakdown-prompt` into the execution block in dependency order, each behind a new backing skill (`initiative-breakdown`, `roadmap-narrative`, `roadmap-assembly`) so they are `from_step`-addressable. Cross-step references were converted from positional/title form to explicit `from_step` bindings via `context_params`. The `roadmap-assembly` step is now the final content step before `language-polish`, and `polish-language` is repinned 1.0.1 → 1.0.6 (adds the bindable `source` slot) with `language-polish` `source` bound to the assembled roadmap — so the output is the polished roadmap, not the polished summary. Skills 4 → 7, total 17 → 20.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (themes/list, dependencies/text, timeline/text, resource_plan/text, stakeholder_analysis/text, summary/text, merged_roadmap/text, polished_roadmap/text, compliance_verdict/decision, consistency_verdict/decision, input_gaps/decision, risk_assessment/text). Lights up the #744 rich flow-map with named, typed outputs. **Also corrects the input-gap-check step to its intended `validation` type** — its `step_type` was mis-indented (outside the parallel item) and dropped at parse time, so the step previously ran untyped; it is now a validation gate. Content + structural fix (GH#748); no bindings changes.
GH#638 Row 4 + Row 13 closure — migrate the dependencies block to K-037 schema and repin every dep at v1.0.1 (assess-risks at v1.0.2 per its own fix-forward). Pre-K-037 v1.1.31 bundle had `id: hub-shared/<slug>` for each dep, which engine STEP 4d strict-UUID match cannot reconcile against the catalogue. v1.1.32 ships each dep with `id: "<UUID>"` (canonical manifest.id from catalogue) plus `name: "<slug>"` (logical alias for URL routing and human readability). All 18 dep bundles were also republished (Row 11 cascade) so their own `manifest.id` aligns with the catalogue UUID, closing the v1.0.0 STEP 4d mismatch end-to-end. No consumer content changes; identity + dep-version repin only. UUIDs sourced from Hub catalogue per K-037; checksums fetched via gen-dep-checksums.mjs (F2 fail-loud).
Re-sign of v1.1.30 — the v1.1.30 publish ran before the scanner fix `4f97762e` was on origin/main, so CI fetched the old scanner and the published bundle still carried the WARN-bearing security block. v1.1.31 republishes against origin/main's fixed scanner; clean security block; App import-review shows PASS on structural validation.
Re-signed after GH#633 Hub scanner fix: the previous bundle's security block carried a false-positive WARN ("output_step language-polish does not exist as a skill file") because the Hub JS scanner's C1 check was dep-blind. v1.1.30 ships against the fixed scanner; clean security block; App import-review now shows PASS on structural validation.
Fix-forward for caller-release.yml CONTENT_HASH extraction bug surfaced by v1.1.28: the previous regex matched the first `checksum:` in the manifest (which became a dep checksum once the dependencies block landed), not the bundle's integrity checksum. v1.1.28 registered an incorrect contentHash in D1; v1.1.29 ships the integrity-block-anchored regex and the correct bundle checksum.
GH#625 Step 3 (Path A pilot): migrated 18 inline-vendored shared slugs to dep-references against the `hub-shared/*` catalogue. Same canonical content, now sourced from versioned `hub-shared/<slug>@1.0.0` deps with checksums. Slugs: analyse-stakeholders, assess-risks, brief-compliance-check, check-brief-compliance, check-consistency, check-input-gaps, company-okrs, consistency-check, dedup-and-merge, executive-summary, executive-summary-prompt, input-gap-check, language-polish, llm-service, polish-language, product-strategy-guide, risk-assessment, stakeholder-analysis.
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Product Manager
View all →User Research Pipeline
Plan and synthesize user interviews, surveys, and feedback into actionable insights
PRD Generator Flow
Full product requirements document generation with stakeholder context, success metrics, and technical constraints
Prioritisation Framework Flow
Apply RICE, ICE, and MoSCoW scoring frameworks to a product backlog and produce ranked recommendations with rationale