Menú
Download an implementation plan from a Linear ticket attachment into the current plan file. Use when picking up work from another machine or conversation.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
| name | download-plan |
| description | Download an implementation plan from a Linear ticket attachment into the current plan file. Use when picking up work from another machine or conversation. |
Download an implementation plan from a Linear ticket and write it to the current plan file.
Linear tickets are identified by a code like TEAM-1234.
Determine the Linear ticket ID by trying these in order:
/download-plan TEAM-1234)**Ticket**: line (e.g. **Ticket**: TEAM-1234)user/team-1234-... → TEAM-1234)Fetch the issue using mcp__linear-server__get_issue to list its attachments.
Find the attachment with title "Implementation Plan". If not found, inform the user that no plan attachment exists on the ticket.
Download the attachment using mcp__linear-server__get_attachment with the attachment ID. This returns the markdown content directly.
Write the content to the current plan file (from the plan mode system message). If not in plan mode, write to ~/.claude/plans/ using the current plan filename.
Confirm to the user: "Downloaded plan from {TICKET_ID}" and display the plan content.