Linear workflow issue lifecycle plugin¶
- Date: 2026-04-21
- Status: Accepted
- Tags:
tooling
Context¶
The Cyrus agent workflow uses Linear issues as the source of truth for task tracking. Managing issue lifecycle (create, update, transition) requires switching to the Linear UI or using the MCP Linear server. A dedicated plugin for issue lifecycle management inside Claude Code would reduce context switching and integrate more naturally with the Cyrus workflow.
Decision¶
Install the linear-workflow plugin on the work laptop. It provides native Claude Code tools for creating, updating, and transitioning Linear issues. Documentation lives at linear/linear-workflow-plugin.md rather than in claude/plugins-work-laptop/ since it is a Linear-specific integration.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
| MCP Linear server only | Works but adds operational complexity (server management, auth rotation) |
| Linear UI for all issue management | Too much context switching during deep work sessions |
| GitHub Issues as primary tracker | Linear is the established source of truth for the Phazeight team |
Consequences¶
Positive:
- Full issue lifecycle management without leaving Claude Code
- Natural pairing with Cyrus agent workflow
Negative / Trade-offs:
- Overlaps with MCP Linear server capabilities — need to decide which to use for what
- Plugin must be validated from the work laptop environment
Ongoing obligations:
- ✅ Validated 2026-04-21 —
linear-workflow:linear-plan,linear-triage,linear-refine,linear-quality-gateskills confirmed active on work laptop - Overlap resolution:
mcp__plugin_linear_linear__*MCP tools handle raw API calls (bulk queries, programmatic data); linear-workflow plugin handles natural-language issue lifecycle management in Claude Code sessions. No conflict — complementary layers.