Manage and inspect a book project's public work board: organize workstreams, notes, milestones, and tasks, and update their status as work changes. Use it to materialize proposals, track blockers, or check current board state.
中文简介正在准备中。当前显示英语简介。
Arrange the repository's public .pm board for the book — show status, create workstreams, capture inbox notes, promote notes into milestones, add tasks, mark work done, park blocked work, and drop unwanted work. Use only when the user explicitly invokes /pm or asks to update, arrange, or check the .pm board. Do not use for proposing new work (that is pm-brainstorm) or for ordinary chapter edits.
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
.pm boardUsage: /pm [status | new workstream <title> | add <wN> <idea> | promote <wN/NNN> | new milestone <wN> <title> | add-task <wN/mN> <title> | done <wN/mN/tNNN or wN/NNN> | block <target> <reason> | unblock <target> | drop <target> <reason>]
/pm is the only skill that writes to .pm/. /pm-brainstorm proposes; /pm materializes; /loopx drains. This file is the canonical definition of board conventions. Parse the subcommand from $ARGUMENTS (default status).
The board exists to make System Design and Architecture the best open, bilingual (en / zh-CN) system-design book. Sequence work by reader impact, not by what is fun to write. Every milestone names one pillar in ## Source + Goal linkage:
| Pillar | Meaning |
|---|---|
| B1 — Content quality | New or improved chapters: correct, current, concrete (numbers, tradeoffs, diagrams), following the 4-step framework in AGENTS.md. |
| B2 — Bilingual parity & consistency | en/ and zh-CN/ mirror each other: filenames, front matter, structure, links, indexes (README.md, SUMMARY.md, zh-CN/README.md). |
| B3 — Reach & build health | Discoverability and delivery: tables of contents, cross-links, references, images/diagrams, make build health, tianpan.co sync. |
.pm hierarchy| Level | Path | Meaning | Effort |
|---|---|---|---|
| Workstream | wN/ | a general-purpose worker queue; README.md + inbox notes | — |
| Inbox note | wN/NNN.md | one idea or sub-hour unit of work, plain markdown | ≤ ~1h |
| Milestone | wN/mN/ | shippable chunk: README.md + task files | > ~1h, multiple tasks |
| Task | wN/mN/tNNN.md | single unit | tens of minutes |
.pm/DO_NOT_DO.md; refuse conflicting items.wN/NNN.md, and say why.id: wN/mN/tNNN equals its location; repair drift rather than copying it.README.md checkbox, milestone README.md **Status:** + — **DONE** row marker, task status: frontmatter.wN/mN/done/; milestones with no open tasks → wN/done/mN/; done notes → wN/done/NNN.md. Verify old paths are gone before reporting success.drop removes files and leaves a one-line tombstone under ## Dropped in the workstream README; numbers are never reused; work under done/ is never dropped.blocked/ (wN/blocked/mN/, wN/blocked/NNN.md; tasks stay put with status: blocked) with the exact blocker and an Unblock: condition (and who can clear it).wN/mN. Scan done/, blocked/ and ## Dropped first.worker: worker1 unless the workstream README names another.README.md, SUMMARY.md and zh-CN/README.md; cross-references use https://tianpan.co/notes/<slug>.README.md, SUMMARY.md, zh-CN/README.md entries, front matter parity, cross-links, image paths (../images/<file>). Omit (and say why in Source + Goal linkage) for pure board mechanics./simplify if code/scripts changed); behavior/meaning preserving.AGENTS.md that apply (front-matter/parity check, link check, make build when calibre/gitbook are available) and record what was and wasn't run. No fabricated results.wN/done/mN/ via /pm done once the definition of done actually holds.
Each depends on the prior implementation tasks; all count toward (N tasks). add-task inserts new work before them.status (default)Read the tree (skip done/) and .pm/DO_NOT_DO.md. Per open workstream print milestones with **Status:**, next actionable task, open notes, and everything under blocked/ with its condition. Validate and flag: anti-goal conflicts, missing ## Source + Goal linkage/pillar, vague DoD, completed items still in open tree, blocked items lacking Unblock:. Touch no files.
new workstream <title>Create next wN/README.md from the template. Title must be a generic queue.
add <wN> <idea…>Create next inbox note wN/NNN.md (terse markdown, no frontmatter).
promote <wN/NNN> / new milestone <wN> <title>Apply sizing first. > ~1h and multi-task → create wN/mN/ with README.md + tNNN.md files + standing closing tasks, add - [ ] **mN** — … (N tasks) ← from <source> to the workstream README. Otherwise keep as an inbox note and explain.
add-task <wN/mN> <title>Create next tNNN.md, add its table row before the closing tasks, update their depends_on, fix (N tasks).
done <target>status: done (add ## Closed by triage with evidence if the work landed elsewhere).— **DONE**, update **Status:**.wN/mN/done/tNNN.md.wN/done/mN/ and check - [x].--- + **Resolved <YYYY-MM-DD>** — <what changed>, shipped in <SHA>``, move to wN/done/NNN.md.block <target> <reason> / unblock <target>Block: refuse without a reason; write ## Blocked (blocker, Unblock:, owner, partial work shipped); move per the rules; keep the - [ ] line, retarget its link, append — **blocked:** …. Unblock: verify the condition actually holds, move back, replace the Blocked section with a one-line history, restore links.
drop <target> <reason>Refuse without a reason or for anything under done/. Delete the files (task: also fix table, depends_on, counts, add a ## Dropped line in the milestone README), add - ~~**mN**~~ — <title> — dropped <YYYY-MM-DD>: <reason> under ## Dropped in the workstream README. Propose (don't write) a DO_NOT_DO.md entry if the reason generalizes.
DRY_RUN=1 in arguments → show intended moves, mutate nothing.
README.md# wN — <generic worker-queue title> (<worker>)
**Worker:** <worker> — general-purpose worker; takes the next highest-impact milestone across B1/B2/B3.
## Milestones
- [ ] **mN** — <title> (<N> tasks) ← from <source>
README.md# wN · mN — <name>
**Worker:** <worker> **Goal:** <what shipping achieves> **Status:** todo
## Tasks (in order)
| id | title | est | depends_on |
| ---- | ------- | --- | ---------- |
| t001 | <title> | 30m | — |
## Definition of done
<observable, testable end state>
## Source + Goal linkage
- **Source:** <note / brainstorm / issue>
- **Goal linkage:** <B1/B2/B3 and how>
- **Expected outcome:** <what a reader can now do/find>
- **Why now:** <dependency / risk / sequence>
tNNN.md---
id: wN/mN/tNNN
title: <title>
worker: <worker>
status: todo
estimate: 30m
depends_on: [wN/mN/tMMM]
---
## Objective
## Context
## Steps
## Files
## Acceptance criteria
- [ ] <testable check>
## Out of scope
$ARGUMENTS
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Answer questions about a book, its chapters, or system design by consulting relevant material without changing files. For repository questions, ground the response in the source and cite file paths and lines; use web search for general topics when freshness matters.
中文简介正在准备中。当前显示英语简介。
Work through a `.pm` workstream backlog one actionable item at a time. Triage pending milestones, tasks, and inbox notes, then implement and ship them, close items already satisfied, block work with an unblock condition, or remove invalid items until no actionable work remains.
中文简介正在准备中。当前显示英语简介。
Create concise Mermaid architecture diagrams from a chapter, system, component, dependency flow, or supplied description. The skill checks the diagram syntax before presenting the diagram and a brief explanation of its key flow.
中文简介正在准备中。当前显示英语简介。
Break down a book roadmap topic into prioritized milestone and task proposals, considering reader impact, scope, dependencies, and effort. The skill outputs text for a separate board workflow to apply; it does not write board files.
中文简介正在准备中。当前显示英语简介。
Prepare pending changes on the tracked working branch for publishing: check the branch and repository state, rebase on the latest origin changes, commit selected files, and push. It is intended for an explicit ship or publish request.
中文简介正在准备中。当前显示英语简介。