How do I install the Ab Start Roadmap skill?

Run npx skillmds@latest add ayoubben18/ab-start-roadmap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ab Start Roadmap safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ab Start Roadmap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ab Start Roadmap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ab Start Roadmap?

ayoubben18 (@ayoubben18) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ab Start Roadmap by ayoubben18 — Agent Skill

Name: Ab Start Roadmap
Author: ayoubben18

Ab Start Roadmap

Execute a roadmap autonomously to completion — the layer above start-task. Use when a roadmap's tasks are planned and you want them run in dependency order, with independent tasks optionally in parallel. Verifies the dependency tree is planned before running; stops if a needed task has no plan. Executor only.

ayoubben18 Updated Sep 21, 2026

File contents

This skill runs the AB Method start-roadmap workflow.

Follow the workflow defined in .ab-method/core/start-roadmap.md exactly — it contains the dependency-tree verification gate, the parallelism-mode prompt, the topological execution loop, and the failure/resume rules.

Before doing anything, check .ab-method/structure/index.yaml. It defines where roadmaps and tasks are stored and how they reference each other. Paths are user-configurable; never hardcode them.

Key points: build the DAG from roadmap.md; verify the whole dependency tree before executing — a task is runnable only if it has a real plan (progress-tracker.md with missions) and its deps are done; if a needed dependency is unplanned, STOP and tell the user to plan it first with ab-create-task. No "Proceed?" prompt — it starts on invocation. Parallelism comes from the invocation: sequential by default (safe, portable), git worktrees only when explicitly asked. Each task runs by ab-start-task rules (subagent per mission, tdd, commit per green mission). On Codex the parent orchestrates flat — one subagent level, no agent-in-agent — because Codex's spawn_agent is one level deep and cannot nest (NESTING_UNAVAILABLE); never design a task as a subagent that spawns mission-subagents here. (Claude Code, which can nest, defaults to the nested task-subagent → mission-subagent shape for context isolation — that's the Claude path, not this one.) Update roadmap.md statuses as tasks complete; re-runs resume from the frontier. Re-runnable / incremental: a task NEEDS WORK whenever its progress-tracker.md has any unchecked mission, regardless of its status: field — so after a completed roadmap, ab-extend-task can add missions (reopening those tasks), and re-running executes only the tasks with new work, in dependency order, skipping finished ones. Never define or reshape tasks — this is executor only.

---name: ab-start-roadmapdescription: Execute a roadmap autonomously to completion — the layer above start-task. Use when a roadmap's tasks are planned and you want them run in dependency order, with independent tasks optionally in parallel. Verifies the dependency tree is planned before running; stops if a needed task has no plan. Executor only.---This skill runs the AB Method **start-roadmap** workflow.Follow the workflow defined in `.ab-method/core/start-roadmap.md` exactly — it contains the dependency-tree verification gate, the parallelism-mode prompt, the topological execution loop, and the failure/resume rules.Before doing anything, check `.ab-method/structure/index.yaml`. It defines where roadmaps and tasks are stored and how they reference each other. Paths are user-configurable; never hardcode them.Key points: build the DAG from `roadmap.md`; **verify the whole dependency tree before executing** — a task is runnable only if it has a real plan (`progress-tracker.md` with missions) and its deps are `done`; if a needed dependency is unplanned, STOP and tell the user to plan it first with `ab-create-task`. No "Proceed?" prompt — it starts on invocation. Parallelism comes from the invocation: sequential by default (safe, portable), git worktrees only when explicitly asked. Each task runs by `ab-start-task` rules (subagent per mission, `tdd`, commit per green mission). On Codex the parent orchestrates **flat** — one subagent level, no agent-in-agent — because Codex's `spawn_agent` is one level deep and cannot nest (`NESTING_UNAVAILABLE`); never design a task as a subagent that spawns mission-subagents here. (Claude Code, which can nest, defaults to the nested task-subagent → mission-subagent shape for context isolation — that's the Claude path, not this one.) Update `roadmap.md` statuses as tasks complete; re-runs resume from the frontier. **Re-runnable / incremental:** a task NEEDS WORK whenever its `progress-tracker.md` has any unchecked mission, regardless of its `status:` field — so after a completed roadmap, `ab-extend-task` can add missions (reopening those tasks), and re-running executes only the tasks with new work, in dependency order, skipping finished ones. Never define or reshape tasks — this is executor only.

Frequently asked questions