Menu
Use when working with Linear issues/projects: create, update, query, comment, attach files, or inspect Linear URLs/tickets.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use only when the user explicitly asks or allows delegating implementation to a Codex worker — launch Pi running openai-codex/gpt-5.6-sol (xhigh) as a visible sidecar implementer that this session orchestrates over AMQ. Write exact task specs, dispatch with --kind todo, validate the results yourself, then iterate, resume, respawn, or launch another worker. Never invoke on your own initiative.
Use only when the user explicitly allows or asks for this skill to be invoked to pair with a second agent harness — launch a sidecar, get a second opinion from another agent, have one harness drive another, or review work with another agent over AMQ. Otherwise, never invoke it.
first step of planning
convert structure outline into a detailed implementation plan
Create a Product Requirements Document with inline mockups
generate research questions based on a task, spec, or ticket
| name | linear |
| description | Use when working with Linear issues/projects: create, update, query, comment, attach files, or inspect Linear URLs/tickets. |
Manage Linear issues, projects, cycles, teams, labels, and documents using the linear CLI.
The CLI uses credentials managed via linear auth. If auth fails, ask the user to run linear auth.
linear issue list # List your assigned issues
linear issue view ENG-123 # View issue details
linear issue create # Create issue (interactive)
linear issue update ENG-123 # Update issue
linear issue start ENG-123 # Start working on issue
linear issue url ENG-123 # Print issue URL
linear issue title ENG-123 # Print issue title
linear issue describe ENG-123 # Print title + Linear-issue trailer
linear issue comment # Manage comments
linear issue attach ENG-123 ./file.png # Attach file to issue
linear issue pr ENG-123 # Create GitHub PR with issue details
linear issue delete ENG-123 # Delete issue
linear issue relation # Manage issue relations
linear issue id # Print issue from current git branch
linear project list # List projects
linear project view <projectId> # View project details
linear project create # Create project
linear project update <projectId> # Update project
linear project delete <projectId> # Delete project
linear project-update # Manage project status updates
linear cycle list # List cycles for a team
linear cycle view <cycleRef> # View cycle details
linear team list # List teams
linear team members [teamKey] # List team members
linear team id # Print configured team id
linear team create # Create team
linear team delete <teamKey> # Delete team
linear team autolinks # Configure GitHub autolinks
linear label list # List labels
linear label create # Create label
linear label delete <nameOrId> # Delete label
linear document list # List documents
linear document view <id> # View document content
linear document create # Create document
linear document update <documentId> # Update document
linear document delete [documentId] # Delete document
linear api [query] # Raw GraphQL API request
linear config # Generate .linear.toml configuration
linear schema # Print GraphQL schema
Use -w <slug> on any command to target a specific workspace:
linear -w mycompany issue list
linear issue id # Returns issue ID from branch name
linear issue view $(linear issue id) # View details for current branch's issue
linear issue create --title "Bug: login fails" --team ENG --priority urgent --label bug
linear issue update ENG-123 --state "In Progress"
| Error | Solution |
|---|---|
| "Not authenticated" | Run linear auth |
| "Issue not found" | Check issue ID format (e.g., ENG-123) |
| "Team not found" | Run linear team list to see available teams |