Use when something non-trivial is to be built or reworked and its implementation plan has to be written, from an idea or from a board, or when a plan has to be redrawn after an increment landed. Produces, through an interview, the one plan document that holds the design, the decisions, the phases and seats, the tracker execute-plan runs from and the orchestrator's mandate. Not for keeping an open discussion (brainstorm), not for writing a phase's tasks (orchestrate-plan, at the phase's open) and not for carrying the plan out (execute-plan).
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
One document holds the design and the plan. What the interview settles is written once, there, and each task points into it, narrowed to its scope.
The plan is written for an agent that was not in the conversation. Read alone, it gives every decision, its reason and every detail the work needs, so that agent is as aligned as the person and you are now. Nothing settled lives only in the chat.
No code in the repository for the thing being planned until the plan is approved.
YYYY-MM-DD-<topic>.plan.md before the first question, through the aiview skill: kind plan, tags = topic, in the group aiview gives a plan, shared with its task documents when a task needs one. With a roadmap, the slot's slug is a tag. Its two parts, Design and Execution, are references/skeleton.md, read before writing the first section. A board on the topic is the starting point: its agreed decisions become rows, numbered in this plan with the board's id in their source (board <topic>.board#D2), and are not asked again.interview skill on the decisions table, and write each section as its decisions land. If the person declines it, offer its short mode; a decision still unasked is a row with source agent default. A request that is several independent systems is split first, one plan each. One plan per increment: it stops where the next increment would begin.deepen-module skill says, in the plan's modules section. A module the interview cannot settle there gets its own module document, and the plan quotes its entry.
Each guide that applies (the shipped guide-* skills, the project's .claude/skills/guide-*) gets its decision for this plan in the plan's Guides section.swarm-board skill. Read references/phases.md now; then ask phases:, seats: and verify:, one per message, as the orchestrate-plan skill's references/mandate.md says.references/phases.md and the orchestrate skill's references/tasks.md say, and draw the tracker to references/tracker.md, from references/tracker-skeleton.md, both read first. The execute-plan skill keeps it from then on. aiview mermaid-check <plan>, aiview tracker check <plan> and scripts/decisions.mjs <the plan's folder> after every edit: the last says whether a topic, an id or a citation collides or points nowhere.cold-read skill, with the plan's id and none of the conversation; discuss with it as a peer, explaining your intent and asking how it read each part, until you understand each other; every point you settle goes into the plan, and it re-reads until it says ready.orchestrate-plan skill's references/mandate.md, the answers in the plan's Mandate section and in the one line under the tracker. tests: at the plan end adds the tests phase to the tracker then. Whatever the mandate changed in the plan, the cold reader re-reads, until it says ready again.agent default rows, numbered, contract ones first, "4 decisions are mine: … confirm them, or name the ones to change", and the link to the plan comes after the list. The approval goes in the status line with the defaults it confirmed, then aiview plan check <plan>. No task is written now: each is written at its phase's open.| Thought | Reality |
|---|---|
| "I'll plan the whole feature while I have the context" | The next plan is written with this increment's learning in hand, which you do not have yet. |
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use whenever a document is produced for the user to read and react to while it evolves: a brainstorm board, a plan, a design language, a prototype, a PR analysis, a review report, a live PDF. Also when a document must be registered, opened, listed, moved or retired, or a prototype's bindings checked. Not for code, tests or configuration, or any file nobody opens in a browser.
中文简介正在准备中。当前显示原文说明。
Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was investigated. Not for a swarm of seats working it (brainswarm), not for an implementation plan and not for bug fixes.
中文简介正在准备中。当前显示原文说明。
Use when a person wants a swarm of role seats to work a topic on the swarm board under a chosen protocol: a brainstorm (ideas before any judgment), a debate (questions argued to decisions, a skeptic endorsing) or an editorial (one text drafted, read by seats standing for its readers, revised), a protocol or template the project keeps as a `protocol-<name>` skill (or an older `brainswarm-<name>` one), or a custom protocol recommended for the person's intent, or a seat's brief names a brainswarm protocol. Produces the run's record in aiview, written by the orchestrator alone. Not for one person thinking aloud with the agent (brainstorm, interview) and not for a plan's slices (execute-plan).
中文简介正在准备中。当前显示原文说明。
Use when dispatched to cold-read a plan, as an agent that was not in the conversation that wrote it, to say whether it can be carried out from the document alone. Produces what the reader would build, its questions, and a verdict, ready or not ready, repeated as the writer fixes the plan. Not for judging the design (interview, pr-review), not for the mechanical checks (aiview plan check, tracker check), and not for writing the plan (write-plan).
中文简介正在准备中。当前显示原文说明。
Use when code is hard to follow and is to be audited or reworked: long if/else or switch chains, cascades of type checks or parse attempts, kind fields compared to strings, flag parameters, deep nesting, a function hard to read. Also for complexity guardrails, or one long conditional function pasted. Produces a ranked audit of families, one family reworked behind characterization tests, or the guardrails.
中文简介正在准备中。当前显示原文说明。
Use when a page is wanted to work on something with the person during development, fed the project's real data (comparing model answers, walking an agent call by call, measuring an output against its template), when such a workbench has to change, be reworked or its feed broke, or mid-session when turns went into aligning with the person on how to do a kind of work that recurs and real project data could show it. Produces the page in aiview, kind `workbench`, and the project's `workbench-<bench>` skill with its feed and operating steps. Not for designing a product screen (design-prototype) or verifying user stories (verification-skill-create).
中文简介正在准备中。当前显示原文说明。