chrishobbsrocks

Sprint Complete — Testing skill for Claude Code

Testing community

Dev Team: close a sprint once both QA gates have passed AND the user explicitly authorizes closing it.

How to install Sprint Complete

Installs to ~/.claude/commands/chrishobbsrocks-fully-completely-sprint-complete.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/chrishobbsrocks/fully-completely/HEAD/.claude/commands/sprint-complete.md -o ~/.claude/commands/chrishobbsrocks-fully-completely-sprint-complete.md

Restart Claude Code, or start a new session, for it to be picked up.

What Sprint Complete does

description: "Dev Team: close a sprint once both QA gates have passed AND the user explicitly authorizes closing it" allowed-tools: [Bash, Write]

Complete Sprint

Usage: `/sprint-complete --user-said "..."`

**Security note**: do not interpolate `$ARGUMENTS` (or any free-text `--user-said` value) directly into the bash command below, quotes or shell metacharacters in what the user said can break out and run unintended commands. Parse the sprint ID yourself (a safe, low-ent

Alternatives in Testing

Claude Code Spec Workflow — Automated Kiro-style Spec workflow for Claude Code 3.6k ★
Cc Sdd — Spec-driven development (SDD) for your team's workflow 3.1k ★
Spawn Fs Team — Boot a 5-agent full-stack Flotion team as a new workspace in the cmux window (reuse the open window; only crea 107 ★