3 ms·

This sounds interesting. Can you go a bit deeper or provide references on how to implement the green/red/refactor subagent pattern?

• dmd 7mo ago
  That's the cool bit - you don't have to. CC is perfectly well aware and competent to implement it; just tell it to.
  • irishcoffee 7mo ago
    "So this is how liberty dies... with thunderous applause.” - Padmé Amidala s/liberty/knowledge
  • deleted 7mo ago
    [deleted]
• pastescreenshot 7mo ago
  What has worked better for me is splitting authority, not just prompts. One agent can touch app code, one can only write failing tests plus a short bug hypothesis, and one only reviews the diff and test output. Also make test files read only for the coding agent. That cuts out a surprising amount of self-grading behavior.
  • huslage 7mo ago
    How do you limit access like that?
• elemeno 7mo ago
  It’s not an agentic pattern, it’s an approach to test driven development. You write a failing test for the new functionality that you’re going to add (which doesn’t exist yet, so the test is red). You then write the code until the test passes (that is, goes green).
• dworks 7mo ago
  I built rlm-workflow which has stage gating, TDD and sub-agent support: https://skills.sh/doubleuuser/rlm-workflow/rlm-workflow https://skills.sh/doubleuuser/rlm-workflow/rlm-workflow