What it is
A public stack for the shared pieces behind repo-local .go workflows: schemas, CLI behavior, and workflow conventions.
Project page
Go Workflow Stack
Reusable CLI and schemas for repo-local .go agent workflow state across projects, templates, and automated handoffs.
agent-workflow developer-tools schemas cli
CLI
surface
Schemas
contract
Reusable
stack
Project notes
Why it exists
Agent workflow should not be reinvented inside every repo. The stack centralizes the reusable contract while projects keep their own local state.
Useful for
Projects that need claimable tasks, structured handoffs, validation, and repeatable agent work without depending on chat memory.
How it works
The stack defines reusable behavior and contracts. Individual repos can then adopt the same workflow shape through the project template or their own .go setup.
GitHub source
GitHub remains the live source for schema details, CLI commands, examples, and implementation changes.
Relationship
It is the engine layer next to go-project-template: one repo carries the reusable stack, the other gives new projects a clean starting shape.
Good fit
Use it when multiple repos need the same agent workflow discipline, validation rules, and handoff vocabulary.
Design direction
Make autonomous work boringly inspectable: explicit state, explicit contracts, and no hidden dependency on whatever a chat session remembers.
This page gives the public context before the code; use GitHub for the current CLI, schemas, issues, and releases.