Four workflow profiles
Bounded, standard, high-assurance, and exploratory paths select the required roles, gates, readiness denominator, and approval rules for the work.
AgentFlow 1.0 · Core mechanics
The delivery system from request to release.
AgentFlow combines risk-aware paths, named responsibilities, portable evidence, deterministic checks, and explicit authority so work can move quickly without becoming opaque.
Nine responsibilities
Product framing, analysis, architecture, developer planning, implementation, testing, review, technical writing, and PR readiness remain explicit even when one executor carries several roles.
Durable evidence
Requirements, decisions, validations, reviews, documentation, and handoffs live in issues, comments, commits, and PRs instead of private chat memory.
Portable contracts
Artifact references, lifecycle events, delivery handoffs, action boundaries, and transition envelopes keep context truthful across tools and sessions.
Deterministic assurance
Validators and executable evals check workflow state, evidence, collaboration, releases, skills, adapters, migrations, and multi-agent acceptance.
Release governance
Explicit assignment, impact, notes, planning, validation, and tag-to-release closeout make shipping part of the SDLC rather than an incidental semver change.
Authority stays separate from workflow
A selected path describes the delivery process; it does not silently grant permission to edit, open a PR, deploy, or perform an external action.
- One accountable executor is the baseline.
- Focused advisers and routed agents are optional.
- High-assurance security and acceptance gates stay human-controlled.
- Skipped-by-path roles do not reduce readiness.
- Follow-up issues replace hidden TODOs.
Validation surface
node bin/cli.mjs sdlc validate --json
node bin/cli.mjs sdlc audit --json
node bin/cli.mjs sdlc validate-release --path issue.json --json