plan
Use after design approval for milestone plans with executable acceptance.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- plan
- description
- Use after design approval for milestone plans with executable acceptance.
03 SKILL.md 正文
Plan
docs/staging/plans/YYYY-MM-DD-<topic>.md. Reference the spec; don't restate it.
If unresolved spec notes affect implementation or task order, return to design.
Multi-module plan
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md. Open the workspace plan with the declaration block (topology: multi-module, change-set, coordinator, repos, module plan paths, integration task) - it is the on-disk mode marker downstream skills rely on.
- Write the workspace plan in the coordinator repository and a module plan in every affected module's owning repository.
- The workspace plan lists the change-set ID, coordinator, repositories, module plan paths, and the integration task.
- Every task names exactly one
repository:and onemodule:. Cross-module verification is anintegrationtask owned by the coordinator. - Order contract tasks before consumers, local acceptance before integration, and integration before linked commits.
- Mark tasks parallel only when they have independent write scopes and acceptance.
- Adding a repository after implementation starts: update the declaration block and confirm with the user. Return to
designonly if the addition changes a shared contract.
Rolling wave
Spec references a milestone (milestone: MN)? Check docs/ROADMAP.md — expand only that milestone. Leave the rest as stubs.
After ship: open docs/ROADMAP.md, confirm which milestone is next, then expand it. Return to design only if the milestone's goal materially changed.
Milestone tasks (30-60 min each)
Every task is - [ ] T<n>: <name> - always a checkbox, never a heading. tdd/subagents flip it to - [x] on completion; ship refuses to run while any - [ ] remains.
goal: <one sentence>
files: <paths>
acceptance: <test or cmd>
spec: <docs/staging/specs/...#anchor>
No exact code. No step-by-step. Acceptance is verifiable: a test, command, or scripted check — or, when none is possible, an explicit manual check (steps + expected result). Each task leaves the repo green.
Mark independent tasks: [parallel] T3, T4, T5.
Only mark [parallel] when shared contracts, state, errors, and acceptance are closed.
Atomic expansion is deferred until dispatch time - subagents expands a milestone into 2-5 min steps at dispatch time, not here.
for New project: derive an initialization task — scaffold code, tests, CI, and always include: README.md, CHANGELOG.md, .gitignore, and a Makefile (or equivalent task runner config).
Don't put in the plan
background, architecture, rationale (spec), CI commands, copy-pasted acceptance.
Hand off
<gate> The plan must exist on disk before handing off to tdd/subagents. For multi-module work, this means the coordinator workspace plan and every affected module plan in its owning repository. </gate>
Confirm plan with the user.
mostly [parallel] → subagents. Otherwise → tdd.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.