Promote session plans to Linear Documents attached to issues with versioned histories.
npx skills add https://github.com/Cianai/ClinearHub --skill plan-persistence
Please help me install this Agent Skill. Skill: plan-persistence Source: https://github.com/Cianai/ClinearHub/tree/main/skills/plan-persistence Command: npx skills add https://github.com/Cianai/ClinearHub --skill plan-persistence
Plan lifecycle management using Linear Documents as the single source of truth. Use when discussing session plans, plan promotion to Linear, plan versioning, plan finalization at session end, how plans link to issues, how agents consume plans, checkbox-to-AC mapping, or any question about preserving context across Cowork and Code sessions. Also triggers for questions about session handoff, session context preservation, or how to resume work from a previous session's plan.
Promote the current session plan to the active issue as a Linear document.
High-intent search queries and answers about installing and using this skill.
To persist session plans to Linear issues, you promote them to Linear Documents attached to the issues. This ensures durable traceability by mapping plans to issue acceptance criteria, including scope, decisions, tasks, verification, and references.
Preserving context across Cowork and Code sessions is achieved by promoting plans to Linear Documents. This workflow uses versioned histories and back-links to maintain a single source of truth for session handoff and context preservation.
Checkbox-to-AC mapping works by ensuring session plans map directly to issue acceptance criteria (ACs) in Linear. When you finalize a plan at session end, the plan structure includes clear scope, decisions, tasks, and verification aligned with the issue.
Yes, you can sync plans between Cowork, Code, and Plannotator workflows. This cross-surface workflow ensures consistent planning across surfaces by using Linear Documents as the single source of truth for plan versioning and consumption.
Agents consume plans from previous sessions by accessing the versioned Linear Documents attached to issues. This allows agents to resume work from a previous session's plan using the back-links and preserved context within the Linear Document.
You need to promote a plan to a Linear Document when discussing plan promotion, plan versioning, or plan finalization at session end. It is required for preserving context across sessions and ensuring plans map to issue acceptance criteria.
kinglerTransform planning documents into hierarchical Linear issues with linked parent-child relationships.
alex-tgkGenerate INVEST-compliant user stories with acceptance criteria from epics.
RayzerrekAnalyzes denied planning archives and generates an HTML dashboard report with corrective prompts.
Thawatchai-PetkaewManage versioned delivery artifacts and synchronize them with Linear issue tracking.
