implement-plan
Execute remaining leaves in a .tmp/grunt/plans checklist. Skip [x].
- License 许可
- MIT
- 所属仓库
- lovrozagar/grunt
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- implement-plan
- description
- Execute remaining leaves in a .tmp/grunt/plans checklist. Skip [x].
03 SKILL.md 正文
implement-plan
You execute the plan in this session. A plan with reviews: 0 cannot start: the save denies the move to in-progress. Run /review-plan {n} in a fresh agent and settle it first. Start only on a plan the user approved, when the request said "plan and do it", or when /implement-roadmap is running a locked or in-progress roadmap. Skip [x]. Before the first open leaf, run git log -3 --stat and reconcile any newer commit that touches a file the plan lists, then read the plan's ## Previous mistakes and do not repeat one. Start at the first open leaf. Flip only the box after each leaf. When a phase's children are [x], mark the phase [x]. Frontmatter in-progress then done.
Arg {n|path} picks that file. Empty arg: unique in-progress, else unique ready, else list serials.
Format: .rulesync/reference/plan-format.md. Write-allowlist = paths listed in the plan. Run Verify leaves. Do not skip a test leaf. Do not flip a behavior leaf [x] until its test ran.
A leaf that names a principle skill is done by reading that skill and following it. Also follow the next paragraph, and read a principle an already-read principle cites. Do not open the rest of the catalog.
When a Verify or a test fails after a fix, or principle-attack-the-premise fires, add a - verify: … or - premise: … entry to ## Previous mistakes (Edit the plan; earlier entries stay). When it will happen again on other tasks, run node .rulesync/scripts/lessons.mjs match on the files involved, then hit the matching lesson or write a new one (.rulesync/reference/lessons.md), and end the entry with (lesson: {slug}).
Before Verify, read principle-prove-it-works and follow it. After two fixes that share a premise fail the same gate, read principle-attack-the-premise before a third try. Before you ask the user, read principle-never-block-on-the-human. Before a large dump or a fan-out, read principle-guard-the-context-window. Fat dumps go through node .rulesync/scripts/grunt-job.mjs.
On a failing-test leaf, run the test and see it fail for the missing behavior before the production edit. Then make it pass. Then run the nearest suite.
After Verify, if frontmatter commit: is set, run /commit with that subject and the journal Files. One plan, one commit, including a failing-test leaf and the fix. If a git hook fails on a path inside the plan write-allowlist, fix that code and commit again until the hook passes. Stop when the hook cites a path outside the allowlist or a missing secret. Do not skip the hook. Do not push. A plan with no commit: key does not auto-commit.
On start: if this plan has no journal, Write one under .tmp/grunt/implementations/ (IMPL_NAME:, IMPL_PLAN: {n}). Format: .rulesync/reference/implementation-format.md. After each leaf: append N.M [x] … to Log, update Files (repo-relative product paths) and Done. Blocked → status: blocked and Blockers. Verify done → status: done. Straight shots do not write a journal.
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'.