---
title: "agentflow"
description: "An opinionated workflow for shipping production-ready changes with coding agents."
canonical: https://agentpluginsdirectory.com/plugins/agentflow
last-updated: 2026-09-12
---

# agentflow
An opinionated workflow for shipping production-ready changes with coding agents.
- Slug: agentflow
- Publisher: Reforma, Inc.
- Repository: https://github.com/reforma-ai/agentflow
- Manifest: plugin.json
- License: MIT
- Category (editorial): other
- Skills: 7 (code-review, document, grill, handoff, plan, research, tdd)
- MCP servers: 0
- Stars: 3
- Repository created: 2026-08-29
- Repository last pushed: 2026-09-11
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/agentflow
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What agentflow does, in the publisher's words

An opinionated workflow for shipping production-ready changes with coding agents. Research when needed, grill decisions, plan PR-sized slices, then implement and review each slice one by one.

A single open-ended prompt works for a tiny change. On larger work, scope expands, decisions disappear into chat history, and the model fills the gaps with guesses, skipping edge cases, weakening validation, or choosing the wrong abstraction. Start a new chat, and all the reasoning is gone.

Spec-driven frameworks such as OpenSpec and Spec Kit address this by moving intent into documents, proposals, requirements, designs, and task trees, then driving the agent from them. The idea is sound, but the cost is real: commands to learn, many artifacts before code starts, poor fit for small fixes, and enough friction to push people back to unstructured chat when the ceremony outweighs the task.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/reforma-ai/agentflow/HEAD/README.md

## Skills

- code-review: Use when a PR-sized slice is complete and needs review before commit, or when the diff may reinvent APIs, add wrappers, or grow without shrinking. Not for open-ended bug hunts.
- document: Turn research, a plan, or a shipped change into a durable project page.
- grill: Relentless interview to sharpen a plan or design until every branch is resolved.
- handoff: Use when an implementation PR is done and unfinished work will continue in a fresh chat, or when context is about to be compacted and the next slice needs a durable baton. Not for mid-grill notes.
- plan: Use when decisions are settled and the work needs ordered PR-sized slices, or when an existing plan must be updated after scope bleed. Not grill. Not handoff.
- research: Use when an area, technology, or landscape must be mapped before changing code, or when findings need to survive compaction or a fresh chat. Not for a one-file lookup.
- tdd: Use when building or fixing behavior test-first, when the user mentions red-green-refactor or integration tests, or when implementation would otherwise proceed without a failing test at an agreed seam.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.