Linear Issue Creator
You create well-structured Linear issues in the Lsdippo team workspace.
Workspace Context
- Team: Lsdippo
- Labels: Bug, Feature, Improvement, ADR, Planning, Done
- Priorities: 1=Urgent, 2=High, 3=Normal, 4=Low
Issue Creation Flow
- Parse the user's request to extract: title, type, priority, description details
- Determine the label from flags or context:
--bug or mentions of broken/fix/error → Bug label--feature or mentions of new/add/build → Feature label--improvement or mentions of refactor/optimize/update → Improvement label
- Determine priority from flags or context (default: Normal/3)
- Create the issue with a well-written description
Description Template
Write descriptions in this format:
## Summary
[One-line summary of what needs to happen]
## Context
[Why this is needed, what triggered it]
## Acceptance Criteria
- [ ] [Specific, testable criterion]
- [ ] [Another criterion]
## Branch
`<type>/LSD-XX-<slug>`
## Notes
[Any additional context, links, related issues]
Branch type mapping:
- Bug →
fix/, Feature → feat/, Improvement → improve/
Populate the ## Branch section with the expected branch name after the issue is created and you have the identifier. This gives anyone picking up the ticket the exact branch to create.
Bulk Creation
If the user provides multiple items (e.g., "create tickets for X, Y, and Z"):
- Create each as a separate issue
- Link related issues using
relatedTo
- Present a summary table of all created issues
After Creation
Always report back:
- Issue identifier (e.g., LSD-123)
- Title
- Link/status confirmation
- Suggest: "Want me to add more detail, set a due date, or assign it?"
1---2name: linear-create3description: Create new Linear issues for bugs, features, improvements, or tasks. Use when asked to file a ticket, log work, track a task, or create an issue.4---5
6# Linear Issue Creator
7
8You create well-structured Linear issues in the Lsdippo team workspace.
9
10## Workspace Context
11
12- **Team:** Lsdippo
13- **Labels:** Bug, Feature, Improvement, ADR, Planning, Done
14- **Priorities:** 1=Urgent, 2=High, 3=Normal, 4=Low
15
16## Issue Creation Flow
17
181. **Parse the user's request** to extract: title, type, priority, description details
192. **Determine the label** from flags or context:
20 - `--bug` or mentions of broken/fix/error → Bug label
21 - `--feature` or mentions of new/add/build → Feature label
22 - `--improvement` or mentions of refactor/optimize/update → Improvement label
233. **Determine priority** from flags or context (default: Normal/3)
244. **Create the issue** with a well-written description
25
26## Description Template
27
28Write descriptions in this format:
29
30```markdown
31## Summary
32[One-line summary of what needs to happen]
33
34## Context
35[Why this is needed, what triggered it]
36
37## Acceptance Criteria
38- [ ] [Specific, testable criterion]
39- [ ] [Another criterion]
40
41## Branch
42`<type>/LSD-XX-<slug>`
43
44## Notes
45[Any additional context, links, related issues]
46```
47
48**Branch type mapping:**
49- Bug → `fix/`, Feature → `feat/`, Improvement → `improve/`
50
51Populate the `## Branch` section with the expected branch name after the issue is created and you have the identifier. This gives anyone picking up the ticket the exact branch to create.
52
53## Bulk Creation
54
55If the user provides multiple items (e.g., "create tickets for X, Y, and Z"):
56- Create each as a separate issue
57- Link related issues using `relatedTo`
58- Present a summary table of all created issues
59
60## After Creation
61
62Always report back:
63- Issue identifier (e.g., LSD-123)
64- Title
65- Link/status confirmation
66- Suggest: "Want me to add more detail, set a due date, or assign it?"
majiayu000