Skip to content
cccskills
FreePublished on GitHub

vibe-iteration-review

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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]

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.

The English summary is being prepared. Showing the original description.

ash1794/vibe-engineering165Updated Oct 8, 2026

See all skills by ash1794

Report a problem with this skill