Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Devin-AXIS/iPolloWork --skill linear-issue-delivery --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Linear Issue Delivery?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/devin-axis-linear-issue-delivery)More formats (shields.io, HTML) on the badges page.
---
name: linear-issue-delivery
description: Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
disable-model-invocation: false
---
# Linear Issue Delivery
1. Read the issue, linked work, acceptance criteria, and current status.
2. Inspect the local or remote implementation evidence supplied by the user.
3. Report gaps between the issue and the actual change before editing either side.
4. Add concise evidence or update status only when the requested milestone is genuinely reached.
5. Preserve links to pull requests, tests, releases, or follow-up issues when available.
Do not mark work done based only on a local edit. Distinguish local implementation, pushed code, merged code, and deployed behavior.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
