paperclip-converting-plans-to-tasks

Convert Paperclip plans into executable issue graphs with dependencies and assignees.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill paperclip-converting-plans-to-tasks-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-converting-plans-to-tasks
Source: https://github.com/adamtpang/summon.company/tree/main/skills/paperclip-converting-plans-to-tasks
Command: npx skills add https://github.com/adamtpang/summon.company --skill paperclip-converting-plans-to-tasks-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an accepted plan into actionable work often fails because tasks lack clear owners, real dependency wiring, or enough detail for assignees to act. This Skill guides the conversion of Paperclip plans into executable issue graphs so work starts correctly and blockers resolve automatically. ## Core Features & Use Cases - Specialty-matched assignment: Look up company agents and their specialties before assigning, and surface gaps when no agent fits instead of hiding them. - Dependency wiring: Express every hard dependency through blockedByIssueIds so Paperclip's executor auto-starts unblocked tasks and wakes dependents when blockers complete. - Task matrix and verification: Produce a compact matrix of task, owner, status, and blockers, then re-fetch created issues to verify the graph before closing the planning issue. - Use Case: After a product launch plan is approved, use this Skill to break it into issues for engineering, design, and marketing agents, wire the dependencies, and confirm parallel branches can start immediately. ## Quick Start Use the paperclip-converting-plans-to-tasks skill to turn this approved plan into assigned Paperclip issues with correct blockers and parallelizable branches.

Frequently Asked Questions about paperclip-converting-plans-to-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a plan into tasks in Paperclip?

Create one issue per concrete deliverable, assign each to the best-suited agent, and wire hard dependencies through blockedByIssueIds on the dependent issue. Then re-fetch the created issues to verify the graph before marking the planning issue done.

How do task dependencies and blockers work in Paperclip?

Paperclip's executor automatically starts any assigned task with no open blockers, and dependents auto-wake when a blocker reaches done. Dependencies must be declared via blockedByIssueIds, not through parentId, child ordering, or prose.

Does this skill dictate a specific plan format or template?

No, it accepts any plan format including prose, outlines, tables, RACI, or Gantt charts. It only governs how the plan translates into issues, while the separate paperclip skill covers the API mechanics of recording plans.

When should I not break a plan into more tasks?

Stop when the next step is small and clear enough to just do. Splitting work that one agent could finish faster than the breakdown takes, or re-planning an existing plan, is procrastination rather than useful structure.

What should I do when no agent fits a planned task?

Call out the gap explicitly instead of assigning to an unfit agent or defaulting to yourself. The gap may require a hire, a new tool, an external dependency, or a board decision, and hiding it causes downstream failure.