paperclip-converting-plans-to-tasks

1# Plans to tasks
2 
3Keep small, cohesive work on its current ordinary task with one end-to-end owner.
4A plan's steps, files, and phases do not each need a task.
5 
6Create a separate task only for a useful boundary: another owner or permission,
7independent parallel output, a real prerequisite, independent review, or substantial
8follow-up that needs its own lifecycle. Check the available agents before assigning.
9Give each delegate enough context and a clear deliverable to work independently.
10People read these descriptions: reference other tasks and documents with identifier links (for example `[BRA-2](/BRA/issues/BRA-2#document-plan)`), never raw UUIDs.
11 
12Set real dependencies through `blockedByIssueIds` (or the native dependency tool).
13Parent/child nesting and prose do not delay execution. Independent work can start
14now; dependent work must wait for its prerequisite. Verify the saved relationships.
15 
16Reviewers publish findings on their own review task and complete it, including an
17adverse verdict. Make its description self-contained. Connect the verdict to the
18owner who must act on it; do not require writes to the parent.
19 
20Honor existing authorization and approval boundaries. Use Paperclip's planning
21mechanics when approval is required; decomposition does not create new approval gates.