st

Generate API documentation: OpenAPI spec, Postman Collection, and/or Markdown docs from codebase

Brainstorm ideas: explore vague concepts, 2-round research, produce actionable spec

Code review: linting + 1 reviewer agent (13 domains), confidence-scored report, auto-fix

Quick debug: fast fix for simple bugs in main context, auto-escalates to /st:debug if complex

Systematic debugging: persistent state, knowledge base, 12 techniques, anti-shortcut discipline

Analyzes codebase structure and produces structured analysis documents. Spawned by /st:init with a specific focus area (tech, arch, quality, concerns). <example> Context: User runs /st:init on a brownfield project user: "/st:init" assistant: "Brownfield project detected. Spawning codebase-mapper agents to analyze the existing codebase." [mapper receives focus=tech] assistant: "MAPPING COMPLETE — .superteam/mapping/TECH.md" </example>

Investigates bugs using scientific method with persistent session state and knowledge base. Spawned by /st:debug command. <example> Context: User encounters a failing test they can't figure out user: "/st:debug test_auth_flow is failing intermittently" assistant: "Spawning debugger agent to investigate" </example>

Standard implementation specialist. Executes tasks following plans, writes clean code, self-verifies acceptance criteria. Member of /st:team. <example> Context: Scrum Master assigns a task scrum-master: "Task #2: Add theme toggle to settings page. Files: settings.tsx" developer: "Reading settings.tsx, implementing toggle component..." </example>

CI/CD and infrastructure specialist. Handles pipeline configuration, deployment, containerization. Optional role — activated when CI/CD config detected. Member of /st:team. <example> Context: Scrum Master assigns CI/CD task scrum-master: "Task #5: Update GitHub Actions workflow for new feature tests." devops-engineer: "Reading current workflow, adding test step..." </example>

Executes implementation plans with atomic commits, wave-based parallelism, and deviation handling. Spawned by /st:execute and /st:phase-execute commands. <example> Context: A plan has been created and approved for adding dark mode user: "/st:execute" assistant: "Spawning executor agent to implement the plan" </example>

Use when writing code that will be committed. Enforces task-atomic commit granularity, conventional message format, independent revertability, and parallel-safe git operations. Auto-triggered by execute, quick, tdd, phase-execute.

Use when executing any command or agent task. Cross-cutting principles for all Superteam work. Auto-triggered by all commands and agents. Covers: visual-first (design decisions, verification, comparisons, any visual content), UI screenshots, Playwright, browser preview, HTML preview, questioning, one question per message, adaptive, ASK/PRESENT/CONFIRM, recommendation, decision continuity, confirmed decisions, DECISIONS block, never re-ask confirmed.

Use when making design judgments for UI/UX work — auditing, specifying, reviewing, or building frontend interfaces. Covers accessibility, touch targets, typography, color, layout, spacing, animation, forms, navigation, design tokens, and AI slop detection. Reference for agents needing concrete design rules with specific values. Keywords: WCAG, contrast ratio, touch target, font pairing, color palette, responsive breakpoints, design tokens, CSS variables, animation timing, spacing scale, AI slop, anti-patterns.

Use when pausing work mid-session or resuming from a previous session. Defines HANDOFF.json/HANDOFF.md schemas, capture/restore protocols, context quality standards, and one-shot lifecycle rules.

Use when creating any implementation plan (task or phase). Enforces goal-backward plan design, quality gates before execution, anti-vagueness rules, and plan-checker agent verification loop.

1 hook across 1 event