Read-only view of the execution roadmap. Lists every epic with its per-status tallies, nests the still-open rows beneath their epic, collapses wholly-finished epics into one rollup line, and closes by naming the next planned task in file order. Four verbs — `list` (the reader's view), `tasks` and `epics` (filterable row and epic queries), `next` (the first planned task). Invoke any time to see what is left to build. Not a workflow phase; never writes; never starts or commits work.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
A read-only reader over the execution plan named by project.json → roadmap.path, in the family of standup and audit-baseline: it reads state and reports, it never mutates. It is not a workflow phase — it does not enter the Track Guard ordering and never blocks a commit.
standup answers six questions and the roadmap is one of them, so it bounds the roadmap section and drops to tallies on a large plan. This command answers only that one question, so it never collapses open rows at any plan size. What collapses instead is the finished work — that is the bulk, and it carries no pickup.
node .claude/skills/roadmap/cli.mjs list [--all] [--epic N] [--json] [--root <dir>]
node .claude/skills/roadmap/cli.mjs tasks [--epic N] [--status done|in-progress|planned] [--json]
node .claude/skills/roadmap/cli.mjs epics [--json]
node .claude/skills/roadmap/cli.mjs next [--json]
| Verb | Answers |
|---|---|
list | The whole plan as a reader sees it — header, rollup, open rows nested under their epic, and the next pickup. |
tasks | Individual rows, filtered by --epic and/or --status. One line per row. |
epics | One line per epic with its status and its done / in-progress / planned tally. |
next | The first planned row in file order, plus the epic it belongs to. |
Every verb takes --json and prints the raw projection instead of the rendering. A missing plan file exits 2 with the path it looked for; a malformed filter exits 1 with the usage error.
list printsRoadmap — docs/roadmap-execution-plan.md
13 epics · 78 rows · 66 done, 0 in progress, 12 planned
✅ Epics 1-7, 10, 12 (53 rows, all done)
Epic 8 ⬜ Codebugger explanation trace (0/3 done)
⬜ A Runtime-witness rule and the mcp-debugger declaration
⬜ B The /codebugger session and the explanation trace
Next planned: Epic 8 A Runtime-witness rule and the mcp-debugger declaration
Epic 4, never 4-4.--all expands the rollup: each epic gets its own header and its done rows render too.--epic N scopes the view to one epic. Naming an epic is itself a request to see it, so a scoped view never collapses.Every rendered line is whitespace-collapsed, clipped to 96 characters, and stripped of C0/C1 control characters by .claude/skills/lib/terminal-text.mjs. Roadmap titles are repository-controlled content on its way to a terminal, and a row title in this repo already runs past 1000 characters.
next and the Next planned: line both mean first in file order — the first planned row reading the plan top to bottom. Neither resolves a dependency graph; sequencing the work is sprint-planner's job, not this reader's.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
中文简介正在准备中。当前显示原文说明。
Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.
中文简介正在准备中。当前显示原文说明。
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
中文简介正在准备中。当前显示原文说明。
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after `/intake` when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at `docs/brd/<slug>.md`.
中文简介正在准备中。当前显示原文说明。
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
中文简介正在准备中。当前显示原文说明。
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
中文简介正在准备中。当前显示原文说明。