diolog-tasks-pipeline
claudeThree native skills that run the Diolog Tasks issue pipeline — triage, plan, and worker — entirely inside your interactive Claude Code session (no Agent SDK, so usage draws from your standard interactive allowance, not the separate Agent SDK credit). Formerly linear-issue-pipeline; now targets the diolog-tasks MCP (mcp.diolog.com.au). tasks-triage runs a technical + Specification Sentinel product review and posts a non-technical readiness comment; tasks-plan classifies a tier, investigates the codebase, writes docs/plans/{id}.md and comments the repo-relative path (no file upload); tasks-worker implements a planned issue in an isolated worktree via dynamic ultracode workflows (understand → implement → rebase → acceptance review → resolve), with no remote PR. The plan and worker fan out parallel subagents via the Workflow tool to speed up large investigations. Recalibrated for current-model behaviour (Anthropic's Claude Opus 5 prompting guidance), ported from the generalized twin: tasks-worker's per-phase gate is explicitly a conformance check (evidence-shaped — the clause, the file:line, the gate you ran) rather than a second correctness review stacked on a phase that already reviewed itself; adversarial finding-verification is aimed at Criticals, structural fixes, and locked-decision reversals rather than blanket 1:1, and no reviewer is briefed to be conservative; the completion comment keeps to tables/counts/drops/gates rather than narrating the phases; and tasks-triage/tasks-plan gain the effort dial plus length budgets. All three point at the twin's new pipeline-wide canonical feature-spec-pipeline/skills/work/references/model-and-effort.md. v2.4.0 (from the WEB-4905 110-ticket audit): a fourth skill, tasks-verify — an independent fresh-session acceptance verifier that re-derives requirements from the ticket and closes them on typed behavioural evidence (browser measurements, exercised requests, stored-row counts) before a ticket is treated as done; evidence-typ
4 skills