Produces requirements.md and design.md from an approved idea or feature request. Use for the WHAT and the HOW — user stories, EARS requirements, data models, API contracts, technical decisions with rationale, and the requirement→design traceability map. Never writes implementation code.
Implements one approved task from tasks.md — code plus tests — after checking that .status reads tasks:approved. Follows the spec exactly, stops on ambiguity instead of guessing, and reports verification evidence. Use for the EXEC phase, one task at a time.
Reviews an implementation against requirements.md, design.md, tasks.md, and the produced code in a fresh context. Reports coverage gaps and spec violations with verification evidence — not stylistic opinions. Use before treating a feature as done. Reviews only; does not implement fixes.
A read-only quality-audit agent that treats “finished” as something to test rather than assume. It checks a system through several independent lenses, including security, data quality, operations, performance, and error handling.
Routes individual planning questions to AUTORESOLVE or ESCALATE. Used when cm-planner surfaces multiple questions and the main agent needs to decide which require human ratification vs which can be auto-resolved with the recommended option. Read-only — produces routing verdicts, not implementations.
Architectural authority for all work in this repository. Invoked before responding to ANY user request. Plans scope, surfaces ratifications, names specialist agents needed for the change. Returns either an implementation prompt or STOPFORHUMAN for decisions only the user can make.
Audits decision documents under docs/decisions/ for convention compliance. Runs when decision docs touched OR sub-phase declared closed. Checks frontmatter, structure, length, content-sync between docs and metrics, override-block format. Returns ALL CLEAR, OVERRIDES PRESENT, or BLOCK CLOSURE.
A specialized sub-agent that performs security-focused reviews of the Blog API codebase. It looks for authentication gaps, injection vulnerabilities, data exposure, and insecure configs.
A code-review agent that checks changes against a project's design patterns, ADRs, and recommended practices. ADRs are short records explaining important architecture decisions.
An agent for operating a retrieval-augmented generation system, or RAG system, which lets an AI search stored information before answering. It manages indexing, collections, memory, and system health.
Expert in web accessibility, WCAG compliance, inclusive design, and assistive technology support. Use for accessibility audits, ARIA implementation, and inclusive UX. Triggers on accessibility, a11y, wcag, aria, screen reader, inclusive, disability, contrast.
Expert in AI/ML pipelines, LLM integration, RAG systems, embeddings, and intelligent automation. Use for building AI-powered features, prompt engineering, and model integration. Triggers on ai, ml, machine learning, llm, gpt, embeddings, rag, vector, chatbot, agent.
Expert in system design, architectural decisions, trade-off analysis, and technical strategy. Use for high-level design, ADRs, scalability planning, and technology evaluation. Triggers on architecture, system design, scalability, trade-off, ADR, design decision, tech stack, distributed system.
★not rated 1 5mo agoA60 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: