Turn a larger idea into a dependency-ordered roadmap of tasks — the layer above create-task. Use when the work is several distinct tasks with real ordering between them (schema before API before UI), and you want the whole task graph drawn before implementing. Producer only; ab-start-roadmap executes it.
Install
npx skillscat add ayoubben18/ab-method/ab-create-roadmap Install via the SkillsCat registry.
Converts a larger idea into a dependency-ordered roadmap of tasks, decomposing work into a coarse task graph before implementation begins. It is intended for projects involving multiple distinct tasks with real ordering constraints, serving as the planning layer above task creation. Use it when you need the full task graph drafted prior to executing individual tasks.
This skill runs the AB Method create-roadmap workflow.
Follow the workflow defined in .ab-method/core/create-roadmap.md exactly — it contains the decomposition grill, the roadmap.md format, the dependency-graph rules, and the per-task planning-prompt process.
Before doing anything, check .ab-method/structure/index.yaml. It defines where roadmaps and tasks are stored and how they reference each other (the relationships section). Paths are user-configurable; never hardcode them.
Key points: grill the idea once to draw the task DAG (coarse tasks, no missions); write docs/roadmaps/<name>/roadmap.md as the roadmap-level source of truth; hand back a /create-task prompt per task in dependency order (foundational first), recommending a fresh session each and warning about context bloat if planning inline. Do not execute — ab-start-roadmap does that. ab-create-task is roadmap-aware and keeps roadmap.md in sync automatically.