retro

/retro — Feature Retrospective

Arguments

• $ARGUMENTS — Optional: story ID (e.g., "US-001") or branch name. If omitted, analyzes the current branch.

Instructions

You are generating a retrospective report for a completed feature. Your job is to analyze git history and project artifacts to surface patterns, measure delivery quality, and suggest workflow improvements.

Input: $ARGUMENTS

Step 1: Gather Data

Git History

# All commits on the feature branch
git log main..HEAD --oneline --format="%h %s"

# Commits per phase (by scope in commit message)
git log main..HEAD --oneline --grep="(ui):" --grep="(api-client):" --grep="(smart-components):" --grep="(repository):" --grep="(service):" --grep="(controller):" --grep="(integration):"

# Files changed per commit
git log main..HEAD --stat --format="%h %s"

# Total diff stats
git diff main..HEAD --stat

Project Artifacts

• Read .phase-context.json for the story ID and completed phases
• Read the plan at docs/plans/PLAN-{story-ID}.md for planned vs. actual deliverables
• Read the user story at docs/stories/{story-ID}.md for BDD scenarios

Step 2: Analyze Phase Delivery

For each phase (1–7), report:

Metric	How to Measure
Commits	Count commits matching the phase scope
Files created	Count new files in that phase's commit(s)
Files modified	Count files changed after initial commit (rework)
Test count	Count it() or test() calls in test files

Flag phases with high rework (multiple commits modifying the same files), which indicates the phase wasn't completed cleanly on the first pass.

Step 3: Identify Patterns

Analyze the git history for these patterns:

Iteration Patterns

• Single-pass phases — completed in one commit (ideal)
• Multi-commit phases — required fixes after initial implementation
• Fix-after-validate — commits that follow a validation failure

Common Issues

Look for these in commit messages and diffs:

• Type errors fixed after implementation
• Test failures fixed after writing
• Lint fixes as separate commits
• Import/export issues between shared types and consumers