Menu
Upload the current plan file as an attachment to a Linear ticket. Use when the user wants to persist a plan to Linear for cross-machine workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Let's go — start work on a Linear issue, resolved from the current branch or a supplied ticket arg (e.g. BEMLO-1234). Use when the user wants to begin work on a ticket.
Read comments and full comment threads on the current branch's GitHub pull request, then plan solutions to address the feedback. Use when the user wants to respond to PR review feedback.
Download an implementation plan from a Linear ticket attachment into the current plan file. Use when picking up work from another machine or conversation.
| name | upload-plan |
| description | Upload the current plan file as an attachment to a Linear ticket. Use when the user wants to persist a plan to Linear for cross-machine workflows. |
Upload the current conversation's plan file to a Linear ticket as a markdown attachment.
Linear tickets are identified by a code like TEAM-1234.
Determine the Linear ticket ID by trying these in order:
/upload-plan TEAM-1234)**Ticket**: line (e.g. **Ticket**: TEAM-1234)user/team-1234-... → TEAM-1234)Read the current plan file from the path specified in the plan mode system message. If not in plan mode, check for a recently written plan in ~/.claude/plans/.
Base64-encode the plan file content using the Bash tool.
Upload using mcp__linear-server__create_attachment:
issue: the ticket IDtitle: "Implementation Plan"filename: "implementation-plan.md"contentType: "text/markdown"base64Content: the encoded contentConfirm to the user: "Uploaded plan to {TICKET_ID}."