書籍や章、システム設計について、ファイルを変更せずに資料を読み、根拠を添えて質問に回答します。
- 書籍や章の内容を確認したいとき
- 設計の仕組みを説明してほしいとき
- 変更せず資料の根拠を知りたいとき
`.pm`の作業項目を順に確認し、実装・完了処理・保留・無効項目の整理を進め、対応できる項目がなくなるまで作業します。
Autonomously drain a `.pm` workstream item by item — triage every pending milestone, task, and inbox note, then implement and ship it, close it as already done, block it with an unblock condition, or delete it as invalid, and keep going until nothing actionable remains. Use when the user explicitly invokes /loopx or asks to loop, drain, or work through a whole workstream's backlog (e.g. `/loopx w1`). Sequential, not interval-based; not for timed polls, a single task, or ordinary edits.
実行スコア 未検証
インストール方法を見る.pmの指定された作業系列から、対応可能なマイルストーン、タスク、受信箱のメモを一つずつ選び、現状を確認して処理します。未完了で要望が有効な項目は実装して出荷し、すでに条件を満たしている項目は根拠を添えて完了扱いにします。必要な判断や資料が不足している場合は、解除条件を付けて保留にし、無効・重複などと確認できた項目は削除します。依存関係を考慮して順番に進め、対応可能な項目がなくなるまで続けます。
作業系列に残った複数の項目をまとめて棚卸しし、次々に進めたいときに向いています。単一タスクの実装や定期的な時間間隔での確認ではなく、バックログ全体を処理する依頼に使います。
/loopx w1でこの作業系列を進めて」開始時にブランチがmainであること、既存の未コミット変更がないこと、対象のREADMEと.pm/DO_NOT_DO.mdがあることを確認します。作業は項目ごとに出荷し、.pm/の状態変更は/pmで行います。
この紹介文は、公開されている SKILL.md をもとに AI(OpenAI Codex)が作成しました。正確な仕様は下の原文を確認してください。
インストールする前に、エージェントに与えられる指示の中身を確認できます。
.pm workstream item by itemUsage: /loopx <wN>
Repeatedly pick the next actionable pending item in workstream <wN> (a pending milestone, a pending task in a live milestone, or an open inbox note), triage it, act, /ship it, and continue until nothing actionable remains. Every item ends in exactly one place: implemented and shipped, closed as already done, moved to blocked/ with an unblock condition, or deleted as invalid. Composes /pm (only writer to .pm/), your own writing work, and /ship. If you can name the next pick, keep looping — don't pause for a checkpoint or ask the user to re-run.
A pending item is a claim that the work is still wanted and undone. Boards go stale; never start on the strength of a checkbox alone.
If $ARGUMENTS is empty, STOP and ask which workstream.
git branch --show-current is main; else STOP and ask.git status — pre-existing uncommitted changes you didn't make (other than ignorable .DS_Store) must not ride along; surface and ask..pm/<wN>/README.md exists; else STOP..pm/DO_NOT_DO.md; a conflict is a delete reason.(There is no stop-hook guard in this repo; the Exit rules below are the only enforcement.)
List .pm/<wN>/m*/, *.md, done/, blocked/. Checkbox and disk must agree; if not, trust task files and repair via /pm. Order: (1) lowest-numbered actionable pending milestone, its tasks in depends_on order; (2) lowest-numbered open inbox note; (3) a blocked item whose unblock condition now verifiably holds (/pm unblock). Honor depends_on; scan all later items before concluding none are actionable. Announce the pick. Nothing actionable → Exit.
Read the item fully. Establish what is true on main with evidence: git log and grep the cited paths, check whether the chapter/file already exists in en/ and zh-CN/, run the DoD checks. Announce outcome + evidence:
| Outcome | When | Action |
|---|---|---|
| Work on it | still wanted, acceptance not yet true | one-line plan → step 3 |
| Close as already done | acceptance already holds (incl. both languages, indexes, checks) | /pm done; ship board move alone: chore(pm): close <target> — already satisfied by <SHA> |
| Block it | wanted but can't proceed: needs author/user decision, missing source material, unavailable tooling (e.g. no calibre for PDF build), unverifiable claim | /pm block <target> <reason> with Unblock:; ship alone: chore(pm): block <target> — … |
| Delete as invalid | conflicts with DO_NOT_DO.md, superseded/duplicate, or targets removed content | /pm drop <target> <reason>; ship alone: chore(pm): drop <target> — … |
User-routed/approved items you merely doubt are blocked, never deleted. Closing tasks (Reader surface, Simplify, Verification) are real work.
Do the writing/editing following AGENTS.md:
en/ and zh-CN/ change together; identical filenames; slug/id equal filename; only title/tags translated; never renumber.README.md, SUMMARY.md, zh-CN/README.md.https://tianpan.co/notes/<slug>; local images in images/ as ../images/<file>; diagrams via the mermaid skill.diff <(ls en) <(ls zh-CN), slug==filename), no broken relative links, make build when gitbook/calibre exist (otherwise say it was not run)./pm done <target> per finished item — never hand-edit board state.Invoke /ship for this item (content + .pm/ moves together, or board move alone). One board outcome per ship; never batch items. Never ship red — run checks as their own command and read the result before committing.
Re-scan immediately and pick again. Between items write one sentence: what shipped and what's next. Long queue / long session / several ships is not an exit.
Report item, blocker, and unblock; don't stop while independent work remains. Preserve partial work (stash or branch) — don't ship half-work. Block individual tasks in place when only some are stuck; block the milestone when all open tasks are. Skip dependents of blocked work automatically. Don't retry an unchanged blocker.
Only when: Done (nothing pending), Blocked (all remaining items blocked or depend on blocked work), or Hard stop (user interrupt/runtime limit/lost push access). Final report: shipped items with SHAs, closed-with-evidence, blocked-with-conditions-and-owners, deleted-with-reasons (and any proposed DO_NOT_DO.md entry), and for a hard stop the next actionable pick.
/pm owns .pm/. Doubt is a block, not a delete.<wN>. Report honestly: skipped checks, partial work, closes-by-triage.$ARGUMENTS
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
書籍や章、システム設計について、ファイルを変更せずに資料を読み、根拠を添えて質問に回答します。
システムや依存関係の説明から、構成要素と呼び出しの向きを整理したMermaid図を作り、構文を検証してMarkdownで提示します。
本の公開作業ボードを確認・整理し、作業の追加、完了、保留、取り下げなどを反映します。状態や未解決の課題も把握できます。
本のロードマップ案を読者への影響から整理し、マイルストーンやタスク候補に分解します。公開ボードへ反映するための提案文を作成します。
現在のブランチの変更を確認し、リモートの更新を取り込んでからコミットしてプッシュします。依頼に沿って変更を公開する作業を進めます。