sprint-endlisted

______________________________________________________________________ ## sprint-end **Skill metrics:** Emit a start event to the activity log: ```bash echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"sprint-end\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl ``` Ending the sprint. Discovering and wrapping up all work on the current branch. ## Profile-Adaptive Behavior Read the `**Profile:**` line from CLAUDE.md to determine the active project profile. <IF condition="Profile is lean"> **Lean mode:** Simplified flow: 1. Discover sprint state 2. Run tests (HARD GATE: must pass) — skip quality agent dispatch 3. Commit any pending changes 4. Push and create PR (simplified PR body — summary of changes, test results, files changed) 5. Wait for CI (if configured) 6. Merge and clean up Skip: Step 2 quality agent dispatch, Step 3 documentation updates (epics, backlog, metrics, context, architecture, PRD review, debt register), ground rules compliance check, ADR compliance check. Tests must still pass — safety is not reduced. </IF> <IF condition="Profile is strict"> **Strict mode:** All quality gates mandatory — skip the selection AskUserQuestion and run `/quality-check --all` automatically. PR body MUST include an Audit Trail section: files changed, agents run with verdicts, gates passed/failed, coverage delta. Ground rules compliance and ADR compliance checks are mandatory (if files don't exist, flag as a gap). On sprint completion,