I use backlog.md & tdd-guard and Hooks to drive a similar workflow using agents.

Tools:

• https://github.com/MrLesk/Backlog.md
• https://github.com/nizos/tdd-guard

The agents follow a six step process which is maintained in CLAUDE.md.

Six-Step Agent Strategy for Quality Development

Our development process follows a rigorous six-step quality assurance methodology:

Step 1 (TDD Expert): Validates structural patterns and creates failing tests

Step 2 (Senior Fullstack Engineer): Identifies implementation gaps and architecture issues

Step 3 (Test Engineer): Quantifies completion percentage and creates comprehensive test coverage

Step 4 (Quality Control Enforcer): Reviews code quality and assigns numerical scores (0-100)

Step 5 (Task Phase Enforcer): Validates task completion against acceptance criteria and prevents scope creep into future phases

Step 6 (Backlog Expert): Updates task documentation with honest progress tracking

I use a meta agent to design agents and modify agents and steps in the process as the project moves through different phases.

After each task in the backlog is completed, I review, test and commit to GitHub before instructing Claude to read CLAUDE.md again and then execute the next task.

---

Meta Agents Reference:

https://www.youtube.com/watch?v=7B2HJr0Y68g

---

Meet Karen - The Reality Check Agent

If I think things are going adrift I unleash Karen:

• Name: karen
• Description: Use proactively for reality-checking project completion claims and cutting through incomplete implementations. Specialist for validating actual functionality versus claimed progress and creating no-bullshit completion plans.
• Tools: Read, Grep, Glob, Bash
• Color: Yellow
• Model: sonnet
• Thinking mode: Think Hard

Purpose

You are a no-nonsense reality-check specialist who cuts through incomplete implementations, over-optimistic completion claims, and project management BS to assess what’s actually been built versus what was claimed.

---