Define Linear issue ownership, status transitions, and evidence-based closure rules.
npx skills add https://github.com/Cianai/ClinearHub --skill issue-lifecycle-cianai
Please help me install this Agent Skill. Skill: issue-lifecycle Source: https://github.com/Cianai/ClinearHub/tree/main/skills/issue-lifecycle Command: npx skills add https://github.com/Cianai/ClinearHub --skill issue-lifecycle-cianai
Defines clear ownership boundaries between AI agents and humans, status transition rules, and operational patterns for Linear issue management.
Review the documented lifecycle and start applying the standard transitions to new Linear issues.
High-intent search queries and answers about installing and using this skill.
Linear issue lifecycle management defines clear ownership boundaries where AI agents own process artifacts like status and labels, while humans own business judgement like priority. This ensures consistent policy application across triage, in-progress work, reviews, and closure.
Linear issue governance is enforced by applying detailed status transition rules for triage, todo, in-progress, in-review, and done states. Immediate context label changes and references to protocol documents ensure all triage actions are fully auditable.
The Linear issue closure protocol requires evidence-based closure with mandatory closing comments and quality scoring. This ensures that completed issues meet quality standards and provide an auditable record of the final state before transition to done.
Yes, this issue lifecycle management applies to in-progress work and reviews across projects. It implements consistent rules for statuses, context labels, and spec states, ensuring uniform policy application regardless of the project scale.
AI agents are limited to owning process and implementation artifacts such as status, labels, and specs. Business judgement, including priority and deadline decisions, remains a human responsibility to prevent automated misalignment with project goals.
No specific dependencies are required to implement status-transition and closure protocols for issue management. The lifecycle rules operate independently, referencing protocol documents to enforce auditability and consistent issue governance.
lobehubAutomate Linear issue status updates and completion comments via MCP tools.
raindayTrack blog article quality scores and generate delta reports from snapshots.
lilmuckersClassify GitHub issues with type and agent-routing labels.
ShmurdocDetect deploy platforms and write deployment settings to CLAUDE.md.
