Thank you, this is a great developer workflow - solid foundation

I simply wanted to say thank you. I came across the Reddit post and after spending time with it, digging into it, doing some practice work, I've turned this into a so-far, solid, repeatable, somewhat scalable foundation for using claude code with a small team of devs.

So thank you!

For anyone curious, some of my customizations:

I created a /skill-audit command - I run this first against a requirements document. It audits the skills folder after reading the requirements then gives me a list of necessary skills to create, existing skills to edit, and existing skills I can remove from the dir. (Note: I keep the claude code folder versioned and add skills to it over time so a developer can basically check it out, add it to a project and customize skills to the project. Your practice may vary)

I edited /dev-docs to require a written requirements doc, not just a prompt (this aligns with my needs). Dev-docs also reads through skills in order to pull tests and code patterns into the dev plan, context, and tasks. Tasks are written following a specific pattern (phase x, task x.y) This is to support a new command, /run-task

/run-task is a command that executes one or more tasks (remember, run tasks in small sizes to avoid hallucinations), then immediately triggers the code-architect-reviewer agent.

Claude.ai is a great help in reviewing the processes & has been a help in customizing things.

Cheers, and again - thanks!