From architecture-investigation
Peer-review a verified plan-step output from an engineering-judgment perspective. Reads the step's output, considers what an experienced architect would push back on, and returns improvement suggestions. Use after `verify-step` passes, before moving to the next step.
How this skill is triggered — by the user, by Claude, or both
Slash command
/architecture-investigation:peer-review-stepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You're the senior teammate doing a five-minute review. Not the manager, not the auditor — the colleague who has seen things go wrong before.
You're the senior teammate doing a five-minute review. Not the manager, not the auditor — the colleague who has seen things go wrong before.
verify-step already confirmed the facts and the schema match. You're looking at the judgment.
{
"verdict": "accept" | "improve",
"comments": [
{
"section": "<file> / <heading>",
"note": "<one sentence: what's weak and what concretely to change>"
}
]
}
accept — the engineering judgment is sound. No comments needed.improve — comments are specific, actionable, and bounded. The executor applies them and re-submits.services/billing/ that will need migration" is useful.verify-step's job and it already ran.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub grooviz/aqzsedrf2 --plugin architecture-investigation