Issue Shaping
Transform needs, problems, or ideas into complete, actionable, developer-oriented tickets.
Full reference: Ticket Creator Prompt
Linear Config
| Setting | Value |
|---|---|
| Default Team | Product Development (DEV) |
| Tools | linear_createIssue, linear_searchIssues, linear_getLabels |
Teams
| Team | Key | ID |
|---|---|---|
| Product Development | DEV | 0949be32-5dd7-4ced-80d9-f055c999f1e1 |
| Commerce | COM | 56707273-2d58-418e-b9fb-772674792089 |
| Fullfilment | FUL | 1cd32263-7d92-426e-9923-1fdc433b6b9a |
| QA | QA | 318b09cc-ab8a-4544-a1cb-05be388d0935 |
| Product Design | DES | 51778a4b-e373-4704-a50f-857709a6a22c |
| Product Support | SUP | 8d28397f-3bb5-4db1-817f-d2d4acbb66ba |
| Customer Success | CUS | 66a31498-9dc8-4c0d-b9f5-7b4c3d09ac80 |
Workflow States
| State | ID | Use |
|---|---|---|
| Backlog | 9f7714a2-731a-4630-8b33-7462a26cce2c | Default |
| Shaping | c7bfe76e-ca29-40d9-810e-3b49bfaa702f | Needs definition |
| Todo | b3635693-0477-4add-a6e6-b26efa811a95 | Ready for work |
Issue Types
| Type | Template | Prefix |
|---|---|---|
| Bug | templates/bug.md | [Bug] |
| Feature | templates/feature.md | [Feature] |
| Improvement | templates/improvement.md | [Improvement] |
| Task | templates/task.md | [Task] |
| User Story | templates/user_story.md | [User Story] |
Critical Flows (require extra detail)
- Auth & Identity: Login, registration, permissions
- Commerce: Cart, checkout, payments, subscriptions
- Content: Reading, download, playback
- Integrations: External APIs, webhooks
- Sensitive Data: Payments, personal data
If ticket impacts a critical flow → include Business Rules + Error handling.
Process
1. Investigation (BEFORE writing)
1. Search docs/product/ and docs/engineering/ for related functionality
2. Identify similar existing behaviors
3. Understand Current State of the system
4. Identify dependencies with other features
2. Determine Type
- Bug: Something broken
- Feature: New functionality
- Improvement: Enhance existing
- Task: Technical work
- User Story: From user perspective
3. Discovery Questions
Follow template for selected type. Use AskUserQuestion in batches of 2-3.
4. Check Duplicates
linear_searchIssues({ query: "{keywords}", teamId: "0949be32-5dd7-4ced-80d9-f055c999f1e1" })
5. Create Issue
Use format from corresponding template.
Quality Criteria
Basic (all tickets)
- Clear, descriptive title
- Description explains WHAT and WHY
- Verifiable acceptance criteria
- Labels: Type + Project + Domain
Intermediate (Features, Improvements)
- Current State documented
- Concrete examples (URLs, params)
- Testing scenarios (8-10 minimum)
Advanced (Critical Features)
- User Flows documented (3-5)
- Clear Business Rules
- Edge cases covered
Principles
- Describe WHAT the system should do
- Do NOT describe HOW to implement it
- Focus on business value and UX
- Do NOT propose technical solutions
- Document verifiable business rules
Project Labels
| Label | ID | Service |
|---|---|---|
| Farfalla | 5fd5841f-f2a0-4744-852c-53ce0ea15afe | Core monolith |
| Volpe | c49cc6a4-3b24-47c8-8584-a8c393592923 | Reader API |
| Micelio | eb280fb7-c8ea-40c4-bddb-14ac0ee54c66 | CDN proxy |