xp-agents

Review the completed sprint. Compares what shipped vs planned, updates execution_plan.json milestones with delivered status, and records sprint velocity. Use when all stories are done or deferred.

Create sprint.json from an execution plan milestone or product spec. Decomposes milestones into context-rich stories with file domains, interface contracts, and inlined design context. Deep codebase dive identifies story boundaries. Customer confirms scope before writing.

The universal per-story execution-shape decision. Reads the session default tier and the plan-reviewer's per-story recommendation, then applies a behavior table: it may exit in-agent (no spawn — continue in the existing checkout) or spawn exactly ONE teammate at the chosen tier (the story's executor_model forwarded to spawn_teammate's --model flag). Valid for solo and parallel frontiers alike. Runs once per story after that story's plan is reviewed.

Push the sprint branch, fork xp-close-reviewer for cross-cutting review, and merge into the target with cleanup. Auto-invoked at the end of /xp-sprint-review; degrades gracefully when gh is unavailable.

Verify acceptance criteria for in-progress stories. Present criteria, guide e2e test execution, mark stories done or deferred, update sprint.json.

This skill should be used when the user needs to select work for the session, review retro Try items, triage open questions, or pick sprint stories. Invoked as part of /xp-kickoff or standalone via /xp-work-selection.

Review the current plan mode plan. Checks plan size, TDD ordering, milestone boundaries, and decision conflicts. Use after planning completes.

Independent review of the current diff. Spawns an xp-code-reviewer subagent that self-finds correctness (per-increment) or validates & fixes /code-review's findings (close path, MODE=consume-findings), plus drift, debt, and reuse/quality/efficiency + XP-lens review. Resolves plan concerns inline.

Per-story close: review the story diff, merge into the sprint base, and clean up. Invoked by /xp-accept on each accepted story; the next-frontier promotion (via /xp-schedule) and the sprint-review dispatch are owned by /xp-accept after its loop completes — single source of truth lives there.

Push the current free branch, fork xp-close-reviewer for free-mode review, and merge into the target integration branch (recorded plan branch when set and present locally, else primary) with cleanup. Used for ad-hoc work performed outside a sprint or plan; degrades gracefully when gh is unavailable.

User-invoked end-of-session cleanup. Drafts a session_summary event, force-closes/defers open questions, bulk-drops maybe-addressed concerns and debts, and prints an honesty-signal count of SMM events not yet linked to a commit.

Create or update execution_plan.json — collaborative planning that transforms external design sources into ordered development milestones with change zones, impact zones, and design details. Replaces /xp-product-spec for sprint-mode work. Use when starting a new change request or refining an existing plan.

Push the plan branch, fork xp-close-reviewer for plan-level review, and merge into the primary branch with archive. Auto-invoked by /xp-sprint-close after the last milestone of a plan-branch plan ships; degrades gracefully when gh is unavailable.

Decide the next execution unit per ready frontier: auto-solo on a single frontier or one that cannot run concurrently (overlapping domains or a dependency edge), ask solo/parallel on >=2 stories that form a disjoint antichain, then promote the chosen scheduled stories to in-progress and set each story's execution_mode. Runs before planning so the mode choice sets the planning scope. Solo also creates+checks out the branch; parallel leaves branches to /xp-assign.

Session start orchestrator. Sequences retrospective, sprint setup, work selection, and housekeeping. Use at the start of every session.

Scaffold an acceptance test harness for a project surface. Triggers on /xp-scaffold-acceptance. Inline skill that detects active teammates and existing tooling, asks the customer to pick a surface and tool (with monorepo path placement when relevant), web-refreshes the tool's latest version, plans + previews the scaffold for explicit yes/show-files/no confirmation, then atomically writes + installs + verifies + commits and flips the system_context surface to covered. Re-running on a scaffolded repo offers add-complementary / redo-via-revert / cancel. Refuses to run while teammate worktrees are live.

Stage 2 floor migration prompt for /xp-kickoff Step 0. Reads dismissal, prompts customer to set the Stage 2 floor or records a dismissal. INTERNAL — invoked only by xp-kickoff when stage < 2.

Create or update system_context.json — autonomous codebase analysis that produces a thorough system description. Reads project structure, CLAUDE.md, and key source files to synthesize product overview, architecture, and technical constraints. Use standalone or invoked by /xp-plan.