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

技能中的「规划」部分。本技能涵盖的是规划方法，而非API层面的操作。

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. Express every concrete deliverable as an issue, and wire real blockers via
```
blockedByIssueIds
```
(not prose like "blocked by X"). When
```
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的执行者会自动启动所有没有未解决障碍的已分配任务。将每个具体交付成果都转化为任务，并通过
```
blockedByIssueIds
```
明确真实的障碍（而不是用“被X阻碍”这样的文字描述）。当任务完成后，依赖它的任务会自动启动。
先排序，再并行：根据实际依赖关系安排工作顺序，而非个人偏好。依赖图中的独立分支应并行启动。与人类不同，大多数Agent支持并发运行，因此你可以将并行工作分配给同一个Agent。
适可而止：计划的存在是为了推进执行，而非取代执行。如果下一步工作小而明确，直接去做，或者让计划保持原样。重新规划一份计划，或者拆分一个Agent在拆分工作的时间内就能完成的任务，都是拖延——要产出成果。

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
```
.
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
```
技能中的规划操作。请同时使用两者。