Menú
Re-generate Squad agent definitions as your spec evolves
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Wrap core analysis with behavior-first vertical consistency checks.
Apply approved architecture refactors by updating plan and task artifacts directly.
Perform a framework-agnostic architecture review validating implementation against spec.md, plan.md, tasks.md, and the governance and architecture constitutions.
Perform an architecture-aware verification gate validating implementation against spec.md, plan.md, tasks.md, and the Architecture Constitution.
Run a single architecture workflow that prefers memory-first context and can incorporate security review when available.
Run implementation with memory context, then review the produced implementation against security and architecture constraints.
| name | speckit-squad-generate |
| description | Re-generate Squad agent definitions as your spec evolves |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"squad:commands/generate.md"} |
Re-read the current spec and regenerate Squad agent definitions, capabilities, and routing rules to stay in sync with spec changes. Safe to run repeatedly — existing agents are updated in place; agents no longer supported by the spec are flagged (not deleted).
This command is also triggered by the after_specify hook.
$ARGUMENTS
Verify .squad/ exists — if not, tell the user to run
/speckit.squad.init first and stop.
Read the spec from the active spec directory under specs/ (e.g.,
specs/001-<name>/spec.md).
Load bridge config from .specify/extensions/squad/squad-config.yml
if it exists, otherwise use extension defaults.
Read existing agents from .squad/agents/ (each agent lives in
.squad/agents/{name}/charter.md) so changes can be diffed rather than
blindly overwritten.
Analyze the spec to extract technology domains, architectural concerns,
and cross-cutting roles (same logic as init). If $ARGUMENTS names a
specific domain, limit regeneration to that domain's agent.
Diff against existing agents:
status: inactive and note in output (do NOT delete)Update squad.config.ts at the project root (using defineSquad() with
defineTeam(), defineAgent(), and defineRouting()) to reflect the new
agent set, routing rules, and model tier assignments.
Update .squad/routing.md to add routing rules for any new agents and
update patterns for changed agents.
Print a diff summary:
Squad agents updated
✅ Added : data-engineer (PostgreSQL/migrations — proficient)
✏️ Updated : backend-engineer (added GraphQL capability)
⚠️ Inactive: mobile-engineer (no longer in spec — set to inactive)
Routing rules updated: 8 total (2 added, 1 modified)
inactive agents remain in .squad/ and can be reactivated manually with
squad commands if needed.