speckit-claude

Use this agent for any spec-kit lifecycle question or operation: which spec to claim next, whether a spec is ready to plan, what's blocking a feature, what's on the build-order page, and as the lead session for `/speckit-claim`, `/speckit-specify`, `/speckit-plan`, and `/speckit-tasks`. Knows the full pipeline (`/speckit-claim` → `/speckit-clarify` → `/speckit-checklist` → `/speckit-plan` → `/speckit-tasks` → `/speckit-analyze` → `/speckit-implement` → `/speckit-deploy`), the build-order scanner conventions, the NEW-NNN migration registry, the status ladder, branch-naming rules, pin blocks, and the constitution boundaries. Surfaces slash commands for the user to type rather than invoking them. <example> Context: The user wants to know what to work on next. user: "Which spec should I claim next?" assistant: "I'll use the speckit-workflow agent — it knows the build-order recommendation logic, the dependency graph, and the migration backlog." <commentary> Advisory mode: read build-order data, surface the recommended spec and the slash command to claim it. </commentary> </example> <example> Context: The user is mid-pipeline and forgot the next step. user: "I just finished /speckit-plan on F42. What's next?" assistant: "speckit-workflow agent — it tracks the pipeline order and the gating between phases." <commentary> Workflow advisory: surface the next slash command (`/speckit-checklist` or `/speckit-tasks`) for the user to type. </commentary> </example> <example> Context: A spec looks blocked. user: "What's blocking F30?" assistant: "speckit-workflow will resolve the dependency graph and check migration prerequisites." <commentary> Dependency resolution: read **Depends On**, check NEW-NNN migration status, report which prerequisites are unmet. </commentary> </example> <example> Context: The user typed /speckit-claim and the wrapper session is spawning a lead. user: "/speckit-claim 47" assistant: "The /speckit-claim wrapper spawns speckit-workflow as the lifecycle lead to run the claim end-to-end." <commentary> Lead mode: speckit-workflow is spawned by the /speckit-claim wrapper session via the Agent tool and follows the SKILL.md outline directly. </commentary> </example> <example> Context: The user wants a status snapshot. user: "Show me where we are on the migration backlog" assistant: "speckit-workflow knows the NEW-NNN registry shape and surfaces the right command." <commentary> The agent surfaces `/migration-backlog` for the user to type — it does not invoke the skill itself. </commentary> </example>

Show the recommended next feature to build based on specs/ directory and dependency graph. Scans every feature spec, derives build status from tasks.md completion, and recommends the lowest-numbered spec with all dependencies satisfied.

Monitor CI/CD deployment, check Copilot review notes, evaluate findings, and offer to fix. Run after merging a PR.

Show the migration backlog status — what NEW-NNN entries are built, deferred, retracted, or planned, plus next-actionable items. Reads scripts/lib/migration-backlog-data.ts, the machine-readable registry that mirrors the §13 inventory tables in the architecture spec.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Generate a custom checklist for the current feature based on user requirements.

2 hooks across 2 events