What problem does it solve? Picking up a ticket and jumping straight into code produces implementations that miss the intent, duplicate existing features, or bake in unapproved decisions. This Skill turns a Linear issue into an agreed, test-backed approach before any file is edited, then builds and verifies it against the ticket. ## Core Features & Use Cases - Approach-first workflow: Reads the full issue (comments, blockers, linked docs), maps the codebase seam and prior art, then interviews the human one question at a time until every decision has an explicit answer. - Acceptance criteria as tests: Restates each criterion as a named unit, integration, or E2E test, forming the contract the final verification checks against. - Ticket-native record keeping: Posts the approved approach as an issue comment, claims and branches the ticket, ships a feature doc with the diff, and closes out with PR, issue comment, and deferred-work tickets. - Use Case: Given "implement PROJ-142", the agent reads the issue and its blockers, proposes reusing an existing seam, grills you on data shape and rollout, posts the plan to Linear, then builds it with a failing test first and verifies each criterion before opening the PR. ## Quick Start Ask the agent to pick up and implement Linear issue PROJ-142 using this skill, answering its approach questions one at a time.
