ticket
Installation
SKILL.md
1. Find the issue
Use the mcp__linear-server__* tools.
- Link or ID (
ENG-123):get_issue. - Branch name (
nathan/eng-123-…): take the ID from it, thenget_issue. - Roadmap screenshot or a title: read the title, then
list_issueswith its key words. One clear match: use it. Several: show them and ask. None: ask whether to create one.
Read the description and list_comments; comments often carry the decisions.
Split what you read in two:
- The problem: what is broken or missing, and for whom. This is the work.
- The proposal: any "Proposed solution", "Proposed fix", "Ideal UX" or similar section, and any fix the description prescribes. Proposals are often written by non-engineers or drafted with AI, so a proposal is a hypothesis to test against the code and data, not a spec. Find the root cause yourself, then keep, change or replace the proposal according to which solves the problem best.
Done when you have the issue ID, its gitBranchName, and a numbered list of the requirements: the problem's outcomes, stated without the proposal's mechanism.