Task Planning Produce implementation plans that the Paperclip executor can actually run: explicit child issues, real blockers, named owners, and a defined acceptance bar. Avoid plans that read well but cannot be split into work. When to use - An issue asks you to "plan", "scope", "break down", "design the rollout", "propose the work", or similar. - A user wants a written plan before approving implementation. - A manager needs to delegate non-trivial work and the shape of the work is not obvious yet. - You inherited an issue too large to deliver in one heartbeat and need to split it. When not…