squad

Plugin squad from marketplace build-squad in sturlese/build-squad. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• breaking-change

  Apply when a task changes a public API, endpoint signature or response shape, database schema, serialized or persisted format, event/message contract, or any interface other code or systems consume. Enforces closing the transition safely — consumer inventory, compatibility decision (compatible exten

• define

  Conversational spec mode — the main session interviews the user, round by round, until the product definition closes; then writes a spec file with verifiable acceptance criteria, ready for /squad:build. Use when the user wants to define, spec, or shape a feature or product, or when a request is too

• final-validation

  Use before delivering ANY code change to choose and run final validation — the smallest set of build/test/lint targets that covers the real risk of the change, run at the end (not after every tiny edit), never running test commands in parallel, and reporting targets executed, results, and selection

• fix

  Bug-fix pipeline, reproduce-first — the tester captures the bug as a failing test BEFORE the developer may touch production code, then verifies the fix and scans for sibling occurrences of the same defect. Accepts an informal report or a screenshot and clarifies interactively in the main session fir

• refactor

  Behavior-preserving restructuring — the existing tests become the frozen invariant that must pass identically before and after, the developer restructures without touching them, and the auditor judges whether the new structure is actually better. Use when the user wants to refactor, restructure, ext

• review

  Read-only team review of a diff, branch, or PR — the auditor (security, structure), tester (contract protection, coverage gaps), and ux (only if user-facing surfaces change) review in parallel; findings are merged, deduplicated, severity-ranked, and delivered with a verdict. Nothing is modified. Use

• semantic-architecture

  Apply when a task involves active/inactive states, archiving, visibility or lifecycle; lists reused between management and operational contexts; shared selectors (comboboxes, pickers, multi-selects); different rules for "can be viewed" vs "can be used"; write-path validations that depend on state; o

Subagents (5)

• auditor

  Security and architecture auditor — read-only review of a diff or system; OWASP-style security checklist, structural quality, duplication, asymmetric patterns; findings with severity and precise fix instructions for the developer. Use after implementation, or standalone for audits. Modifies nothing.

• developer

  Senior full-stack developer — implements a defined, bounded task following existing project conventions, reusing existing code, and validating with the smallest sufficient set of build/test/lint targets. Use AFTER scope and acceptance criteria are defined (via /squad:define or by the user).

• documentator

  Documentation architect — creates and maintains the living map of the system (per-directory index.md files, READMEs, system-overview docs); what each module is for, what to reuse, what to avoid. Never implements code and never runs build/tests/lint. Use at the end of substantial changes or to bootst

• tester

  QA tester — protects the functional contract; writes and repairs tests, runs the smallest sufficient test targets (never in parallel), and diagnoses failures as regression vs test defect. NEVER touches production code. Use after implementation, or standalone for coverage and flaky-test work.

• ux

  UX and usability expert — evaluates flows, copy, feedback, empty/loading/error states, accessibility, and cross-flow consistency from the real end-user's perspective; proposes concrete improvements. Writes documentation only, never code. Use after a spec is defined for user-facing features, or stand

Hooks (1)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guard.py"

Similar plugins