Turn an authorized plan into Paperclip work by deciding which tasks need separate owners, defining clear deliverables, and recording real dependencies so independent work can start and dependent work waits.
Decide whether Paperclip work needs delegation, and connect justified tasks with owners and real dependencies. Use when turning an authorized plan into work.
Run score Not tested
See how to installTurns an approved plan into Paperclip work by deciding where delegation is needed and defining owners, deliverables, and dependencies. Small, cohesive work stays with one owner from start to finish. Separate tasks are used when work needs another owner or permission, can produce an independent parallel result, has a prerequisite, or requires an independent review.
Use it when deciding whether each step or file in a plan needs its own task, or when assigning work to several agents. It checks which agents are available before assignment and gives each owner enough context and a clear deliverable to proceed independently. It also connects review findings to the owner responsible for addressing them.
Requires work to be managed in Paperclip. Dependencies are set with blockedByIssueIds or equivalent tools, and the saved relationships are checked. Parent-child relationships and descriptions alone do not prevent execution. Existing authorization boundaries remain in effect; splitting work into tasks does not introduce new approval stages.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.
Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.
Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.
Read email linked to assigned Paperclip tasks, send new messages or replies through an assigned AgentMail inbox, and check delivery outcomes. Follow task permissions and preserve retry identifiers to avoid duplicate sends.
Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.
Create an AI agent company or team package from an idea or an existing repository. Define roles, reporting lines, skills, and work handoffs, then generate structured files that follow the Agent Companies specification.