Linear Create Issue
When to Use
- User asks to "create an issue" or "file a bug"
- User asks to "add a ticket" or "track this"
- User describes a problem, task, or feature to be tracked
- User wants to create issues with sub-tasks
Tools
Discovery & Context
- LINEAR_CUSTOM_GET_WORKSPACE_CONTEXT — Get teams, projects, labels, states
- LINEAR_CUSTOM_RESOLVE_CONTEXT — Map fuzzy names → IDs (team, user, labels, project, state)
- LINEAR_CUSTOM_SEARCH_ISSUES — Search issues by keyword
- LINEAR_CUSTOM_GET_ISSUE_FULL_CONTEXT — Get full issue details
- LINEAR_CUSTOM_GET_ACTIVE_SPRINT — Get current sprint/cycle info
- LINEAR_CUSTOM_GET_MY_TASKS — Get authenticated user's assigned issues
Creation
- LINEAR_CUSTOM_CREATE_ISSUE — Create issue with all fields
- Required: team_id, title
- Optional: description, assignee_id, priority (0-4), state_id, label_ids, project_id, cycle_id, due_date, estimate, parent_id
- Sub-issues: sub_issues array [{title, description, assignee_id, priority}]
Workflow
Step 1: Search for Duplicates (MANDATORY)
Before creating anything, search for existing issues:
LINEAR_CUSTOM_SEARCH_ISSUES(query="<keywords from user request>")
If similar issues exist:
- Show them to the user: "I found these existing issues that look similar..."
- Ask if they want to proceed or update an existing one
- Only continue to creation after user confirms no duplicate
Step 2: Learn Team Patterns
Understand how the team structures issues:
Get workspace context:
LINEAR_CUSTOM_GET_WORKSPACE_CONTEXT()
This reveals team names, available states, labels, and projects.
Read recent team issues (2-3):
LINEAR_CUSTOM_SEARCH_ISSUES(query="recent")
Study the results to learn:
- Title format (e.g., "[Component] Description" vs plain descriptions)
- Description structure (bullet points? acceptance criteria? steps to reproduce?)
- Common labels used
- Priority conventions
Match the team's style when writing the title and description.
Step 3: Evaluate Sub-Issue Potential
If the user's request is broad or multi-faceted:
- Break it down: Suggest logical sub-issues
- Example: "Implement auth" → "Design login flow", "Implement OAuth", "Add MFA", "Write tests"
- Ask the user: "This looks like it could be broken into sub-tasks. Want me to create sub-issues?"
- Keep it practical: Only suggest 2-5 sub-issues; too many is unhelpful
If the request is specific and focused, skip sub-issues entirely.
Step 4: Resolve All Entities
Use RESOLVE_CONTEXT to convert names to IDs:
LINEAR_CUSTOM_RESOLVE_CONTEXT(
team_name="engineering",
user_name="john",
label_names=["bug", "critical"],
project_name="Q1 Sprint",
state_name="backlog"
)
This returns: team_id, user_id, label_ids, project_id, state_id
For cycle_id (adding to current sprint):
LINEAR_CUSTOM_GET_ACTIVE_SPRINT()
Step 5: Create the Issue
LINEAR_CUSTOM_CREATE_ISSUE(
team_id=resolved_team_id,
title="Formatted like team's convention",
description="Structured like team's existing issues",
assignee_id=resolved_user_id,
priority=2,
label_ids=resolved_label_ids,
project_id=resolved_project_id,
state_id=resolved_state_id,
cycle_id=sprint_cycle_id,
sub_issues=[
{"title": "Sub-task 1", "priority": 2},
{"title": "Sub-task 2", "priority": 2}
]
)
Step 6: Confirm Results
Report back clearly:
- Issue identifier (e.g., "ENG-456")
- URL to the issue
- What was set (assignee, labels, project, sprint)
- Sub-issues created (if any)
- Anything that needs follow-up
Priority Mapping
- 0 = No priority
- 1 = Urgent
- 2 = High
- 3 = Medium
- 4 = Low
Important Rules
- Always search first — Never create without checking for duplicates
- Learn before creating — Read team patterns to match style
- Never guess IDs — Always use RESOLVE_CONTEXT to convert names
- Suggest structure — Offer sub-issues for broad tasks
- Confirm results — Show what was created with identifiers and URLs
1---2name: linear-create-issue3description: Create Linear issues intelligently - search for duplicates, learn team patterns, evaluate sub-issue breakdown, then create with proper context.4target: linear_agent5metadata:6 source: https://skillmd.com/skills/theexperiencecompany/linear-create-issue7---89# Linear Create Issue1011## When to Use12- User asks to "create an issue" or "file a bug"13- User asks to "add a ticket" or "track this"14- User describes a problem, task, or feature to be tracked15- User wants to create issues with sub-tasks1617## Tools1819### Discovery & Context20- **LINEAR_CUSTOM_GET_WORKSPACE_CONTEXT** — Get teams, projects, labels, states21- **LINEAR_CUSTOM_RESOLVE_CONTEXT** — Map fuzzy names → IDs (team, user, labels, project, state)22- **LINEAR_CUSTOM_SEARCH_ISSUES** — Search issues by keyword23- **LINEAR_CUSTOM_GET_ISSUE_FULL_CONTEXT** — Get full issue details24- **LINEAR_CUSTOM_GET_ACTIVE_SPRINT** — Get current sprint/cycle info25- **LINEAR_CUSTOM_GET_MY_TASKS** — Get authenticated user's assigned issues2627### Creation28- **LINEAR_CUSTOM_CREATE_ISSUE** — Create issue with all fields29 - Required: team_id, title30 - Optional: description, assignee_id, priority (0-4), state_id, label_ids, project_id, cycle_id, due_date, estimate, parent_id31 - Sub-issues: sub_issues array [{title, description, assignee_id, priority}]3233## Workflow3435### Step 1: Search for Duplicates (MANDATORY)3637Before creating anything, search for existing issues:3839```40LINEAR_CUSTOM_SEARCH_ISSUES(query="<keywords from user request>")41```4243If similar issues exist:44- Show them to the user: "I found these existing issues that look similar..."45- Ask if they want to proceed or update an existing one46- Only continue to creation after user confirms no duplicate4748### Step 2: Learn Team Patterns4950Understand how the team structures issues:51521. **Get workspace context:**53 ```54 LINEAR_CUSTOM_GET_WORKSPACE_CONTEXT()55 ```56 This reveals team names, available states, labels, and projects.57582. **Read recent team issues (2-3):**59 ```60 LINEAR_CUSTOM_SEARCH_ISSUES(query="recent")61 ```62 Study the results to learn:63 - Title format (e.g., "[Component] Description" vs plain descriptions)64 - Description structure (bullet points? acceptance criteria? steps to reproduce?)65 - Common labels used66 - Priority conventions67683. **Match the team's style** when writing the title and description.6970### Step 3: Evaluate Sub-Issue Potential7172If the user's request is broad or multi-faceted:7374- **Break it down:** Suggest logical sub-issues75 - Example: "Implement auth" → "Design login flow", "Implement OAuth", "Add MFA", "Write tests"76- **Ask the user:** "This looks like it could be broken into sub-tasks. Want me to create sub-issues?"77- **Keep it practical:** Only suggest 2-5 sub-issues; too many is unhelpful7879If the request is specific and focused, skip sub-issues entirely.8081### Step 4: Resolve All Entities8283Use RESOLVE_CONTEXT to convert names to IDs:8485```86LINEAR_CUSTOM_RESOLVE_CONTEXT(87 team_name="engineering",88 user_name="john",89 label_names=["bug", "critical"],90 project_name="Q1 Sprint",91 state_name="backlog"92)93```9495This returns: team_id, user_id, label_ids, project_id, state_id9697**For cycle_id** (adding to current sprint):98```99LINEAR_CUSTOM_GET_ACTIVE_SPRINT()100```101102### Step 5: Create the Issue103104```105LINEAR_CUSTOM_CREATE_ISSUE(106 team_id=resolved_team_id,107 title="Formatted like team's convention",108 description="Structured like team's existing issues",109 assignee_id=resolved_user_id,110 priority=2,111 label_ids=resolved_label_ids,112 project_id=resolved_project_id,113 state_id=resolved_state_id,114 cycle_id=sprint_cycle_id,115 sub_issues=[116 {"title": "Sub-task 1", "priority": 2},117 {"title": "Sub-task 2", "priority": 2}118 ]119)120```121122### Step 6: Confirm Results123124Report back clearly:125- Issue identifier (e.g., "ENG-456")126- URL to the issue127- What was set (assignee, labels, project, sprint)128- Sub-issues created (if any)129- Anything that needs follow-up130131## Priority Mapping132- 0 = No priority133- 1 = Urgent134- 2 = High135- 3 = Medium136- 4 = Low137138## Important Rules1391. **Always search first** — Never create without checking for duplicates1402. **Learn before creating** — Read team patterns to match style1413. **Never guess IDs** — Always use RESOLVE_CONTEXT to convert names1424. **Suggest structure** — Offer sub-issues for broad tasks1435. **Confirm results** — Show what was created with identifiers and URLs