sdlc-review

Verifies Kanban implementation handoffs and routes review verdicts to completion, rework, or escalation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work handed off from a Kanban implementation lane to a review lane needs an independent verdict before it can be completed, but rubber-stamping handoff summaries or letting reviewers edit the deliverable weakens quality control. This Skill enforces an independent, evidence-based review process with clear terminal outcomes. ## Core Features & Use Cases - Independent Verification: Reads the task record via kanban_show, inspects the actual deliverable, and runs focused tests, lint, or builds before deciding. - Structured Verdicts: Routes each review to exactly one outcome — approve with kanban_complete, request changes with kanban_request_changes, or escalate with kanban_block. - Round-Based Review Lenses: Varies inspection strategy per round (artifact cold-read, execution-based verification, contract audit) to catch different defect classes across re-reviews. - Use Case: A dispatcher spawns a reviewer for a task in the review lane after an implementer submits a review_requested handoff; the reviewer checks out the code, runs the project's tests, maps every acceptance criterion to evidence, and either approves with documented checks or returns actionable findings to the implementer. ## 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 recording an approve, request-changes, or escalate verdict.

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 in the review lane?▼

Start with kanban_show to read the task specification, acceptance criteria, and latest review_requested handoff. Then inspect the actual deliverable, run relevant verification, and record exactly one verdict: approve, request changes, or escalate.

How to request changes on a Kanban implementation handoff?▼

First call kanban_comment with actionable findings stating the defect location, reproduction, and required correction. Then call kanban_request_changes with a concise reason, which returns the task to its original implementer for rework.

When should a reviewer escalate instead of requesting changes?▼

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

Can a reviewer edit the implementation during code review?▼

No. The reviewer must preserve role separation and never edit the deliverable. Instead, request changes and let the implementer produce the next candidate, then independently verify that candidate in the next review run.

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

The round is the count of prior changes_requested entries plus one. Round 1 uses a cold artifact read, round 2 uses execution-based verification via terminal, and round 3 or later audits strictly against the original contract and prior requested changes.