Run any Skill in Manus with one click

claude-roadmap

Stars2

Forks0

UpdatedJuly 3, 2026 at 05:35

Drafts or updates `.claude/ROADMAP.md` by sequencing the MVP scope from `.claude/REQUIREMENTS.md` into ordered versions, each a usable increment. Use when asked to "draft a roadmap", "build the roadmap", "sequence the versions", "plan the roadmap", or "update the roadmap". Do NOT break versions into task-level steps. That is `claude-feature` and `.claude/TASKS.md`.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

erclx

erclx/toolkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	claude-roadmap
description	Drafts or updates `.claude/ROADMAP.md` by sequencing the MVP scope from `.claude/REQUIREMENTS.md` into ordered versions, each a usable increment. Use when asked to "draft a roadmap", "build the roadmap", "sequence the versions", "plan the roadmap", or "update the roadmap". Do NOT break versions into task-level steps. That is `claude-feature` and `.claude/TASKS.md`.

Claude roadmap

Guards

If .claude/REQUIREMENTS.md is absent or has no MVP features, stop: ❌ No requirements to sequence. Draft .claude/REQUIREMENTS.md first.
Sequence versions and their outcomes only. Do not produce file lists or task steps.

Step 1: read context

Read these in parallel from the project root, skipping any that do not exist:

.claude/REQUIREMENTS.md: the MVP feature scope to sequence
.claude/ROADMAP.md: the existing roadmap, when updating rather than drafting
.claude/TASKS.md: what is in flight, to mark the active version
.claude/ARCHITECTURE.md: technical dependencies that constrain ordering

Follow .claude/standards/roadmap.md for the doc shape, sections, and version format.

Step 2: sequence

Group the MVP features into versions, each a usable increment that stands on its own. Order the versions by two forces:

Dependency: a version that produces data or a contract another version consumes comes first.
De-risking: a version that de-risks an unproven subsystem comes early, inside the version that first needs it.

For each version, state the observable outcome as what the user can then do, list the features it groups by name, and note what it depends on and why.

When updating an existing roadmap, preserve rows that still hold. Resequence, add, or split only where scope shifted. Do not rewrite rows that did not change.

Step 3: write

Write the roadmap to .claude/ROADMAP.md at the project root, following .claude/standards/roadmap.md. Create the file when absent.

Unlike .claude/plans/ and .claude/TASKS.md, .claude/ROADMAP.md is committed. Do not stage or commit it here. Leave staging to the git skills.

Step 4: output

📝 Wrote .claude/ROADMAP.md

<N> versions sequenced. Active: vX.Y.

Next: /claude-feature for the first version's opening feature.

When updating, replace the first line with 📝 Updated .claude/ROADMAP.md and name which versions changed.

More from this repository

same repository

claude-address-review

erclx/toolkit

Pulls review findings and CI status on the current branch's open PR, fixes each in the working tree, refreshes any stale `.claude/` docs, replies with a summary comment, and pushes a follow-up commit. The worker's return leg after `claude-pr-review`. Use when asked to "address the review", "fix the PR comments", "respond to review", or after an orchestrator posts findings. Do NOT use to write a review. That is `claude-pr-review`.

2026-07-112

git-followup

erclx/toolkit

Ships a small self-review edit on the current PR branch by staging, committing, pushing, and syncing the open PR, replying on the PR when it carries review comments. Use when asked to "ship a followup", "push the PR fix", "followup", or "commit and push this small change". Do NOT use when there is no open PR for the branch (use git-ship instead).

2026-07-112

code-review

erclx/toolkit

Claude skill structure and authoring rules

2026-07-102

claude-autoship

erclx/toolkit

Chains implement → verify → review → ship after a feature plan is approved. Reads the plan for the current branch, runs the full pipeline in one session, and stops on any failure or non-minor review finding. Use when asked to "autoship", "ship this feature end to end", or "run the chain". Do NOT auto-trigger. Requires an approved plan file.

2026-07-102

claude-orchestrate

erclx/toolkit

Asserts the orchestrator role for the current session and holds the build loop, dispatching to the roadmap, feature, review, and worktree skills. Use when asked to "be the orchestrator", "run the orchestrator", "orchestrate this project", or to set up the control session for parallel feature builds. Do NOT build features or merge PRs in this session.

2026-07-102

claude-pr-review

erclx/toolkit

Reviews an open pull request from an independent session and posts findings as a review comment on the PR. Reads project docs and the roadmap for cross-feature context a self-review lacks. Use when asked to "review the PR", "review this feature's PR", "post a PR review", or acting as the orchestrator reviewing a worker's PR. Do NOT use to review local uncommitted changes. That is `claude-review`.

2026-07-102

name	claude-roadmap
description	Drafts or updates `.claude/ROADMAP.md` by sequencing the MVP scope from `.claude/REQUIREMENTS.md` into ordered versions, each a usable increment. Use when asked to "draft a roadmap", "build the roadmap", "sequence the versions", "plan the roadmap", or "update the roadmap". Do NOT break versions into task-level steps. That is `claude-feature` and `.claude/TASKS.md`.

Claude roadmap

Guards

If .claude/REQUIREMENTS.md is absent or has no MVP features, stop: ❌ No requirements to sequence. Draft .claude/REQUIREMENTS.md first.
Sequence versions and their outcomes only. Do not produce file lists or task steps.

Step 1: read context

Read these in parallel from the project root, skipping any that do not exist:

.claude/REQUIREMENTS.md: the MVP feature scope to sequence
.claude/ROADMAP.md: the existing roadmap, when updating rather than drafting
.claude/TASKS.md: what is in flight, to mark the active version
.claude/ARCHITECTURE.md: technical dependencies that constrain ordering

Follow .claude/standards/roadmap.md for the doc shape, sections, and version format.

Step 2: sequence

Group the MVP features into versions, each a usable increment that stands on its own. Order the versions by two forces:

Dependency: a version that produces data or a contract another version consumes comes first.
De-risking: a version that de-risks an unproven subsystem comes early, inside the version that first needs it.

For each version, state the observable outcome as what the user can then do, list the features it groups by name, and note what it depends on and why.

When updating an existing roadmap, preserve rows that still hold. Resequence, add, or split only where scope shifted. Do not rewrite rows that did not change.

Step 3: write

Write the roadmap to .claude/ROADMAP.md at the project root, following .claude/standards/roadmap.md. Create the file when absent.

Unlike .claude/plans/ and .claude/TASKS.md, .claude/ROADMAP.md is committed. Do not stage or commit it here. Leave staging to the git skills.

Step 4: output

📝 Wrote .claude/ROADMAP.md

<N> versions sequenced. Active: vX.Y.

Next: /claude-feature for the first version's opening feature.

When updating, replace the first line with 📝 Updated .claude/ROADMAP.md and name which versions changed.