Can Inspection Execution Be This Automated? Let Me Tell You About the Team Agent Pattern
To be honest, when I first saw this skill, I was a bit confused. Terms like "検品実行" (inspection execution) and "Team Agent パターン" (Team Agent pattern) sounded pretty impressive. But after digging into it, I realized this is basically a way to automate our quality inspection process! And it does so using a particularly clever parallel approach — just like calling in four inspectors at once, each responsible for one area, making efficiency take off.
What do we, as developers, hate the most? It's having to manually check all sorts of things after every feature is done — whether the specs are correct, whether performance is acceptable, whether there are security vulnerabilities, whether the UI matches the design mockups... There's a huge list of checks, and running through them manually is exhausting. This skill is designed to solve exactly that pain point. It can automate your inspection checklist and run it in parallel using a team collaboration model, saving both time and effort.
How Does It Actually Work?
The process goes roughly like this: all you need to do is input a feature name, and it automatically creates a Team, then spawns four "inspector" sub-agents within that team, each responsible for one domain:
- inspector-spec: Checks whether the spec and implementation are consistent — for example, whether the file paths, class names, and method names mentioned in the documentation can actually be found in the code.
- inspector-perf: Runs performance tests, using the REPL or debugging tools to measure memory usage and check SQL query counts.
- inspector-security: Checks for security vulnerabilities like XSS and SQL injection, as well as backward compatibility — whether URL parameters and CSV output still behave the same as before.
- inspector-ux: Reviews UI/UX and existing bug fixes, including design system consistency, responsiveness, and localization.
Each agent reads the inspection checklist file (docs/02_active/{feature}/09-inspection-checklist.md) and then executes its own portion accordingly. Here's the key part: after completing their checks, each agent must report back by sending a message via SendMessage, and update the task status using TaskUpdate, so the team lead can track progress.
Once all inspectors have finished, the team lead consolidates the results, fills in the "Judgment" column in the inspection checklist, generates an inspection summary, and then automatically commits the code. The entire process flows seamlessly without any manual intervention from you.
Installation and Configuration Aren't That Hard Either
To install this skill, you use npx. The command looks like this:
npx skills add https://github.com/bravesoft-inc/waterfall-agents --skill step09-runOnce installed, you can trigger it in Claude by entering "検品実行" or "/step09-run {feature name}". The prerequisite is that the project must have the corresponding inspection checklist file, and the checklist must include those sections: spec vs. implementation, performance, security, compatibility, UI/UX, and bug fixes — otherwise, the inspectors will have nothing to check.
One thing to note: the skill documentation mentions a "ゲートレビュー" (gate review) that every inspector must complete. If any inspector hasn't finished, the team lead will follow up. This ensures there are no missed checks.
Remember to Shut Down the Team After Use
There's a detail in this skill that I think is quite thoughtful: it includes a dedicated "チームシャットダウン" (team shutdown) step at the end. It requires you to verify that all tasks are marked as completed, force-complete any that aren't, and then delete the Team. This is likely to prevent resource leaks, since keeping a team running indefinitely also consumes resources. If deletion fails, there's a set of forced cleanup procedures you can reference.
In short, for projects using waterfall development, this skill is a real game-changer. It fully automates the tedious, repetitive quality inspection work, and with parallel execution, it saves a significant amount of time. I tried it myself, and I found that as long as you configure the inspection checklist properly, you don't have to worry about subsequent inspections at all — just sit back and wait for the results.
If you're also looking for an automated quality inspection solution, give this a try. It's easy to install, and trying it won't cost you anything. 😄
