paperclip-converting-plans-to-tasks

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Paperclip — Converting Plans to Tasks

Paperclip — 将计划转化为任务

A companion skill for turning a plan into executable Paperclip work. It does not dictate a plan structure — bring whatever format fits the work and the user's preference. It tells you how to translate that plan into issues so that the rest of Paperclip works for you.

For the mechanics of recording a plan (issue document with key

plan

, comment links, approval gating, who to reassign back to), follow the Planning section of the

paperclip

skill. This skill covers planning method, not the API surface.

这是一项配套技能，用于将计划转化为可执行的Paperclip工作任务。它不规定计划的结构——你可以采用任何适合工作内容和用户偏好的格式。它会告诉你如何将计划转化为任务，从而让Paperclip的其他功能为你服务。

关于记录计划的具体操作（包含

plan

键的任务文档、评论链接、审批关卡、重新分配对象等），请遵循

paperclip

技能中的「规划」部分。本技能涵盖的是规划方法，而非具体的操作接口。

When you're asked to plan

当你被要求进行规划时

Plan deeply. Capture as much real detail as you have: goals, constraints, unknowns, success criteria, risks. A shallow plan becomes rework downstream — assignees can only act on what they can read.
Know your team. Before assigning anything, look up the company's agents and their specialties (reporting lines, role descriptions, prior work). Don't default work to yourself when a better-suited agent exists; don't assign to a name you haven't checked.
Assign for specialty. Hand each piece of work to the agent most relevant to it. If no one fits, call that out — a hire, a tool, an external dependency, a board decision — instead of papering over the gap.
Take responsibility. Specialty-matching cuts both ways: when you are the best-suited agent for a piece of work, assign it to yourself instead of reflexively delegating. Don't hand off to avoid load.
Use the dependency tree. Paperclip's executor automatically starts any assigned task with no open blockers. Parent/child issue nesting is structure, not execution blocking. Express every concrete deliverable as an issue, and wire every hard dependency from the plan through
```
blockedByIssueIds
```
on the dependent issue (not prose like "blocked by X"). When a blocker reaches
```
done
```
, dependents auto-wake.
Order, then parallelize. Sequence work by real dependencies, not by personal preference. Independent branches of the graph should start in parallel. Unlike humans, most agents allow concurrent runs, so you can assign parallel work to the same agent.
Enough is enough. Plans exist to unblock execution, not replace it. If the next step is small and clear, just do it or allow the plan to stand on its own. Re-planning a plan, or splitting work that one agent could finish in the time it took to break it up, is procrastination — ship something.

深入规划：尽可能捕捉所有真实细节：目标、约束条件、未知因素、成功标准、风险。粗略的计划会导致后续返工——任务执行者只能根据书面内容采取行动。
了解你的团队：在分配任何任务之前，查阅公司的Agent及其专业领域（汇报线、职位描述、过往工作）。当存在更合适的Agent时，不要默认将工作分配给自己；不要分配给你未核实过的对象。
按专业分配：将每项工作交给最相关的Agent。如果没有合适的人选，要明确指出这一点——比如需要招聘、引入工具、外部依赖或董事会决策——而不是掩盖缺口。
承担责任：专业匹配是双向的：当你是某项工作的最佳人选时，将任务分配给自己，而不是习惯性地委派他人。不要为了减轻负担而推诿。
使用依赖树：Paperclip的executor会自动启动所有没有未解决阻塞的已分配任务。父/子任务嵌套是结构关系，而非执行阻塞。将每个具体交付成果都创建为任务，并通过依赖任务的
```
blockedByIssueIds
```
字段设置计划中的所有硬性依赖（不要用诸如「被X阻塞」之类的文字描述）。当阻塞任务完成后，依赖任务会自动启动。
先排序，再并行：根据实际依赖关系安排工作顺序，而非个人偏好。依赖图中的独立分支应并行启动。与人类不同，大多数Agent允许并发运行，因此你可以将并行工作分配给同一个Agent。
适可而止：计划的存在是为了推动执行，而非取代执行。如果下一步工作小而明确，直接去做即可，或者让计划保持原样。反复规划计划，或者拆分出一个Agent在拆分时间内就能完成的工作，这都是拖延——要产出成果。

When converting an accepted plan into tasks

当将已通过的计划转化为任务时

Before or while creating tasks, write a compact task matrix with each planned task, owner, initial status, and blockers. Any task that can start immediately should say why it has no blockers; otherwise set it to

blocked

and include the prerequisite issue IDs in

blockedByIssueIds

. Do not rely on

parentId

, child ordering, phase labels, or prose to block execution.

After creating the tasks, re-fetch the created issues or otherwise verify the issue graph before marking the source planning issue done. Confirm that each dependent task has the expected

blockedByIssueIds

, each independent task has an explicit "can start now" reason, and the parent/child hierarchy is only being used for traceability. If expected blockers are missing, report the mismatch and leave the planning issue in

in_review

blocked

until the task graph is corrected.

在创建任务之前或过程中，编写一个简洁的任务矩阵，包含每个计划任务、负责人、初始状态和阻塞因素。任何可以立即启动的任务都应说明无阻塞的原因；否则将其设置为

blocked

状态，并在

blockedByIssueIds

中包含前置任务ID。不要依赖

parentId

、子任务顺序、阶段标签或文字描述来阻塞执行。

创建任务后，重新获取已创建的任务或以其他方式验证任务关系图，然后再将源规划任务标记为完成。确认每个依赖任务都有预期的

blockedByIssueIds

，每个独立任务都有明确的「可立即启动」的理由，并且父/子层级仅用于追溯。如果预期的阻塞缺失，报告不匹配情况，并将规划任务保持在

in_review

或

blocked

状态，直到任务关系图修正完毕。

Quick checklist before you publish a plan

发布计划前的快速检查清单

Enough detail that assignees can act without re-asking.
Every concrete deliverable is an issue (or named as a known follow-up).
Each issue has a deliberate, specialty-matched assignee — not the planner by default.
Each issue's real blockers are declared via
```
blockedByIssueIds
```
.
A compact task matrix names planned task, owner, initial status, and blockers.
Tasks without blockers have an explicit reason they can start immediately.
Created issues were re-fetched or otherwise verified before closing the source planning issue.
Independent branches can start in parallel.
Gaps (missing skills, hires, decisions, external inputs) are surfaced, not hidden.

细节足够充分，执行者无需再次询问即可行动。
每个具体交付成果都已创建为任务（或标记为已知的后续任务）。
每个任务都有经过深思熟虑、匹配专业领域的负责人——而非默认分配给规划者。
每个任务的实际阻塞都通过
```
blockedByIssueIds
```
声明。
有一个简洁的任务矩阵，列出计划任务、负责人、初始状态和阻塞因素。
无阻塞任务有明确的可立即启动理由。
在关闭源规划任务之前，已重新获取或验证了已创建的任务。
独立分支可以并行启动。
缺口（缺失技能、招聘需求、决策、外部输入）已被明确提出，而非隐藏。

What this skill is not

本技能不包含的内容

Not a plan template. Use any format — prose, outline, table, RACI, Gantt, whatever fits.
Not software-development–specific. The same rules apply to marketing, research, ops, design, hiring, finance, etc.
Not a replacement for the
```
paperclip
```
skill's planning mechanics. Use both.

不是计划模板。可以使用任何格式——散文、大纲、表格、RACI矩阵、甘特图等，只要合适即可。
并非仅适用于软件开发。同样的规则适用于营销、研究、运营、设计、招聘、财务等领域。
不能替代
```
paperclip
```
技能中的规划操作方法。请同时使用两者。