Skip to main content
skill CX Codex

paperclip-converting-plans-to-tasks — Claude Code skill

The paperclip-converting-plans-to-tasks skill turns an approved plan into owned Paperclip tasks with real dependencies. Use it when work needs deliberate delegation.

MIT 264 installs ★ 115,688 updated 2026-11-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add paperclipai/paperclip --skill paperclip-converting-plans-to-tasks -a claude-code
Open on GitHub

What paperclip-converting-plans-to-tasks does

The skill helps keep small, cohesive work in one ordinary task with one end-to-end owner. It creates separate tasks only when there is a meaningful boundary, such as a different owner or permission, parallel output, a true prerequisite, independent review, or substantial follow-up. Available agents should be checked before assigning work, and each delegate needs enough context to deliver independently.

Dependencies use blockedByIssueIds or the native dependency tool. Parent/child nesting and prose do not hold execution back, so the saved links need verification. A reviewer gets a self-contained review task, posts the findings there, completes it even when the verdict is adverse, and connects the result to the owner responsible for action.

The skill follows existing authorization and approval boundaries. Breaking a plan into tasks does not create another approval gate.

What it helps with

  • split an approved plan at useful task boundaries
  • assign owners after checking available agents
  • connect prerequisites with real dependencies
  • route review findings to the owner who must act

Example prompts for the agent

  • Turn this approved Paperclip plan into tasks and keep small cohesive work with one end-to-end owner.
  • Create separate tasks only for another owner, parallel output, a real prerequisite, independent review, or substantial follow-up.
  • Make the review task self-contained, connect its verdict to the action owner, and verify blockedByIssueIds.

How to install paperclip-converting-plans-to-tasks

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/paperclip-converting-plans-to-tasks/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/paperclip-converting-plans-to-tasks/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about paperclip-converting-plans-to-tasks

How do I install paperclip-converting-plans-to-tasks in Claude Code?

Run npx skills add paperclipai/paperclip --skill paperclip-converting-plans-to-tasks -a claude-code, then check ~/.claude/skills/paperclip-converting-plans-to-tasks/SKILL.md.

What does paperclip-converting-plans-to-tasks do?

It converts an authorized plan into Paperclip tasks, helps decide where delegation is justified, assigns owners, and connects real prerequisites. It also defines how review tasks should pass findings to the responsible owner.

How are task dependencies handled?

The skill uses blockedByIssueIds or the native dependency tool. Independent work can start immediately, while dependent work waits for its prerequisite, and the saved relationships should be verified.

Source text

SKILL.md · MIT
---
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.
People read these descriptions: reference other tasks and documents with identifier links (for example `[BRA-2](/BRA/issues/BRA-2#document-plan)`), never raw UUIDs.

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.

© paperclipai · MIT · paperclipai/paperclip

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set7

Project sponsors

Companies that keep this analytics open