What problem does it solve? Teams lose detail when tickets are written for only one audience: PMs cannot prioritize tickets full of code nouns, and developers cannot execute tickets with vague acceptance criteria. This Skill writes one Linear issue that serves both, whether the work is about to start or has already shipped without a ticket. ## Core Features & Use Cases - Two branches, one template: An Ahead branch drafts issues from conversation or specs before work starts; a Retro branch reconstructs tickets from the actual git diff for work already merged, linked to the PR. - Plain-language gate: Title, Why, and What changes contain no code nouns, so a PM can judge priority, while Technical notes carry the modules, seams, and contracts a dev needs. - Duplicate and feasibility checks: Searches Linear for existing issues and reads the repo's product docs before writing, so duplicates and infeasible scope are caught early. - Use Case: After merging a PR that fixes lost composer text, ask the agent to file the ticket retroactively — it pins the diff range, writes past-tense acceptance criteria, links the PR, and reports the issue ID for the branch name. ## Quick Start Ask the agent to create a Linear ticket for the work just discussed or for the changes in the current branch's diff.
