Claude Code Workflow Manager
npx claudepluginhub azevedo-home-lab/claude-code-workflowsStructured workflow enforcement for Claude Code with phase gates, coaching, and autonomy levels
Continuous Learning — detects patterns in workflow observations and proposes improvements
Structured development with Claude Code. Think before coding, review before shipping.
Claude Code is powerful but undisciplined. Left to its defaults, it:
The objective is to make Claude Code behave more like a disciplined senior engineer
Inspired by cc-sessions (DAIC workflow enforcement with trigger-phrase automation and sub-agents for Claude Code) This project builds on top an opinionated workflow enforcement system with:
Four tools that work together:
Six phases. Code edits are blocked until you discuss and approve a plan.
| Phase | Edits | What happens |
|---|---|---|
| OFF | Allowed | No enforcement |
| DEFINE | Blocked | Frame the problem, define outcomes |
| DISCUSS | Blocked | Research approaches, write plan |
| IMPLEMENT | Allowed | Execute plan with TDD |
| REVIEW | Allowed | Parallel review agents + verification |
| COMPLETE | Blocked | Validate outcomes, docs, open issues, handover |
Commands: /define /discuss /implement /review /complete /off /proposals /debug /autonomy
Any command can jump to any phase. /off closes the workflow. Soft gates warn when skipping steps.
See Architecture — Phase Model for the full breakdown: steps, agents, gates, milestones, and coaching per phase.
Orthogonal to phase, the autonomy level controls how independently Claude operates. Set with /autonomy off|ask|auto (default: ask):
▶ Supervised (off): Step-by-step pair programming. Claude executes one plan step at a time, presents the change, and waits for your review before proceeding. Writes follow phase rules.▶▶ Semi-Auto (ask): Claude works freely within each phase but stops at phase boundaries for review and guidance before transitioning. No auto-commits.▶▶▶ Unattended (auto): Full autonomy. Claude auto-transitions between phases, auto-fixes review findings, auto-commits. Stops only when user input is genuinely needed or before git push.Autonomy symbols are shown in the status line alongside the current phase.
Each cycle produces a plan (problem, approaches, rationale) and a spec (requirements, tasks, acceptance criteria).
| Tool | What it does | Docs |
|---|---|---|
| Workflow Manager | Phase-based enforcement + coaching | Architecture |
| Integrated Superpowers | Auto-activated development skills | Hooks reference |
| Integrated claude-mem | Persistent cross-session observations | Hooks reference |
| Status Line | Informational status bar | plugin/statusline/statusline.sh |
Add the marketplace and install:
/plugin marketplace add azevedo-home-lab/claude-code-workflows
/plugin install workflow-manager
The plugin auto-wires hooks, installs the statusline, and initializes project state. No manual configuration needed.
Installed separately with --iterm or --yubikey flags: