task-planning

Converts Paperclip issues into structured implementation plans with child tasks, blockers, and acceptance criteria.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill task-planning-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-planning
Source: https://github.com/adamtpang/summon.company/tree/main/packages/skills-catalog/catalog/bundled/paperclip-operations/task-planning
Command: npx skills add https://github.com/adamtpang/summon.company --skill task-planning-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or ambiguous issues in Paperclip are hard to delegate and execute directly. This Skill turns an issue or request into a structured implementation plan with an explicit child task graph, named owners, real blocker chains, and a defined acceptance bar, saved as the issue's plan document. ## Core Features & Use Cases - Structured Plan Generation: Produces plans with required sections including goal, context reviewed, constraints, approach, work breakdown, acceptance, risks, and deferrals. - Delegation-Ready Work Breakdown: Splits work into child issues with one specialty, one acceptance verdict, and explicit blocked-by relationships per child. - Paperclip API Integration: Writes the plan via PUT /api/issues/{issueId}/documents/plan, posts a summary comment, and creates a request_confirmation interaction when approval is required. - Use Case: A manager inherits an issue too large to ship in one heartbeat. The Skill breaks it into ordered child issues with owners and blockers, files the plan document, and requests confirmation before any implementation subtasks are created. ## Quick Start Ask the agent to plan the current Paperclip issue and save the breakdown as the issue's plan document for review.

Frequently Asked Questions about task-planning

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

FAQPage Schema
How do I break down a large issue into child tasks in Paperclip?

Use the task-planning workflow to produce a work breakdown where each child issue has one specialty, one acceptance verdict, an imperative title, and explicit blocked-by relationships. The plan is saved as the issue's `plan` document via the Paperclip API.

How do I write an implementation plan for a Paperclip issue?

Follow the required plan structure: goal, context reviewed, constraints and non-goals, approach, work breakdown, acceptance, risks, and deferrals. File it with `PUT /api/issues/{issueId}/documents/plan` and post a summary comment linking the plan.

When should I not create a task plan for an issue?

Skip planning when the issue is a single small change shippable in one heartbeat, when it is a forensic diagnosis task, or when a current plan document already exists and the change is minor. In those cases ship directly, diagnose first, or update the existing plan.

How does plan approval work before creating subtasks?

When approval is required, create an issue interaction of kind `request_confirmation` bound to the latest plan revision with `continuationPolicy: wake_assignee`, then set the issue to `in_review`. Implementation subtasks are only created after the plan is accepted.

Why do child issues fail at delegation time?

Children fail when their descriptions say "see parent", combine multiple specialties, lack acceptance criteria, or hide blocker chains in prose. Each child must be checkout-able by its owner from its title and description alone.