What problem does it solve? When work is dispatched to an agent or teammate via a Linear ticket, context is often scattered across prompts, chats, and documents, leading to duplicated work, wrong assumptions, and lost feedback. This Skill establishes a single disciplined reading order so the ticket itself carries everything needed to start work or hand it back. ## Core Features & Use Cases - Dispatch rule: A prompt is just a pointer — the ticket id plus this skill — so no context is pasted into kickoff prompts that would drift from the ticket. - Four-beat reading order: Read the ticket, its parents and blockers, the project context doc, and optionally the vault for depth, never as a dependency. - Status semantics: Enforces that Review means the PR is open and Done means merged to main, with a rule that you never close your own work. - Hand-back flow: Rejected work gets reviewer comments quoted on the ticket, acceptance criteria rewritten, labels like defect:discovery or defect:build applied, and the ticket moved back to a doing status. - Use Case: An agent receives "work LIAB-693" — it reads the ticket and its epic, verifies blockers are actually finished, checks the context doc, comments that it has taken the ticket, and holds the finished PR at Review for a lead to merge. ## Quick Start Tell the agent to pick up a Linear ticket by saying "work LIAB-693" and it will follow the pickup reading order to start the work.
