sdlc-review

Verifies Kanban implementation handoffs and routes approve, request-changes, or escalate verdicts.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill sdlc-review-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-review
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/devops/sdlc-review
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill sdlc-review-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work handed off from a Kanban implementation lane needs independent verification before completion, and rubber-stamping handoff summaries lets defects slip through. This Skill gives a reviewer agent a structured procedure to verify deliverables against acceptance criteria and record an evidence-backed verdict. ## Core Features & Use Cases - Independent verdict routing: Approve via kanban_complete, request changes via kanban_request_changes, or escalate via kanban_block, each with concrete recorded evidence. - Round-based review lenses: Rotate between artifact, execution, and contract lenses across review rounds so each re-review catches different defect classes instead of repeating the same inspection. - Role separation enforcement: The reviewer never edits the implementation; corrections go back to the original implementer, and reviewer provenance routes re-reviews to the same reviewer. - Use Case: An implementer marks a bug-fix task review_requested. The reviewer reads the task with kanban_show, checks out the diff, runs the project's tests, finds one acceptance criterion unmet, and files actionable findings before returning the task for rework. ## Quick Start Review the current Kanban task in the review lane by reading its handoff with kanban_show, verifying the deliverable against the acceptance criteria, and submitting an approve, request-changes, or escalate verdict with evidence.

Frequently Asked Questions about sdlc-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Kanban task handoff before approving it?▼

Start with kanban_show to read the task specification, acceptance criteria, and latest review_requested handoff. Then inspect the actual deliverable, run relevant tests or builds, and map every acceptance criterion to concrete evidence before choosing a verdict.

What verdicts can a reviewer give on a Kanban review task?▼

Exactly one of three terminal actions: approve with kanban_complete when criteria pass, request changes with kanban_comment plus kanban_request_changes for correctable defects, or escalate with kanban_block when a human decision or external prerequisite is required.

How does the review lens change across re-review rounds?▼

Round 1 uses an artifact lens reading the diff cold, round 2 uses an execution lens running the work via terminal, and round 3 onward uses a contract lens auditing strictly against the original acceptance criteria and prior requested changes.

When should I escalate instead of requesting changes on a review?▼

Escalate with kanban_block only when the reviewer and implementer cannot resolve the problem without a human decision or external prerequisite. Correctable implementation defects belong in kanban_request_changes, not blockers.

Can the reviewer fix defects directly in the deliverable?▼

No. The reviewer must preserve role separation and never edit implementation files. Defects are documented as actionable findings and returned to the original implementer, whose next candidate is independently verified in the following review round.