Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Agent Team Scaffold
Report the current state of the Planner → Generator → Evaluator loop — which stage is active, the last verdict, open issues, and what's blocking. Read-only. Triggers on "loop status", "where are we", "what's blocking", "show progress".
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-team:loop-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Report the current state of the Planner → Generator → Evaluator loop. Read-only —
Report the current state of the Planner → Generator → Evaluator loop. Read-only — do not start or modify work.
./out/ awaiting human sign-off.Loop: <deliverable>
Stage: <active stage>
Last verdict: <PASS/FAIL/APPROVE/REVISE> (<n> blocking, <n> advisory)
Blocking: <list or "none">
Next: <single next action>
Awaiting sign-off: <./out/ packages or "none">
Keep it concise. If no loop is active, say so.
npx claudepluginhub aws300/agent-team-scaffold --plugin agent-team2plugins reuse this skill
First indexed Jun 27, 2026
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.