agentflow

AgentFlow

Your Kanban board builds your code.

The first AI development pipeline that uses your project management tool as the orchestration layer.
Full observability. Deterministic quality gates. Zero custom infrastructure.

Quick Start • Architecture • Getting Started • Gap Registry • Comparison

What is AgentFlow?

AgentFlow turns your existing Kanban board (Asana, GitHub Projects, Linear, Jira) into a fully autonomous AI development pipeline. Instead of building custom orchestration infrastructure, AgentFlow treats your project management tool 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: Complete pipeline observability from your phone. Crash recovery for free (state lives in your PM tool, not in memory). Human override at any point by dragging a card.

Why AgentFlow?

Most AI coding tools either give you a chatbot or a black-box agent. AgentFlow gives you a visible, auditable pipeline where:

• Every decision is a comment on a task card
• Every stage transition is a card moving between columns
• Every retry carries accumulated context from previous attempts
• Every cost is tracked per-task with automatic guardrails
• Every failure pattern is captured and fed back into the system

You don't need to trust a black box. Open your Kanban board and watch the pipeline work.

Key Features

Pipeline Orchestration

• 7-stage Kanban pipeline: Backlog → Research → Build → Review → Test → Integrate → Done
• Stateless orchestrator: One-shot sweep via crontab — no daemon, no session dependency, crash-proof
• Transitive priority dispatch: Tasks that unblock the most work get built first (automatic critical path)
• Conflict-aware scheduling: Parallel tasks touching the same files are serialized automatically

Quality Gates

• Deterministic before probabilistic: tsc + eslint + tests run as hard gates before any AI review — catches ~60% of issues at near-zero cost
• Adversarial AI review: Reviewers must "list 3 things wrong before deciding to pass"
• Coverage gate: 80% threshold on new files before promotion to Test stage
• Integration testing: Full suite runs on main after every merge — auto-reverts on failure

Observability & Cost Tracking

• Full pipeline observability from your phone — every task card shows current stage, assigned agent, retry count, and accumulated cost
• Per-task cost tracking with stage cost ceilings (Sonnet default: Research ~$0.10, Build ~$0.40, Review ~$0.10, Test ~$0.05, Integrate ~$0.03)
• Automatic cost guardrails: Warning at $3/$8, hard stop at $10/$20 (Sonnet/Opus) with human escalation
• Real-time status dashboard pinned to each project
• Heartbeat monitoring: Dead agents detected and reassigned within 10 minutes

System Learning

• Feedback loops with accumulated context: Every retry carries what was tried, what failed, and what to do differently
• System-level retrospectives: Every 10 completed tasks, common failure patterns are extracted to LEARNINGS.md
• Cross-task learning: Builders and reviewers read LEARNINGS.md before starting work
• Spec drift detection: SHA-256 hash comparison catches requirement changes mid-sprint

Safety & Recovery

• Auto-revert on integration failure: git revert (new commit, never force-push)
• Graceful shutdown: Active workers finish, unstarted tasks return to backlog
• Blocked task detection: After 2 failed attempts, tasks escalate to human review
• Scope creep detection: PR diff files compared against predicted files list
• Secret management: Mock values in tests, environment variables in code, manual verification flags for real API tasks

Architecture