create-roadmap
/create-roadmap
Create a Now/Next/Later outcome-oriented roadmap when the user asks to plan a roadmap, prioritize features, or define product direction
- Author
- jerelvelarde ↗
- Repository
- chalk-skills ↗
- Licence
- MIT
- Last repository change
- 10.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create a Now/Next/Later outcome-oriented roadmap when the user asks to plan a roadmap, prioritize features, or define product direction
Arguments
/create-roadmap [product area or theme to roadmap]
Original author description
Create a Now/Next/Later outcome-oriented roadmap when the user asks to plan a roadmap, prioritize features, or define product direction
How it works
- Overview
- Workflow
- Output
- Anti-patterns
SKILL.md preview
--- name: create-roadmap description: Create a Now/Next/Later outcome-oriented roadmap when the user asks to plan a roadmap, prioritize features, or define product direction author: chalk version: "1.0.0" metadata-version: "3" allowed-tools: Read, Glob, Grep, Write argument-hint: "[product area or theme to roadmap]" read-only: false destructive: false idempotent: false open-world: false user-invocable: true tags: product, roadmap, planning --- # Create Roadmap ## Overview Generate a Now/Next/Later roadmap where every item ties to a measurable outcome, not just a feature name. This format communicates strategic intent without false precision on dates, and forces prioritization by time horizon and confidence level. ## Workflow 1. **Read product context** -- Scan `.chalk/docs/product/` for the product profile, PRDs, JTBD docs, and metrics frameworks. Check `.chalk/docs/engineering/` for architecture constraints and tech debt items. These inform what is feasible and what matters. 2. **Parse scope** -- Extract from `$ARGUMENTS` the product area, theme, or time horizon to roadmap. If unspecified, create a full-product roadmap using all available context. 3. **Determine the next file number** -- Read filenames in `.chalk/docs/product/` to find the highest numbered file. The next number is `highest + 1`. 4. **Categorize items into time horizons**: - **Now** (current cycle, high confidence): Actively being built or about to start. Clear problem definition, validated need, committed resources. - **Next** (1-2 cycles out, medium confidence): Problem is understood, solution is taking shape, not yet committed. - **Later** (future, low confidence): Strategic bets, exploration areas, things that depend on learning from Now/Next. 5. **Write each item** with columns: Item, Outcome (measurable result), Confidence (high/medium/low), Dependencies (what must be true or done first). 6. **Add strategic context** -- Above the roadmap table, write a brief narrative explaining the strategic themes connecting the items and what the roadmap is optimizing for. 7. **Write the file** -- Save to `.chalk/docs/product/<n>_roadmap.md`. 8. **Confirm** -- Share the file path and highlight any items with unresolved dependencies or low confidence that need validation. ## Output - **File**: `.chalk/docs/product/<n>_roadmap.md` - **Format**: Plain markdown with strategic narrative and Now/Next/Later tables - **First line**: `# Roadmap: <Product Area or Theme>` ## Anti-patterns - **Feature lists without outcomes** -- "Add filtering" is not a roadmap item. "Users can find records in <10 seconds (reduce support tickets by 30%)" ties the work to value. - **Dates on everything** -- Now/Next/Later intentionally avoids specific dates for Next and Later items. Adding dates to low-confidence items creates false promises. - **No dependencies called out** -- Roadmap items without dependencies hide sequencing risks. If B requires A, say so. - **Confidence theater** -- Marking everything as "high confidence" defeats the purpose. Be honest about what is validated versus what is a bet. - **Solution-shaped items** -- "Build GraphQL API" belongs in an engineering plan, not a product roadmap. Roadmap items should describe user or business outcomes.
Versions
The database has no other skills named create-roadmap.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 2e787516b797 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85pm-roadmap
Create or critique a product roadmap — outcome-oriented, theme-based, confidence-aware (Now-Next-Later) roadmaps tied to strategy, instead of dated feature lists. Gates format and detail by audience and planning horizon. Trigger when the user asks to build, write, review, or… - 100roadmap
Use when the PM wants to build, update, reprioritise or present the product roadmap, asks "what's now, next and later", needs to fit a new item in, or has to move dates after a slip. Keeps a Now / Next / Later roadmap in sync with the items in work/, their evidence and stages,… - 100helm-plan
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features". - 90roadmap
Builds or updates a product or delivery roadmap from a charter, PRD, backlog, or stakeholder priorities. Use whenever someone says "build a roadmap", "what's our roadmap", "plan the next quarter", "now/next/later", or wants initiatives sequenced into themes and time horizons… - 100helm-plan
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features". - 100outcome-roadmap
Transform output-based feature lists into outcome-driven Now/Next/Later roadmaps using the "so what?" technique. Use when converting a feature-list roadmap to outcomes, communicating product strategy, or running quarterly planning.