Pre-task analysis and architecture design. TRIGGER for all tasks, without exception — mandatory gate before any sub-agent is spawned. Main Agent provides raw task description and codebase context; architect determines task boundaries and returns decomposition. SKIP: implementation, external technology research …
Implements bounded delivery slices with clear acceptance criteria. TRIGGER when: (1) task has explicit files-to-modify and definition of done, (2) slice is single-role with no architectural uncertainty, (3) the mandatory architect decomposition gate has already been cleared for this task. SKIP: strategic decisions…
Validates completed slices against acceptance criteria. TRIGGER when: (1) developer marks a slice devdone or readyforqa, (2) runtime or manual verification is required. SKIP: artifact-only or unit-only tasks (validator run / test suite serves as QA), tasks still inprogress.
One of wgm's four docs-audit personas — reviews documentation for architectural fit, strategic consistency, and constitution conformance from a principal developer's vantage point, reporting findings only.
Consolidates wgm's four docs-audit personas into one paper-trail report — normalizes feedback, preserves dissent, and classifies every action item strictly as Agent action or Operator action.
This directory contains the 12 Claude Code agents that implement the SpecRoute skeleton. They are project-internal - they build SpecRoute itself, not consumer-facing templates that ship as artifacts.
Use when checking whether SpecRoute's claims about the outside world are still true - vendor config surfaces, hook event taxonomies, frontmatter contracts, version anchors, transition dates, and counts that must match disk. Owns the currency cycle, not the prose. Runs before releases, after any vendor ships a breaking…
Parallel bias-isolated review with 4 specialized single-domain reviewers (security, performance, test coverage, correctness). Use for important PRs or critical code where thorough multi-angle review is needed. Each perspective has blinders — forces deeper analysis per domain.
Mandatory pre-implementation interrogation. Use before any non-trivial coding task to surface assumptions, find existing solutions, and prevent over-engineering. Forces 6 critical questions before a single line of code.
Multi-depth research agent with configurable intensity. Use for any research task — from quick lookups to nuclear-level exhaustive investigations. Specify depth in the prompt: surface, basic, deep, in-depth, ultra, nuclear, overkill.
Explores the codebase and returns concise summaries of code structure, relationships, and patterns. Use for understanding existing code before making changes.
Reviews code in two passes: first spec compliance (does it do what was asked?), then code quality (is it well-written and secure?). Use after writing or modifying code.
Audits code for security vulnerabilities. Use on API routes, auth code, input handling, and database queries.
★not rated 2 4mo agoA26 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: