Skip to content
Back to skills

Enhancements

ASecurity

Add an interactive `/ll:review-sprint` skill that uses Claude's intelligence to analyze a sprint and suggest improvements — reordering waves for efficiency, swapping issues based on priority changes, recommending issues to remove or add from the backlog, and resolving dependency conflicts. This goes beyond the deterministic edits in `ll-sprint edit` (ENH-393) by providing opinionated, context-aware recommendations.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsgodocumentation

Works with

  • cli

Security analysis

A100/100

Pro scans all 21 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add BrennonTWilliams/little-loops --skill enhancements --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Enhancements?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Enhancements
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brennontwilliams-enhancements-9384caa7/badge)](https://www.skillsdirectory.com/skills/brennontwilliams-enhancements-9384caa7)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
discovered_date: 2026-02-12
discovered_by: manual
status: done
completed_at: 2026-02-13T00:00:00Z
priority: P4
---

# ENH-394: Add `/ll:review-sprint` skill for AI-guided sprint health checks

## Summary

Add an interactive `/ll:review-sprint` skill that uses Claude's intelligence to analyze a sprint and suggest improvements — reordering waves for efficiency, swapping issues based on priority changes, recommending issues to remove or add from the backlog, and resolving dependency conflicts. This goes beyond the deterministic edits in `ll-sprint edit` (ENH-393) by providing opinionated, context-aware recommendations.

## Current Behavior

Sprint review is limited to:
- `ll-sprint show` — displays structure and warnings but offers no suggestions
- `ll-sprint edit` (ENH-393) — deterministic add/remove/prune operations
- No tool suggests *what* to change, only allows the user to make changes they've already decided on

## Expected Behavior

A `/ll:review-sprint` skill that:
- Loads a sprint and analyzes its current health (invalid refs, completed issues, dependency warnings)
- Suggests wave reordering based on updated dependency analysis and file contention
- Recommends removing issues that are completed, blocked, or low-value relative to the sprint goal
- Recommends adding related issues from the backlog that align with the sprint's theme/description
- Proposes swapping issues when priorities have shifted since sprint creation
- Uses `AskUserQuestion` to present recommendations and let the user accept/reject each suggestion
- Applies accepted changes via `ll-sprint edit` CLI flags or direct YAML updates

## Motivation

After a sprint sits for a while, the backlog evolves — issues get completed, priorities shift, new related issues appear. A user needs AI-assisted judgment to review whether the sprint still makes sense, not just mechanical validation. This pairs with `ll-sprint edit` (ENH-393) the way `/ll:create-sprint` pairs with `ll-sprint create` — the CLI handles the mechanics, the skill handles the intelligence.

## Proposed Solution

Create a new skill in `skills/review_sprint.md` that:
1. Reads the sprint YAML and loads all referenced issues
2. Runs validation (reusing `SprintManager.validate_issues()`)
3. Loads the backlog to find related issues not in the sprint
4. Analyzes the sprint against its description/goal for coherence
5. Presents findings and recommendations via `AskUserQuestion`
6. Applies accepted changes

## Scope Boundaries

- Out of scope: Deterministic edit operations (covered by ENH-393)
- Out of scope: Sprint execution logic changes
- Out of scope: Automatic sprint modification without user approval

## Dependencies

- **ENH-393**: `ll-sprint edit` CLI subcommand — this skill should apply changes through the edit CLI or share the same underlying operations

## Implementation Steps

1. Create `skills/review_sprint.md` (or `commands/review_sprint.md`) skill definition
2. Define the review analysis logic: health check, wave optimization, backlog scanning
3. Implement recommendation presentation via `AskUserQuestion` with accept/reject per suggestion
4. Wire accepted changes to sprint YAML updates (via `ll-sprint edit` or direct `SprintManager` calls)
5. Add sprint description/goal coherence analysis

## Impact

- **Priority**: P4 - Nice-to-have, manual review is always possible
- **Effort**: Medium - Skill definition + analysis logic + interactive flow
- **Risk**: Low - Additive, read-only analysis with opt-in changes
- **Breaking Change**: No

## Success Metrics

- Skill identifies stale/misaligned issues that the user would otherwise miss
- Backlog recommendations surface relevant issues the user hadn't considered
- Users report sprint quality improves after review

## Related Key Documentation

| Category | Document | Relevance |
|----------|----------|-----------|
| architecture | docs/ARCHITECTURE.md | Sprint system architecture |
| guidelines | .claude/CLAUDE.md | Prefer Skills over Agents guidance |
| related | .issues/completed/P4-ENH-393-sprint-review-edit-command.md | CLI edit counterpart (completed) |
| implementation | commands/create_sprint.md | Existing interactive sprint skill pattern |

## Labels

`enhancement`, `sprint`, `skill`, `captured`

---

## Resolution

- **Action**: implement
- **Completed**: 2026-02-12
- **Status**: Completed

### Changes Made
- `skills/review-sprint/SKILL.md`: Created new skill with 6-phase workflow (health check, backlog scan, analysis, recommendations, interactive approval, apply changes)

### Verification Results
- Tests: PASS (2711 passed)
- Lint: PASS
- Types: PASS

## Session Log
- `/ll:manage-issue` - 2026-02-12T00:00:00Z

---

## Status

**Completed** | Created: 2026-02-12 | Completed: 2026-02-12 | Priority: P4

Files in this skill

  • P0-ENH-206-improve-cli-py-test-coverage.md4.3 KB
  • P0-ENH-207-improve-issue-manager-py-test-coverage.md3.2 KB
  • P0-ENH-321-add-integration-map-to-issue-template.md11 KB
  • P1-ENH-056-ll-loop-end-to-end-execution-test.md3.7 KB
  • P1-ENH-057-ll-loop-successful-resume-test.md2.4 KB
  • P1-ENH-129-fsm-validation-test-coverage.md3 KB
  • P1-ENH-130-git-lock-test-coverage.md3 KB
  • P1-ENH-1547-enhance-review-loop-with-harness-design-best-practices.md17.8 KB
  • P1-ENH-190-hooks-system-robustness-improvements.md14.6 KB
  • P1-ENH-191-distinguish-transient-vs-real-failures-in-automation.md10.9 KB
  • P1-ENH-208-improve-merge-coordinator-py-test-coverage.md3.7 KB
  • P1-ENH-209-improve-orchestrator-py-test-coverage.md2.7 KB
  • P1-ENH-2814-make-failure-terminals-observable-end-to-end.md28.2 KB
  • P1-ENH-2939-delete-session-log-hunting-prose.md13.8 KB
  • P1-ENH-2941-ll-issues-find-similar-similarity-foundation.md36.7 KB
  • P1-ENH-2950-ll-issues-locate-options-json.md15.8 KB
  • P1-ENH-2951-verify-skill-prose-algorithm-lint.md18.9 KB
  • P1-ENH-320-optimize-issue-template-v2.md8.3 KB
  • P1-ENH-3397-distinguish-repetition-infrastructure-retry-and-continuation-in-ll-harness.md45.6 KB
  • P1-ENH-3406-harness-run-model-schema-migration.md35.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…