A task stack records a code dependency: a child task needs an unmerged parent's work. This is more than a link between two tasks. The child branch starts from the parent's task branch so its review can focus on the child's own change; the stack merges from parent to child.
When to stack
Create a child with rp task create --title <title> --stack-on <parent-number> when implementing it requires code still on the parent's unmerged branch. Independent changes should not be put in the same chain merely because they share a topic. Separate children can be stacked on the same parent without making them depend on one another.
Each child has its own ownership turn, submission, review, and approval gates. Merging the parent reconciles its open descendants onto the parent's merge target without merging the child into the parent. A changed parent may require an explicit restack; inspect rp task stack <number> and use rp task restack <number> when it says a restack is needed. Conflicts preserve work and require deliberate recovery; do not treat an old approval as permission to merge a different patch.
To change the base of an existing task, use rp task stack <number> --on <parent> to choose a parent, rp task stack <number> --base to unstack, or rp task retarget <number> --base <branch> on an unstacked task. API clients can use the stack endpoint. These moves apply directly after preflight. Conflicts, stale heads, or rewrites of another owner's pushed branch leave the stack unchanged. Follow the result to refresh rewritten checkouts. Moving a task does not change the base branch or bypass review before merging.
An unmerged parent cannot be closed while open children remain: resolve, move, or unstack them first. This prevents an unreviewed parent change from slipping into the base through a child. Task turns and review explains what a submitted head and readiness mean for each task.
Links express a different relationship
Related links are informational. A directed blocks link stops the blocked task from merging while its blocker remains open, but work and review can continue. Neither kind changes Git ancestry, branch base, or restacking. If B needs A's code, use a stack; if B simply cannot merge until A is resolved, use a blocking link. The two relationships can coexist when both facts are true.
See the first-task guide for the unstacked task workflow. A full stack-recovery guide and command reference will follow; do not guess a conflict-resolution command from this overview.