Skip to content

ash1794/vibe-engineering / plugins/vibe-engineering/skills/vibe-iteration-review

vibe-iteration-review

Verified

Performs end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.

vibe-iteration-review

What gets measured gets improved. Review every iteration.

When to Use This Skill

  • End of a development sprint or iteration
  • After completing a milestone
  • Before starting the next iteration (retrospective)
  • When the user asks "how did we do?"

When NOT to Use This Skill

  • Mid-iteration (too early, incomplete data)
  • After single small tasks
  • When there's no defined iteration boundary

Steps

  1. Gather data:

    • What was planned for this iteration?
    • What was actually delivered?
    • How many commits? Lines changed? Tests added?
    • Coverage delta? Quality metrics?
    • Known issues introduced?
  2. Grade quality (A-F):

    • A: All planned work delivered, tests pass, no known issues, clean code
    • B: Most work delivered, minor issues, good test coverage
    • C: Core work delivered, some gaps, acceptable quality
    • D: Significant gaps, quality issues, needs rework
    • F: Iteration failed, major rework needed
  3. Compare to previous iterations (if available):

    • Is quality trending up or down?
    • Is velocity improving?
    • Are known issues accumulating?
  4. Extract lessons:

    • What went well?
    • What went poorly?
    • What to change next iteration?

Output Format

Iteration Review: [Iteration Name/Number]

Quality Grade: A/B/C/D/F Planned vs Delivered: X/Y (Z%)

MetricThis IterationPreviousTrend
CommitsXY↑/↓/→
Tests addedXY↑/↓/→
CoverageX%Y%↑/↓/→
Known issuesXY↑/↓/→

Delivered

  • [Task 1]
  • [Task 2]
  • [Task 3] — deferred because [reason]

Lessons Learned

  1. [What to continue]
  2. [What to change]
  3. [What to stop]
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall