Agent Skills › paperclipai/paperclip › paperclip-converting-plans-to-tasks

paperclip-converting-plans-to-tasks

GitHub

指导将授权计划转化为可执行任务，确定任务边界、所有者及依赖关系。仅在有明确所有权变更、并行输出或硬性依赖时才拆分任务，保持工作单元紧凑并验证关联。

skills/paperclip-converting-plans-to-tasks/SKILL.md paperclipai/paperclip

Trigger Scenarios

将计划分解为具体任务分配任务给不同所有者设置任务间的依赖关系

Install

npx skills add paperclipai/paperclip --skill paperclip-converting-plans-to-tasks -g -y

More Options

Use without installing

npx skills use paperclipai/paperclip@paperclip-converting-plans-to-tasks

指定 Agent (Claude Code)

npx skills add paperclipai/paperclip --skill paperclip-converting-plans-to-tasks -a claude-code -g -y

安装 repo 全部 skill

npx skills add paperclipai/paperclip --all -g -y

预览 repo 内 skill

npx skills add paperclipai/paperclip --list

SKILL.md

Frontmatter

{
    "name": "paperclip-converting-plans-to-tasks",
    "description": "Decide whether Paperclip work needs delegation, and connect justified tasks with owners and real dependencies. Use when turning an authorized plan into work."
}

Plans to tasks

Keep small, cohesive work on its current ordinary task with one end-to-end owner. A plan's steps, files, and phases do not each need a task.

Create a separate task only for a useful boundary: another owner or permission, independent parallel output, a real prerequisite, independent review, or substantial follow-up that needs its own lifecycle. Check the available agents before assigning. Give each delegate enough context and a clear deliverable to work independently.

Set real dependencies through blockedByIssueIds (or the native dependency tool). Parent/child nesting and prose do not delay execution. Independent work can start now; dependent work must wait for its prerequisite. Verify the saved relationships.

Reviewers publish findings on their own review task and complete it, including an adverse verdict. Make its description self-contained. Connect the verdict to the owner who must act on it; do not require writes to the parent.

Honor existing authorization and approval boundaries. Use Paperclip's planning mechanics when approval is required; decomposition does not create new approval gates.