| name | kata-linear |
| description | Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers include, start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion. |
Linear Ticket Lifecycle
This skill wraps the general /linear skill with structured start/next/end workflows.
Always invoke the /linear skill for the actual MCP calls when using this skill.
Determining the Mode
Parse the user's request to determine which workflow to run:
| User says | Mode |
|---|
| "start KAT-N", "pick up KAT-N", "implement KAT-N", "work on KAT-N" | Start |
| "finish KAT-N", "complete KAT-N", "done with KAT-N", "close KAT-N" | Complete |
| "what's next", "what should I work on", "next ticket", "next issue" | Next |
If ambiguous, ask.
Identifying the Project
- Check the current working directory's AGENTS.md for a Linear project reference.
- If not found, call
list_projects and ask the user which project to use.
- Cache the project name for the remainder of the session and update AGENTS.md for future reference.
Mode: Next
Find the next actionable issue.
- Query
list_issues for the project with state Todo.
- If results exist, present them. The first
Todo issue is the recommended next pick.
- If no issues, resolve from blocking relations:
a. Query for the project with state .
b. For each Backlog issue, call with .
c. Find issues whose entries are all (or have no blockers).
