Agent Claude Code
Synthesizes classified planning docs into a single consolidated context. Applies precedence rules, detects cross-ref cycles, enforces LOCKED-vs-LOCKED hard-blocks, and writes INGEST-CONFLICTS.md with three buckets (auto-resolved, competing-variants, unresolved-blockers). Spawned by /gsd:ingest-docs.
Agent Claude Code
Verifies factual claims in generated docs against the live codebase. Returns structured JSON per doc.
Agent Claude Code
Writes and updates project documentation. Spawned with a docassignment block specifying doc type, mode (create/update/supplement), and project context.
Agent Claude Code
Researches the business domain and real-world application context of the AI system being built. Surfaces domain expert evaluation criteria, industry-specific failure modes, regulatory context, and what "good" looks like for practitioners in this field — before the eval-planner turns it into measurable rubrics. Spawned…
Agent Claude Code
Retroactive audit of an implemented AI phase's evaluation coverage. Checks implementation against the AI-SPEC.md evaluation plan. Scores each eval dimension as COVERED/PARTIAL/MISSING. Produces a scored EVAL-REVIEW.md with findings, gaps, and remediation guidance. Spawned by /gsd:eval-review orchestrator.
Agent Claude Code
Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd:ai-integration-phase…
Agent Claude Code
Presents an interactive decision matrix to surface the right AI/LLM framework for the user's specific use case. Produces a scored recommendation with rationale. Spawned by /gsd:ai-integration-phase and /gsd-select-framework orchestrators.
Agent Claude Code
Analyzes codebase and writes structured intel files to .planning/intel/.
Agent Claude Code needs its repo
Analyzes codebase for existing patterns and produces PATTERNS.md mapping new files to closest analogs. Read-only codebase analysis spawned by /gsd:plan-phase orchestrator before planning.
Agent Claude Code
Verifies threat mitigations from PLAN.md threat model exist in implemented code. Produces SECURITY.md. Spawned by /gsd:secure-phase.
Agent Claude Code
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
Agent Claude Code
Validates UI-SPEC.md design contracts against 6 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.
Agent Claude Code
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
Agent Claude Code
Analyzes extracted session messages across 8 behavioral dimensions to produce a scored developer profile with confidence levels and evidence. Spawned by profile orchestration workflows.
Command Claude Code
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Command Claude Code
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
Command Claude Code
Cross-phase audit of all outstanding UAT and verification items.
Command Claude Code
Run all remaining phases autonomously — discuss→plan→execute per phase.
Command Claude Code
Capture ideas, tasks, notes, and seeds to their destination.
Command Claude Code
Review source files changed during a phase for bugs, security issues, and code quality problems.
Command Claude Code
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile.
Command Claude Code
Generate or update project documentation verified against the codebase.
Command Claude Code
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
Command Claude Code
Socratic ideation and idea routing — think through ideas before committing to plans.
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: