create-roadmap

Generate Now/Next/Later roadmaps as markdown files from product context.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-roadmap-generaljerel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-roadmap
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-roadmap
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-roadmap-generaljerel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual roadmapping is time-consuming and prone to misalignment between product context and execution.

Core Features & Use Cases

  • Generates Now/Next/Later roadmaps aligned to measurable outcomes.
  • Incorporates product context from docs and engineering constraints to ensure feasibility.
  • Outputs a ready-to-use markdown file at .chalk/docs/product/<n>_roadmap.md with a strategic narrative.

Quick Start

Provide a product area or theme to roadmap and run the skill to generate the Now/Next/Later roadmap.

Frequently Asked Questions about create-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Now/Next/Later roadmap from existing product documentation?

To create a Now/Next/Later roadmap, you provide a product area or theme and the skill generates prioritized outcomes using your product documentation and engineering constraints, outputting a formatted markdown file.

What is the best way to prioritize product outcomes without committing to specific dates?

Prioritizing product outcomes without specific dates is best achieved using a Now/Next/Later roadmap, which groups deliverables into horizons based on engineering constraints and strategic context rather than fixed timelines.

Can I generate a strategic roadmap for multiple product areas and themes?

Yes, you can generate a strategic roadmap for multiple product areas and themes by running the skill for each specific area, producing individual markdown files containing a strategic narrative and a prioritized outcomes table.

Does this roadmapping approach incorporate engineering constraints to ensure feasibility?

Yes, the roadmapping approach incorporates engineering constraints alongside product documentation context to ensure that the prioritized outcomes across the Now, Next, and Later horizons remain technically feasible.

Where are the generated roadmap files saved?

The generated roadmap files are saved as ready-to-use markdown files at the path .chalk/docs/product/<n>_roadmap.md, containing both the strategic narrative and the Now/Next/Later table.