/linear

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 (2): Important features with deadlines, major bugs
• Medium (3): Standard implementation tasks (default)
• Low (4): Nice-to-haves, minor improvements
• **Links**: Use the `links` parameter to attach URLs (not just markdown links in description)

Automatic Label Assignment

Automatically apply labels based on the ticket content:

• **hld**: For tickets about the `hld/` directory (the daemon)
• **wui**: For tickets about `humanlayer-wui/`
• **meta**: For tickets about `hlyr` commands, thoughts tool, or `thoughts/` directory

Note: meta is mutually exclusive with hld/wui. Tickets can have both hld and wui, but not meta with either.

Action-Specific Instructions

1. Creating Tickets from Thoughts

Steps to follow after receiving the request:

1. **Locate and read the thoughts document:**

• If given a path, read the document directly
• If given a topic/keyword, search thoughts/ directory using Grep to find relevant documents
• If multiple matches found, show list and ask user to select
• Create a TodoWrite list to track: Read document → Analyze content → Draft ticket → Get user input → Create ticket

2. **Analyze the document content:**

• Identify the core problem or feature being discussed
• Extract key implementation details or technical decisions
• Note any specific code files or areas mentioned
• Look for action items or next steps
• Identify what stage the idea is at (early ideation vs ready to implement)
• Take time to ultrathink about distilling the essence of this document into a clear problem statement and solution approach

3. **Check for related context (if mentioned in doc):**

• If the document references specific code files, read relevant sections
• If it mentions other thoughts documents, quickly check them
• Look for any existing Linear tickets mentioned

4. **Get Linear workspace context:**

• List teams: `mcp__linear__list_teams`
• If multiple teams, ask user to select one
• List projects for selected team: `mcp__linear__list_projects`

5. **Draft the ticket summary:** Present a draft to the user:

   ## Draft Linear Ticket

   **Title**: [Clear, action-oriented title]

   **Description**:
   [2-3 sentence summary of the problem/goal]

   ## Key Details
   - [Bullet points of important details from thoughts]
   - [Technical decisions or constraints]
   - [Any specific requirements]

   ## Implementation Notes (if applicable)
   [Any specific technical approach or steps outlined]

   ## References
   - Source: `thoughts/[path/to/document.md]` ([View on GitHub](converted GitHub URL))
   - Related code: [any file:line references]
   - Parent ticket: [if applicable]

   ---
   Based on the document, this seems to be at the stage of: [ideation/planning/ready to implement]

6. **Interactive refinement:** Ask the user:

• Does this summary capture the ticket accurately?
• Which project should this go in? [show list]
• What priority? (Default: Medium/3)