review-roadmap
Review a roadmap in a fresh agent before lock. Use for /review-roadmap.
- License 许可
- MIT
- 所属仓库
- lovrozagar/grunt
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- review-roadmap
- description
- Review a roadmap in a fresh agent before lock. Use for /review-roadmap.
03 SKILL.md 正文
review-roadmap
You review one roadmap under .tmp/grunt/roadmaps/ that someone else wrote. You start with no context from the writing session, and that is the point: judge the file, not the reasoning behind it. Format: .rulesync/reference/roadmap-format.md. Lessons: .rulesync/reference/lessons.md.
Slash /review-roadmap {n|path} only. Not a session flag. /write-roadmap runs it in a fresh agent after every write or revision. Run it yourself on any roadmap.
Read-only. Write nothing: not the roadmap, not a plan, not a lesson. The writer applies what it accepts and bumps the roadmap's reviews count in that save.
Rounds repeat: the first runs after /write-roadmap, another after each revision, and anyone can run one by hand. The count proves a round ran and was settled, not that it was good. A roadmap cannot move to locked until reviews is at least 1.
Scripts already enforce the format and the append-only ## Previous mistakes. Do not re-check those. Check what a script cannot:
- Read the roadmap in full.
- Read its
## Previous mistakes. Flag a slice or Decision that brings a recorded mistake back. - Run
node .rulesync/scripts/lessons.mjs matchon the absolute paths the roadmap names. Read each matched lesson. Flag a slice that walks into one with no Watch-out. - Read
principle-sequence-verifiable-units. Flag a slice that cannot be verified on its own, or that needs something a later slice ships. - Flag a slice that is really two plans, or half of one that should merge with its neighbor.
- Flag a Decision with no rejected alternative, and a slice Goal or Why that contradicts a Decision.
- Flag a Verify gate no one can run, and a program Goal no Verify gate proves.
- Flag a slice Goal too vague to write a plan from: an open choice, a vague target, or a path that does not exist.
- Compare
## Usagewith the slices in Order. Flag each new or changed command, flag, output, error message, or file a person or agent touches that Usage does not show, a changed one shown without its before, and aNo visible change:line on a roadmap that changes one.
Reply with at most 10 findings, most severe first, one line each: {slice number or section}: {problem}; {fix}. With nothing to flag, reply no findings. No praise and no summary.
04 同仓库更多 Skills
write-roadmap
Write an ordered program of plans under .tmp/grunt/roadmaps/. Use for /write-roadmap. Stops for y, which locks and runs it.
write-plan
Write a local checklist under .tmp/grunt/plans/. Then /implement-plan {n}.
unslop
Cut AI tells from any writing. Use for /unslop.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file, or for /typescript-best-practices.
tmp
Dump a one-off convo artifact under .tmp/grunt/.
teach
Explain a body of work plainly so a person actually understands it. Dig into how it works and why it is that way, then weave that into one clear explanation. Use for /teach, 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.