Agent skill · operations · sickn33
agentflow
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and recoverable pipeline design.
Why this skill is useful
Adds executable scripts for orchestrating AI development pipelines with real-time task management and cost tracking that aren't available in public documentation.
What it needs
Requires claude installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
AgentFlow Overview AgentFlow turns your existing Kanban board into a fully autonomous AI development pipeline. Instead of building custom orchestration infrastructure, it treats your project management tool (Asana, GitHub Projects, Linear) as a distributed state machine — tasks move through stages, AI agents read and write state via comments, and humans intervene through the same UI they already use. The result is complete pipeline observability from your phone, recoverable task state (state lives in your PM tool, not in memory), and human override at any point by dragging a card. When to Use This Skill Use when you need to orchestrate multiple Claude Code workers across a full development lifecycle (build, review, test, integrate) Use when you want deterministic quality gates (tsc/eslint/tests) before AI review on AI-generated code Use when you want full pipeline visibility from your Kanban board or phone Use when running a solo or team project that needs autonomous task dispatch with cost tracking Use when you need orchestration designed to recover after session restarts Core Concepts 7-Stage Kanban Pipeline Tasks flow through: Backlog, Research, Build, Review, Test, Integrate, Done. Each stage has specific gates. The Kanban board IS the orchestration layer — no separate database, no message queue, no custom infrastructure. Stateless Orchestrator A crontab-driven one-shot sweep runs every 15 minutes. No daemon, no session dependency. If it crashes, the next sweep picks up where it left off because all state lives in your PM tool. Deterministic Before Probabilistic Hard gates (tsc + eslint + tests) run before any AI review, catching detectable errors before the more expensive review; coverage and cost must be measured. AI review comes after, as a second layer. Adversarial Review An independent review should report only substantiated findings and incomplete coverage. Do not require an arbitrary number of flaws or fabricate issues to pass a gate. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/agentflow