[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M780P0535WEE9WYBKJC7D83J":3,"skill-same:01M780P0535WEE9WYBKJC7D83J":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M780P0535WEE9WYBKJC7D83J","plan-project",null,"Plan a large, multi-phase implementation as a persisted .claude\u002Fplans\u002F\u003Cname>\u002F workspace with a ROADMAP and one sub-plan per phase. Use when a task is too big to hold in one in-context plan.","DTCurrie\u002Fhouserules","DTCurrie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1930371?v=4","01M780ND83PAY17A9HX96HHWG4","Devin T. Currie","01M780ND8W21FE1NSPAG03M0HM",2,"MIT","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fpayload\u002Fskills\u002Fplan-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan-project\ndescription: Plan a large, multi-phase implementation as a persisted .claude\u002Fplans\u002F\u003Cname>\u002F workspace with a ROADMAP and one sub-plan per phase. Use when a task is too big to hold in one in-context plan.\nargument-hint: \u003Cwhat to build>\nallowed-tools: Read, Edit, Write, Grep, Glob, Bash, Agent\n---\n\nPlan a multi-phase implementation as a persisted project: **$ARGUMENTS**\n\n**This skill plans. It does not implement.** It ends at a scaffolded workspace and a handoff (§4).\nStarting phase 1 is the user's call, not a continuation of planning.\n\nOne discipline makes this cheaper than re-planning from scratch each session. The plan lives on disk,\nnot in the transcript, and **`ROADMAP.md` is the single source of truth for what's done**. Every phase\nupdates its status _in place_ the moment it lands, so resuming is a grep rather than a re-derivation\nfrom scrollback.\n\n## 0. How much ceremony does this earn?\n\nThere are three tiers, and the ask lands in exactly one:\n\n- **Do it inline.** A handful of files you will finish now, with the shape already obvious. Write no\n  plan at all.\n- **Plan inline, persist nothing.** Enough moving parts to be worth thinking through first, but still\n  one sitting. Use plan mode or an in-context plan and scaffold no `.claude\u002Fplans\u002F` dir.\n- **Persist a workspace.** The rest of this skill.\n\nName the tier out loud before doing anything, in one sentence, with the reason you picked it. The\nuser can then override it in a word. Silently scaffolding is the failure this prevents, since a\n`.claude\u002Fplans\u002F` dir for a one-sitting task is pure overhead that no one asks you to delete.\n\nThe top tier has a bar. Scaffold **only** when at least one holds:\n\n- **3+ distinct phases** that can land independently and each leave the tree working.\n- Work you expect to **pause and resume** across sessions or days.\n- Enough moving parts that \"what's left?\" won't be obvious from `git diff` alone.\n\nWhen it's a genuine toss-up between the middle tier and this one, ask the user whether to track it\nas a project.\n\n## 1. Name the plan and scaffold the workspace\n\nPick a short kebab slug for the effort, such as `auth-rework` or `payments-v2`. Stamp the date once so\nthe docs are dateable on resume:\n\n```\ndate +%Y-%m-%d\n```\n\nCreate the workspace directory (houserules already installed `.claude\u002Fplans\u002F.gitignore`):\n\n```\nmkdir -p .claude\u002Fplans\u002F\u003Cslug>\n```\n\nEverything under `.claude\u002Fplans\u002F` is **gitignored by default**. It's your living project state, not a\ncommit artifact, and it churns every phase. To share a plan with the team, `git add -f` it or delete\n`.claude\u002Fplans\u002F.gitignore`.\n\n## 2. Design the phases\n\nBreak the work into **coarse phases**, typically 2 to 6. If you have a dozen, you're listing steps,\nnot phases. Each phase must:\n\n- land independently and leave the tree in a working state, and\n- have a **falsifiable \"done\"**, the acceptance you could actually check (a test passes, a route\n  returns 200, a flag flips).\n\nCut the phases **vertically**, so each one is a thin end-to-end path someone can actually touch,\nrather than a layer of the stack. The default pull is horizontal, a schema phase then a service\nphase then a UI phase, and that shape has no working tree and no falsifiable acceptance until the\nlast phase lands. Prefer one narrow feature wired all the way through over one whole layer built for\nfeatures that do not exist yet.\n\nRead independence off the finished cut, do not manufacture it. When two phases name disjoint path\nroots and neither reads the other's output, mark them `After: none` (or the phases they really wait\non) so they can run together. Re-cutting horizontally to make lanes brings back the no-working-tree\nfailure described above.\n\nGround the phases in the real code, not guesses. Read the repo's own docs and run targeted greps\nfirst. If a subsystem is unfamiliar, fan out **one read-only Explore subagent** to map its seams\nbefore you commit to a phase boundary, and fan out only for what the docs and greps don't answer. For\nthe design thinking itself, plan mode and the Plan agent are available. This skill's job is to\n**persist** the result, not to replace them.\n\nA phase whose work is answering questions rather than writing code can name the `research-spike`\nagent in its sub-plan, one spike per scoped question set, each writing one report into the plan\nworkspace. A follow-up synthesis step names `research-synth` to merge those reports into one\nreference document, resolving contradictions explicitly. Both agents are optional installs from the\n`research` module. When they are absent, the phase says what to research and the implementer does it\nin-context.\n\n## 3. Write the three doc types\n\nCreate these under `.claude\u002Fplans\u002F\u003Cslug>\u002F`. Keep each lean and cross-linked, with relative links so\nthe workspace is self-contained. A phase that records its spec in `## Reference` is what lets\n`\u002Forchestrate` hand that spec to the slice it judges, as the brief's `Reference:` line.\n\n**`PLAN.md`** is the stable overview: goal plus approach, and it rarely changes once set.\n\n```markdown\n# PLAN: \u003Cslug>\n\n**Created:** \u003Cdate> · **Status:** see [ROADMAP.md](ROADMAP.md)\n\n## Goal\n\n\u003COne paragraph: what we're building and why. The problem, not the steps.>\n\n## Approach\n\n\u003CThe high-level strategy: key decisions, constraints, explicit non-goals.>\n\n## Phases\n\n1. **\u003Cname>**: \u003Cone line> → [phase-1-\u003Cslug>.md](phase-1-\u003Cslug>.md)\n2. **\u003Cname>**: \u003Cone line> → [phase-2-\u003Cslug>.md](phase-2-\u003Cslug>.md)\n\n## Key files & interfaces\n\n\u003CThe load-bearing files\u002FAPIs this work touches, and where a resuming session should look first.>\n```\n\n**`ROADMAP.md`** is the **living** status doc, the one file resume reads first.\n\n```markdown\n# ROADMAP: \u003Cslug>\n\n**Status:** IN PROGRESS · **Started:** \u003Cdate> · **Updated:** \u003Cdate>\n\n> Resuming? Read this file's status lines below. Do not re-derive scope from the transcript.\n\n## Phases\n\n- [x] **Phase 1: \u003Cname>** · Status: DONE (\u003Cdate>) · [sub-plan](phase-1-\u003Cslug>.md)\n- [~] **Phase 2: \u003Cname>** · Status: IN PROGRESS · [sub-plan](phase-2-\u003Cslug>.md)\n- [ ] **Phase 3: \u003Cname>** · Status: TODO · [sub-plan](phase-3-\u003Cslug>.md) · After: none\n\n## Log\n\n- \u003Cdate>: \u003Cone line on what changed \u002F what's next>\n```\n\nStatus vocabulary is fixed so it's greppable: **`TODO` · `IN PROGRESS` · `DONE` · `BLOCKED`**.\nCheckboxes mirror it: `[ ]` todo, `[~]` in progress, `[x]` done.\n\nThe optional trailing `After` segment sets order. Absent means the phase waits on the line above it,\nand the first line waits on nothing. `none` means no dependency, and does not reset the chain for the\nline below. A list such as `After: 2, 3` names the phases that must be `DONE` first.\n\n**`phase-N-\u003Cslug>.md`** is one file per phase, the working record for that slice.\n\n```markdown\n# Phase N: \u003Cname>\n\n**Status:** TODO · **Part of:** [PLAN.md](PLAN.md) · **Roadmap:** [ROADMAP.md](ROADMAP.md)\n**Signals:** \u003Coptional: `wide` for a big footprint, `ui` for user-facing surfaces, else omit the line>\n**Domain:** \u003Coptional: comma-separated path roots this phase may write, each in backticks, never a glob. Omit the line for `all`>\n\n## Objective\n\n\u003CWhat \"done\" means here: the falsifiable acceptance from step 2.>\n\n## Reference\n\n\u003CRelative links to any spec, format, or standard this phase's work must conform to, or \"none\".>\n\n## Steps\n\n- [ ] \u003Cstep: the decision made, plus the acceptance that shows it holds. Never a code block>\n- [ ] \u003Cstep>\n\nSelf-check before handing off: if fenced code is more than a tenth of a phase file's lines, the\nplan is implementing. Move the code into a \"decisions\" bullet as prose, or drop it. `plan-lint`\nwarns above that share.\n\n## Review Focus\n\n\u003COptional: up to five inputs or failure modes the spec implies but no step's tests exercise.>\n\n- \u003Cthe input or failure mode: what must hold, pinned by `path\u002Fto\u002F__tests__\u002Fowning-step.test.ts`>\n\n## Notes & decisions\n\n\u003CCaptured as you implement: what you chose, what you ruled out, surprises. This is the durable\nmemory that survives the transcript.>\n```\n\n`## Review Focus` lists the inputs and failure modes the spec implies but no step's tests exercise,\nso a reviewer knows where to look. Five items is the cap. Each item names the test file that pins it\nin backticks, in the step that owns the code. `plan-lint` warns past five items and on an item that\nnames no test path. Omit the section when every case the spec implies already has a test.\n\nThe optional `**Signals:**` line is read by `\u002Forchestrate` where that skill is installed: `wide`\nturns on its pre-slicing `\u002Fblast-radius` map and `ui` its close-of-phase accessibility and design\nreviews. Omit the line when neither applies.\n\nFor a control-flow-heavy phase, one where the hard part is which function calls which and in what\norder, add an optional call-stack sketch to that phase file: the call tree in diff syntax, with `+`\non the frames the phase adds and `-` on the ones it removes. Pin the signatures those frames depend\non in `## Reference` beside it, so a slice implementing one frame compiles against the same shape as\nthe slice implementing its caller.\n\n## 4. Stop and hand off\n\nThe scaffold **is** the deliverable. Do not open phase 1. Do not edit a source file. Do not dispatch a\nsubagent to start. Every phase in the ROADMAP stays `TODO`.\n\nThis is a hard stop, not a suggestion. The point of writing the plan down is that the user gets to\nread it and change it before any code moves, and a skill that slides from planning into implementing\ntakes that away. A phase that looks small enough to just do is still the user's call.\n\nBefore the report, dispatch one `plan-reviewer` on the workspace path with\n`subagent_type: \"plan-reviewer\"` and wait for its list. It reads the finished plan as the person who\nwould build it and returns what that person would still have to ask. Carry each question into the\nhandoff under the assumptions line, or say the list was empty. It costs one `plan-reviewer` run\nand catches a mis-specified slice before a worker spends a run on it. Do not edit the plan to\nanswer a question. The user decides.\n\nReport, then wait:\n\n- the resolved slug and the workspace path,\n- the phases, one line each, in order,\n- anything you had to assume or couldn't resolve while planning,\n- the next command, so starting is one keystroke. When any phase carries an `After` that is not the\n  chain, name the first ready set, with `\u002Forchestrate \u003Cslug> all` as the command and the `2,3` form\n  as the explicit one:\n  - `\u002Forchestrate \u003Cslug> 1` fans out scoped workers for phase 1 (needs the `orchestrate` module).\n  - Or the user asks you to take phase 1 in-context.\n- the execution mode, with its cost, and a recommendation. `\u002Forchestrate` runs workers per slice and\n  pays for briefs, dispatch, and review, which is worth it above roughly two slices. In-context is\n  one pass and cheaper below that. Recommend one for this plan and give the reason from its own phase\n  sizes. The user still makes the choice.\n\nWhoever picks it up works in `After` order, concurrently where the ROADMAP allows. Before starting a phase, they\nset its ROADMAP line and sub-plan header to `IN PROGRESS`, then tick the sub-plan's step checkboxes as\nthey go. Don't smuggle a later phase's work into the current one. The point is that each phase lands\ncleanly.\n\n## 5. Status in place (for whoever implements)\n\nThe instant a phase lands and its acceptance actually passes, update **both** the ROADMAP line\n(`[x]` \u002F `Status: DONE (\u003Cdate>)`) and the sub-plan header, in the same edit pass, before moving on. A\nstale ROADMAP is worse than none, because it lies to the next session. Add a one-line `## Log` entry\nwith the date and what's next, and bump the `**Updated:**` date. If a phase is blocked, mark it\n`BLOCKED` and note why in the sub-plan. Don't leave it silently `IN PROGRESS`. Under nested `\u002Forchestrate` the ROADMAP line is the dispatcher's\nwrite, per `references\u002Fnested.md`.\n\nIf `.claude\u002Fscripts\u002Fplan-lint.mjs` is installed, run `node .claude\u002Fscripts\u002Fplan-lint.mjs` after\nthe edit. It checks every phase's status cell against the fixed vocabulary and cross-checks each\nROADMAP line against the sub-plan header it links to, so a pass that missed one half of the\nupdate does not sit undetected until the next resume.\n\nBefore the workspace is discarded, re-read the phase's `## Notes & decisions` and offer to promote\nanything durable with `\u002Fdecide`. It proposes, it does not bulk-write. Most notes are not decisions,\nand a bulk write is how a decision log fills with diary. Apply the bar from the `decide` skill: not\nobvious from the code, a competent person could have chosen otherwise, and re-deriving it costs real\ntime. A note that records something decided and then reversed mid-phase graduates as two linked\nrecords, the first decision and a second that supersedes it, never flattened into one. Skip this step\nsilently if `.claude\u002Fscripts\u002Fdecision-log.mjs` is absent, since the `decisions` module is optional.\n\nWhen the plan itself changes and a phase splits, drops, or reorders, edit PLAN.md and ROADMAP.md to\nmatch reality. The docs track what you're _actually_ doing, not the original guess.\n\n## 6. Resume discipline\n\nReturning to this work in a new session, or after a detour? Read `ROADMAP.md` first. Grep for the live\nphase instead of reconstructing state from scrollback:\n\n```\ngrep -n 'Status: IN PROGRESS\\|Status: BLOCKED' .claude\u002Fplans\u002F\u003Cslug>\u002FROADMAP.md\n```\n\nOpen the matching sub-plan for its steps and notes, then continue. Only fall back to reading the diff\nor transcript for detail the docs don't capture.\n\n## 7. Finishing\n\nWhen every phase is `DONE`, flip the ROADMAP header to `**Status:** DONE`, add a final `## Log` line,\nand give the user the acceptance checklist: the per-phase \"done\" criteria, now checkable. The\nworkspace stays on disk as the project's record, and it's gitignored, so it never enters a commit. If\nthe user wants the plan gone, delete `.claude\u002Fplans\u002F\u003Cslug>\u002F` and leave `.claude\u002Fplans\u002F.gitignore`.\n","Plan a multi-phase implementation as a persisted project: **$ARGUMENTS**\n\n**This skill plans. It does not implement.** It ends at a scaffolded workspace and a handoff (§4).\nStarting phase 1 is the user's call, not a continuation of planning.\n\nOne discipline makes this cheaper than re-planning from scratch each session. The plan lives on disk,\nnot in the transcript, and **`ROADMAP.md` is the single source of truth for what's done**. Every phase\nupdates its status _in place_ the moment it lands, so resuming is a grep rather than a re-derivation\nfrom scrollback.\n\n## 0. How much ceremony does this earn?\n\nThere are three tiers, and the ask lands in exactly one:\n\n- **Do it inline.** A handful of files you will finish now, with the shape already obvious. Write no\n  plan at all.\n- **Plan inline, persist nothing.** Enough moving parts to be worth thinking through first, but still\n  one sitting. Use plan mode or an in-context plan and scaffold no `.claude\u002Fplans\u002F` dir.\n- **Persist a workspace.** The rest of this skill.\n\nName the tier out loud before doing anything, in one sentence, with the reason you picked it. The\nuser can then override it in a word. Silently scaffolding is the failure this prevents, since a\n`.claude\u002Fplans\u002F` dir for a one-sitting task is pure overhead that no one asks you to delete.\n\nThe top tier has a bar. Scaffold **only** when at least one holds:\n\n- **3+ distinct phases** that can land independently and each leave the tree working.\n- Work you expect to **pause and resume** across sessions or days.\n- Enough moving parts that \"what's left?\" won't be obvious from `git diff` alone.\n\nWhen it's a genuine toss-up between the middle tier and this one, ask the user whether to track it\nas a project.\n\n## 1. Name the plan and scaffold the workspace\n\nPick a short kebab slug for the effort, such as `auth-rework` or `payments-v2`. Stamp the date once so\nthe docs are dateable on resume:\n\n```\ndate +%Y-%m-%d\n```\n\nCreate the workspace directory (houserules already installed `.claude\u002Fplans\u002F.gitignore`):\n\n```\nmkdir -p .claude\u002Fplans\u002F\u003Cslug>\n```\n\nEverything under `.claude\u002Fplans\u002F` is **gitignored by default**. It's your living project state, not a\ncommit artifact, and it churns every phase. To share a plan with the team, `git add -f` it or delete\n`.claude\u002Fplans\u002F.gitignore`.\n\n## 2. Design the phases\n\nBreak the work into **coarse phases**, typically 2 to 6. If you have a dozen, you're listing steps,\nnot phases. Each phase must:\n\n- land independently and leave the tree in a working state, and\n- have a **falsifiable \"done\"**, the acceptance you could actually check (a test passes, a route\n  returns 200, a flag flips).\n\nCut the phases **vertically**, so each one is a thin end-to-end path someone can actually touch,\nrather than a layer of the stack. The default pull is horizontal, a schema phase then a service\nphase then a UI phase, and that shape has no working tree and no falsifiable acceptance until the\nlast phase lands. Prefer one narrow feature wired all the way through over one whole layer built for\nfeatures that do not exist yet.\n\nRead independence off the finished cut, do not manufacture it. When two phases name disjoint path\nroots and neither reads the other's output, mark them `After: none` (or the phases they really wait\non) so they can run together. Re-cutting horizontally to make lanes brings back the no-working-tree\nfailure described above.\n\nGround the phases in the real code, not guesses. Read the repo's own docs and run targeted greps\nfirst. If a subsystem is unfamiliar, fan out **one read-only Explore subagent** to map its seams\nbefore you commit to a phase boundary, and fan out only for what the docs and greps don't answer. For\nthe design thinking itself, plan mode and the Plan agent are available. This skill's job is to\n**persist** the result, not to replace them.\n\nA phase whose work is answering questions rather than writing code can name the `research-spike`\nagent in its sub-plan, one spike per scoped question set, each writing one report into the plan\nworkspace. A follow-up synthesis step names `research-synth` to merge those reports into one\nreference document, resolving contradictions explicitly. Both agents are optional installs from the\n`research` module. When they are absent, the phase says what to research and the implementer does it\nin-context.\n\n## 3. Write the three doc types\n\nCreate these under `.claude\u002Fplans\u002F\u003Cslug>\u002F`. Keep each lean and cross-linked, with relative links so\nthe workspace is self-contained. A phase that records its spec in `## Reference` is what lets\n`\u002Forchestrate` hand that spec to the slice it judges, as the brief's `Reference:` line.\n\n**`PLAN.md`** is the stable overview: goal plus approach, and it rarely changes once set.\n\n```markdown\n# PLAN: \u003Cslug>\n\n**Created:** \u003Cdate> · **Status:** see [ROADMAP.md](ROADMAP.md)\n\n## Goal\n\n\u003COne paragraph: what we're building and why. The problem, not the steps.>\n\n## Approach\n\n\u003CThe high-level strategy: key decisions, constraints, explicit non-goals.>\n\n## Phases\n\n1. **\u003Cname>**: \u003Cone line> → [phase-1-\u003Cslug>.md](phase-1-\u003Cslug>.md)\n2. **\u003Cname>**: \u003Cone line> → [phase-2-\u003Cslug>.md](phase-2-\u003Cslug>.md)\n\n## Key files & interfaces\n\n\u003CThe load-bearing files\u002FAPIs this work touches, and where a resuming session should look first.>\n```\n\n**`ROADMAP.md`** is the **living** status doc, the one file resume reads first.\n\n```markdown\n# ROADMAP: \u003Cslug>\n\n**Status:** IN PROGRESS · **Started:** \u003Cdate> · **Updated:** \u003Cdate>\n\n> Resuming? Read this file's status lines below. Do not re-derive scope from the transcript.\n\n## Phases\n\n- [x] **Phase 1: \u003Cname>** · Status: DONE (\u003Cdate>) · [sub-plan](phase-1-\u003Cslug>.md)\n- [~] **Phase 2: \u003Cname>** · Status: IN PROGRESS · [sub-plan](phase-2-\u003Cslug>.md)\n- [ ] **Phase 3: \u003Cname>** · Status: TODO · [sub-plan](phase-3-\u003Cslug>.md) · After: none\n\n## Log\n\n- \u003Cdate>: \u003Cone line on what changed \u002F what's next>\n```\n\nStatus vocabulary is fixed so it's greppable: **`TODO` · `IN PROGRESS` · `DONE` · `BLOCKED`**.\nCheckboxes mirror it: `[ ]` todo, `[~]` in progress, `[x]` done.\n\nThe optional trailing `After` segment sets order. Absent means the phase waits on the line above it,\nand the first line waits on nothing. `none` means no dependency, and does not reset the chain for the\nline below. A list such as `After: 2, 3` names the phases that must be `DONE` first.\n\n**`phase-N-\u003Cslug>.md`** is one file per phase, the working record for that slice.\n\n```markdown\n# Phase N: \u003Cname>\n\n**Status:** TODO · **Part of:** [PLAN.md](PLAN.md) · **Roadmap:** [ROADMAP.md](ROADMAP.md)\n**Signals:** \u003Coptional: `wide` for a big footprint, `ui` for user-facing surfaces, else omit the line>\n**Domain:** \u003Coptional: comma-separated path roots this phase may write, each in backticks, never a glob. Omit the line for `all`>\n\n## Objective\n\n\u003CWhat \"done\" means here: the falsifiable acceptance from step 2.>\n\n## Reference\n\n\u003CRelative links to any spec, format, or standard this phase's work must conform to, or \"none\".>\n\n## Steps\n\n- [ ] \u003Cstep: the decision made, plus the acceptance that shows it holds. Never a code block>\n- [ ] \u003Cstep>\n\nSelf-check before handing off: if fenced code is more than a tenth of a phase file's lines, the\nplan is implementing. Move the code into a \"decisions\" bullet as prose, or drop it. `plan-lint`\nwarns above that share.\n\n## Review Focus\n\n\u003COptional: up to five inputs or failure modes the spec implies but no step's tests exercise.>\n\n- \u003Cthe input or failure mode: what must hold, pinned by `path\u002Fto\u002F__tests__\u002Fowning-step.test.ts`>\n\n## Notes & decisions\n\n\u003CCaptured as you implement: what you chose, what you ruled out, surprises. This is the durable\nmemory that survives the transcript.>\n```\n\n`## Review Focus` lists the inputs and failure modes the spec implies but no step's tests exercise,\nso a reviewer knows where to look. Five items is the cap. Each item names the test file that pins it\nin backticks, in the step that owns the code. `plan-lint` warns past five items and on an item that\nnames no test path. Omit the section when every case the spec implies already has a test.\n\nThe optional `**Signals:**` line is read by `\u002Forchestrate` where that skill is installed: `wide`\nturns on its pre-slicing `\u002Fblast-radius` map and `ui` its close-of-phase accessibility and design\nreviews. Omit the line when neither applies.\n\nFor a control-flow-heavy phase, one where the hard part is which function calls which and in what\norder, add an optional call-stack sketch to that phase file: the call tree in diff syntax, with `+`\non the frames the phase adds and `-` on the ones it removes. Pin the signatures those frames depend\non in `## Reference` beside it, so a slice implementing one frame compiles against the same shape as\nthe slice implementing its caller.\n\n## 4. Stop and hand off\n\nThe scaffold **is** the deliverable. Do not open phase 1. Do not edit a source file. Do not dispatch a\nsubagent to start. Every phase in the ROADMAP stays `TODO`.\n\nThis is a hard stop, not a suggestion. The point of writing the plan down is that the user gets to\nread it and change it before any code moves, and a skill that slides from planning into implementing\ntakes that away. A phase that looks small enough to just do is still the user's call.\n\nBefore the report, dispatch one `plan-reviewer` on the workspace path with\n`subagent_type: \"plan-reviewer\"` and wait for its list. It reads the finished plan as the person who\nwould build it and returns what that person would still have to ask. Carry each question into the\nhandoff under the assumptions line, or say the list was empty. It costs one `plan-reviewer` run\nand catches a mis-specified slice before a worker spends a run on it. Do not edit the plan to\nanswer a question. The user decides.\n\nReport, then wait:\n\n- the resolved slug and the workspace path,\n- the phases, one line each, in order,\n- anything you had to assume or couldn't resolve while planning,\n- the next command, so starting is one keystroke. When any phase carries an `After` that is not the\n  chain, name the first ready set, with `\u002Forchestrate \u003Cslug> all` as the command and the `2,3` form\n  as the explicit one:\n  - `\u002Forchestrate \u003Cslug> 1` fans out scoped workers for phase 1 (needs the `orchestrate` module).\n  - Or the user asks you to take phase 1 in-context.\n- the execution mode, with its cost, and a recommendation. `\u002Forchestrate` runs workers per slice and\n  pays for briefs, dispatch, and review, which is worth it above roughly two slices. In-context is\n  one pass and cheaper below that. Recommend one for this plan and give the reason from its own phase\n  sizes. The user still makes the choice.\n\nWhoever picks it up works in `After` order, concurrently where the ROADMAP allows. Before starting a phase, they\nset its ROADMAP line and sub-plan header to `IN PROGRESS`, then tick the sub-plan's step checkboxes as\nthey go. Don't smuggle a later phase's work into the current one. The point is that each phase lands\ncleanly.\n\n## 5. Status in place (for whoever implements)\n\nThe instant a phase lands and its acceptance actually passes, update **both** the ROADMAP line\n(`[x]` \u002F `Status: DONE (\u003Cdate>)`) and the sub-plan header, in the same edit pass, before moving on. A\nstale ROADMAP is worse than none, because it lies to the next session. Add a one-line `## Log` entry\nwith the date and what's next, and bump the `**Updated:**` date. If a phase is blocked, mark it\n`BLOCKED` and note why in the sub-plan. Don't leave it silently `IN PROGRESS`. Under nested `\u002Forchestrate` the ROADMAP line is the dispatcher's\nwrite, per `references\u002Fnested.md`.\n\nIf `.claude\u002Fscripts\u002Fplan-lint.mjs` is installed, run `node .claude\u002Fscripts\u002Fplan-lint.mjs` after\nthe edit. It checks every phase's status cell against the fixed vocabulary and cross-checks each\nROADMAP line against the sub-plan header it links to, so a pass that missed one half of the\nupdate does not sit undetected until the next resume.\n\nBefore the workspace is discarded, re-read the phase's `## Notes & decisions` and offer to promote\nanything durable with `\u002Fdecide`. It proposes, it does not bulk-write. Most notes are not decisions,\nand a bulk write is how a decision log fills with diary. Apply the bar from the `decide` skill: not\nobvious from the code, a competent person could have chosen otherwise, and re-deriving it costs real\ntime. A note that records something decided and then reversed mid-phase graduates as two linked\nrecords, the first decision and a second that supersedes it, never flattened into one. Skip this step\nsilently if `.claude\u002Fscripts\u002Fdecision-log.mjs` is absent, since the `decisions` module is optional.\n\nWhen the plan itself changes and a phase splits, drops, or reorders, edit PLAN.md and ROADMAP.md to\nmatch reality. The docs track what you're _actually_ doing, not the original guess.\n\n## 6. Resume discipline\n\nReturning to this work in a new session, or after a detour? Read `ROADMAP.md` first. Grep for the live\nphase instead of reconstructing state from scrollback:\n\n```\ngrep -n 'Status: IN PROGRESS\\|Status: BLOCKED' .claude\u002Fplans\u002F\u003Cslug>\u002FROADMAP.md\n```\n\nOpen the matching sub-plan for its steps and notes, then continue. Only fall back to reading the diff\nor transcript for detail the docs don't capture.\n\n## 7. Finishing\n\nWhen every phase is `DONE`, flip the ROADMAP header to `**Status:** DONE`, add a final `## Log` line,\nand give the user the acceptance checklist: the per-phase \"done\" criteria, now checkable. The\nworkspace stays on disk as the project's record, and it's gitignored, so it never enters a commit. If\nthe user wants the plan gone, delete `.claude\u002Fplans\u002F\u003Cslug>\u002F` and leave `.claude\u002Fplans\u002F.gitignore`.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Read, Edit, Write, Grep, Glob, Bash, Agent","\u003Cwhat to build>","main","039f153ef841e9e6f26430b3e17ea428d8a3ce06","packages\u002Fcli\u002Fpayload\u002Fskills\u002Fplan-project",0,"https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules","https:\u002F\u002Fgithub.com\u002FDTCurrie","Engineering Lead at @viamrobotics, specializing in 2D and 3D visualizations.","2026-11-13 21:14:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add DTCurrie\u002Fhouserules --skill plan-project",{"tool":40,"command":41},"bunx","bunx skills add DTCurrie\u002Fhouserules --skill plan-project",{"tool":43,"command":44},"pnpm","pnpm dlx skills add DTCurrie\u002Fhouserules --skill plan-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fpayload\u002Fskills\u002Fplan-project\u002FSKILL.md",true,[],[49,56,63,70,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M780QVJX363SHD100WRD4TD0","pr-description","Write the pull request description for a change as a pasteable markdown body. Use before opening or updating a PR, or when asked for a PR body, PR summary, or gh pr create text.","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-prose\u002Fpayload\u002Fskills\u002Fpr-description\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M780QR0V9D4AJHTPN1NJHQRG","ledger-sync","Push the backlog and decision ledgers to GitHub Projects (issues and project board items). Use when the user asks to sync, push, or upload to GitHub Projects or the project board.","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-github\u002Fpayload\u002Fskills\u002Fledger-sync\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M780QKAY9PW98XRYGQFNDEMP","backlog-adopt","Adopt a reported GitHub issue into the backlog ledger and the linked project board. Use to triage or track a GitHub issue or bug report as a backlog entry.","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-github\u002Fpayload\u002Fskills\u002Fbacklog-adopt\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M780QJ4B917TCZM76X55NKQE","design-review","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-design\u002Fpayload\u002Fskills\u002Fdesign-review\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M780QEV3HGXEWMWG5VJEFF0J","chrome-devtools-mode","Switch the Chrome DevTools MCP server between its full 29-tool surface and the slim 3-tool one (--slim). Use when asked to change, shrink, or restore the chrome-devtools MCP tool surface.","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-design\u002Fpayload\u002Fskills\u002Fchrome-devtools-mode\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M780Q9MX9ADN41RZKQ47B8CT","decide","Record a decision to the decision ledger, with the rejected alternative and revisit trigger. Use when a discussion settles a design question or a new decision supersedes a prior one.","https:\u002F\u002Fgithub.com\u002FDTCurrie\u002Fhouserules\u002Fblob\u002Fmain\u002Fpackages\u002Fplugin-decisions\u002Fpayload\u002Fskills\u002Fdecide\u002FSKILL.md",[],[]]