ab-start-roadmap

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.