mcpField
P
paperclip-converting-plans-to-tasks

paperclip-converting-plans-to-tasks

github.com/paperclipaiAgent workflows108.3k218 installsUpdated today
Repository

About paperclip-converting-plans-to-tasks

A Paperclip skill for turning plans into tasks while keeping cohesive work with one owner and splitting only at useful boundaries. It covers delegation context, dependencies, review ownership, and approval constraints.

Key features

  1. 01Keep cohesive work on one task
  2. 02Split work at useful boundaries
  3. 03Check agents before assigning
  4. 04Set and verify dependencies
  5. 05Give delegates clear deliverables
  6. 06Respect approval boundaries

Use cases

  1. 01Break out work for an independent owner
  2. 02Sequence tasks with real prerequisites
  3. 03Assign an independent review with its own verdict

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/paperclipai/paperclip --skill paperclip-converting-plans-to-tasks

After installing, type/paperclip-converting-plans-to-tasksin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported