Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?"
/plugin marketplace add jclfocused/claude-agents/plugin install linear-planning-workflow@laserfocused-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples.mdreferences.mdThis skill guides the creation of well-structured, actionable Linear issues that any developer or AI can pick up and execute independently.
Apply this skill when:
## IMPORTANT: Linear Issue Discipline
[Standard discipline rules]
---
## Problem
[1-2 sentences: Why does this feature need to exist?]
## Solution
[1-2 sentences: What are we building to solve this?]
## High-Level Implementation
[Bullet points: Key technical decisions, patterns]
## Codebase Investigation Findings
[What patterns to follow, similar features, code locations]
## Out of Scope / Deferred
[Explicitly list what we're NOT doing]
## Objective
[1-2 sentences: What specific thing needs to be done?]
## Acceptance Criteria
- [ ] [Specific, testable criterion 1]
- [ ] [Specific, testable criterion 2]
- [ ] [Specific, testable criterion 3]
## Implementation Notes
- Relevant files: [paths]
- Patterns to follow: [reference]
- Dependencies: [other issues]
ALWAYS include Mermaid diagrams when applicable. Linear supports Mermaid diagrams natively in issue descriptions. Use them to visualize:
Use standard markdown code fences with mermaid as the language identifier:
```mermaid
flowchart TD
A[Start] --> B[End]
```
| Type | Use Case | Syntax |
|---|---|---|
flowchart TD | Top-down user flows, process flows | flowchart TD |
flowchart LR | Left-right horizontal flows | flowchart LR |
sequenceDiagram | API calls, service interactions | sequenceDiagram |
stateDiagram-v2 | State machines, status transitions | stateDiagram-v2 |
erDiagram | Database schemas, entity relationships | erDiagram |
classDiagram | Class relationships, component structure | classDiagram |
Always include a diagram when:
The diagram should appear in:
Remember: A good issue can be executed by anyone who reads it.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.