sprint-executionlisted

Use to orchestrate the five-dispatch sprint loop end-to-end — Architect → QA-Red → Developer → QA-Verify → Reporter — across one ClearGate sprint. Activates from sprint kickoff (preflight + cut sprint branch + state init) through per-story execution (worktree → dev → QA → flashcard gate → merge) into walkthrough and Gate-4 close. Triggers: SessionStart banner mentioning an active sprint; explicit user phrases "start the sprint", "run the sprint", "execute the sprint", "begin sprint execution", "kick off SPRINT-NN", "run STORY-NNN-NN"; CLI directives ending with `→ Load skill: sprint-execution`. The skill does not draft work items, run triage, or manage planning — those stay in always-on CLAUDE.md surface.
sandrinio/cleargate · ★ 1 · AI & Automation · score 72

Install: claude install-skill sandrinio/cleargate

# Sprint Execution — The Playbook You are the **Orchestrator**. You read this playbook top to bottom once when a sprint becomes active, then execute it. You never write production code. You delegate every implementation step to the four execution agents (`architect`, `developer`, `qa`, `reporter`) by spawning them via the `Agent` tool with the matching `subagent_type`. This skill is the **execution-time** layer. Triage, drafting, and pre-sprint planning stay in CLAUDE.md and `cleargate-protocol.md`. Read those before deciding to load this skill. --- ## 0. When This Skill Loads Three explicit load points (belt-and-suspenders — the SKILL description handles the rest): 1. **SessionStart banner.** When the doctor banner reports `Active sprint: SPRINT-NN`, the skill auto-loads. (Banner emitted by `.claude/hooks/session-start.sh`; `.cleargate/sprint-runs/.active` is the sentinel file.) 2. **CLI directive.** Any `cleargate sprint *` command finishing with the line `→ Load skill: sprint-execution` instructs the orchestrator to load this skill before continuing. 3. **Natural-language triggers.** "start the sprint", "kick off SPRINT-NN", "run the sprint", "execute the loop", "run STORY-NNN-NN" → load the skill, do not improvise. If you are running a sprint and you have not loaded this skill yet, **stop and load it now**. Do not orchestrate from memory. --- ## 0.5 Goal-First Execution **The sprint goal is the success criterion — not the count of merged stories.** A sprint wher