1 min lesson
Linear MCP, issue ENG-412
Describe what "Start with this check: An agent can implement from the issue id without you re-pasting the requirements" changes in practice.
Step 1 of 3
The job: you can drive an agent from an issue id and trigger work from a board column. Start with this check: An agent can implement from the issue id without you re-pasting the requirements. Keep it small enough to check the result yourself instead of taking the summary on trust.
Learn more
Full explanation
Linear MCP, issue ENG-412
Tickets as briefs — drive one agent from a Linear issue to a reviewable PR
Linear MCP, issue ENG-412
SayENG-412 reads "add rate limiting." That is too thin for an agent; it says nothing about what done looks like. I rewrite it as the what, not the how.
DoEdit the ticket to state the outcome, the constraints and the acceptance check: limit the public API to 100 requests per minute per key, return 429 with a Retry-After header when exceeded, leave authenticated routes unaffected, and call it done when the new 429-path integration test passes.
DoPoint an agent at the issue id over the Linear MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition.: it pulls ENG-412 itself and builds from the brief, so you never re-paste the requirements into the prompt.
SeeThe agent works from the ticket's outcome and acceptance check, not from a step-by-step recipe you dictated.
SayThe MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. connection is scoped to read-plus-comment. The agent can read the ticket and post progress, nothing more; it never gets merge rights.
DoWire the board-column move as the trigger, so dragging a ticket into that column starts one agent per item instead of you kicking each off by hand.
SeeA single drag replaces the manual triage of copying the ticket, opening an agent and pasting the context.
SeeThe proof point: the agent implemented straight from the issue id, the ticket described outcomes rather than implementation steps, and the work came back as a reviewable PR - not an automation that merged itself.
Learn more
Optional practice
Practice: Linear MCP, issue ENG-412
QYou've applied it. What actually proves the work is done, not just a plausible answer?