Agent skill · operations · paperclipai
paperclip-converting-plans-to-tasks
Convert Paperclip plans into executable issue graphs. Use when asked to plan, scope, or break down Paperclip company work into assigned tasks with specialty fit, dependencies, blockers, and parallelization.
Why this skill is useful
Provides a structured method for converting plans into executable tasks with specific dependencies and roles, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Paperclip — Converting Plans to Tasks 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. 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. Minimize the issue graph. Use as few tasks as possible while still completing and verifying the job. Prefer one end-to-end task with one owner over separate tasks for each step, file, component, or phase. Keep those structural details as checklists or acceptance criteria inside the owning task unless a real execution boundary requires another issue. Split only for a qualifying boundary. Create a separate subtask only when at least one of these applies: A different specialist, owner, permission boundary, or external actor must own the work. A self-contained deliverable can usefully run in parallel with other work. A hard dependency or handoff needs its own blockedByIssueIds lifecycle. A review, QA pass, or governed approval gate has an independent owner. Substantial follow-up work needs independent tracking or retry because it cannot safely be completed and verified in the parent. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/paperclip-converting-plans-to-tasks