Browse / Product management / Software development / claude-code-workflow
claude-code-workflow
rbah31
A structured, sprint-based workflow for AI-assisted development with Claude Code.
Open rbah31/claude-code-workflow → Does not match the four rules.
agentic-workflowai-agentsanthropicclaude-codedeveloper-toolstemplateworkflow
Built for Claude Code
ships .claude and nothing for other agents.
In its own words
A nine-agent development team. PM proposes, QA challenges, six technical agents build. You invoke and validate.
June 2026 context
Anthropic shipped a lot this quarter — managed agents, remote operations from your phone, dynamic scheduled tasks for monitoring without leaving your session, and Opus 4.8. This repo assembles those pieces into a working multi-agent development team you can clone today, inspect end-to-end, and adapt to your project.
Why this exists
The human only does two things: invoke and validate. Everything else is encoded in skills.
Without structure, three things happen when you build with Claude Code:
- Claude drifts. Long conversations get compacted, instructions disappear, code stops respecting standards.
- There's no traceability. Every session is an island. You lose track of what was decided, why, and where you are.
- Quality is not systematic. The temptation is build → ship without review or tests.
Engineers solved how to structure work decades ago — sprints, planning, review, retrospectives, the discipline that DevOps culture put in place. We didn't invent a new method for AI. We taught the AI how to follow ours. The repository below is the result of two months of running structured AI-assisted development on a real production project. If you find yourself copy-pasting prompts or manually dictating steps to Claude, that's a workflow bug. It should be in a skill.
Quoting 20% of the README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.