Linear - Ticket Management

---

description: Manage Linear tickets - create, update, comment, and follow workflow patterns

Linear - Ticket Management

You are tasked with managing Linear tickets, including creating tickets from thoughts documents, updating existing tickets, and following the team's specific workflow patterns.

Initial Setup

First, verify that Linear MCP tools are available by checking if any `mcp__linear__` tools exist. If not, respond:

I need access to Linear tools to help with ticket management. Please run the `/mcp` command to enable the Linear MCP server, then try again.

If tools are available, respond based on the user's request:

For general requests:

I can help you with Linear tickets. What would you like to do?
1. Create a new ticket from a thoughts document
2. Add a comment to a ticket (I'll use our conversation context)
3. Search for tickets
4. Update ticket status or details

For specific create requests:

I'll help you create a Linear ticket from your thoughts document. Please provide:
1. The path to the thoughts document (or topic to search for)
2. Any specific focus or angle for the ticket (optional)

Then wait for the user's input.

Team Workflow & Status Progression

The team follows a specific workflow to ensure alignment before code implementation:

1. Triage → All new tickets start here for initial review
2. Spec Needed → More detail is needed - problem to solve and solution outline necessary
3. Research Needed → Ticket requires investigation before plan can be written
4. Research in Progress → Active research/investigation underway
5. Research in Review → Research findings under review (optional step)
6. Ready for Plan → Research complete, ticket needs an implementation plan
7. Plan in Progress → Actively writing the implementation plan
8. Plan in Review → Plan is written and under discussion
9. Ready for Dev → Plan approved, ready for implementation
10. In Dev → Active development
11. Code Review → PR submitted
12. Done → Completed

**Key principle**: Review and alignment happen at the plan stage (not PR stage) to move faster and avoid rework.

Important Conventions

URL Mapping for Thoughts Documents

When referencing thoughts documents, always provide GitHub links using the `links` parameter:

• thoughts/shared/... → https://github.com/humanlayer/thoughts/blob/main/repos/humanlayer/shared/...
• thoughts/allison/... → https://github.com/humanlayer/thoughts/blob/main/repos/humanlayer/allison/...
• thoughts/global/... → https://github.com/humanlayer/thoughts/blob/main/global/...

Default Values

• Status: Always create new tickets in "Triage" status
• Project: For new tickets, default to "M U L T I C L A U D E" (ID: f11c8d63-9120-4393-bfae-553da0b04fd8) unless told otherwise
• Priority: Default to Medium (3) for most tasks, use best judgment or ask user
  • Urgent (1): Critical blockers, security issues
  • High (