linear-workflow
Skill1 starsChanged 28 days agoMITView on GitHub
Use when working with Linear issues, milestones, dependencies, statuses, comments, or project roadmap context
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Diligence-AI/org-skillstheir own version, first seen Oct 13, 2026
- SkillMedev/project-managementtheir own version, first seen Oct 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Diligence-AI/org-skills★ 0same name
- SkillMedev/project-management★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read references/connector-contract.md before any Linear connector call.
- Very specific: line 15
Read references/task-lifecycle.md only for issue, dependency, claim, milestone, status, or task execution operations.
- Very specific: line 17
Read references/document-persistence.md only when reading or writing Linear Documents, retrospectives, learning indexes, or learning …
- Distinctive: line 23
Use compact projected reads first.
- Distinctive: line 24
Read all blocker states, but expand only unfinished or contract-relevant blockers within the active depth and node limits.
- Distinctive: line 26
Never mutate during a read-only request.
- Distinctive: line 30
Keep volatile plans and completion receipts out of stable issue descriptions.
- Distinctive: line 31
Do not infer completion, persistence, dependency, or milestone membership from titles or prior conversation state.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Linear Workflow
Linear is durable coordination memory for agents and humans. Keep descriptions stable, keep one authoritative current plan, and persist compact completion evidence. The active command's project scope, approval, context budget, and session boundary remain authoritative.
Load only the required operation rules
- Read
references/connector-contract.mdbefore any Linear connector call. - Read
references/task-lifecycle.mdonly for issue, dependency, claim, milestone, status, or task execution operations. - Read
references/document-persistence.mdonly when reading or writing Linear Documents, retrospectives, learning indexes, or learning entries.
Invariants
- Resolve the project before milestones, issues, or documents; stop on ambiguity.
- Use compact projected reads first. Expand full text only when it can affect the command result.
- Read all blocker states, but expand only unfinished or contract-relevant blockers within the active depth and node limits.
- Never mutate during a read-only request. For writes, re-read, apply only intended fields, and read back before reporting success.
- Preserve human-authored issue intent and enforce
Human draft -> Unplanned -> Backlog; never skip refinement or planning readiness gates. - Keep volatile plans and completion receipts out of stable issue descriptions.
- Do not infer completion, persistence, dependency, or milestone membership from titles or prior conversation state.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.