sdlc-review

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

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/harlanljones/dotfiles --skill sdlc-review-harlanljones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-review
Source: https://github.com/harlanljones/dotfiles/tree/main/dot_hermes/skills/devops/sdlc-review
Command: npx skills add https://github.com/harlanljones/dotfiles --skill sdlc-review-harlanljones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work moves from a Kanban implementation lane to a review lane, someone must independently verify the deliverable against the original acceptance criteria instead of trusting the implementer's handoff summary. This Skill provides a structured review procedure that produces a single evidence-backed verdict. ## Core Features & Use Cases - Independent Verification: Reads the task record with kanban_show, inspects the actual deliverable, and runs builds, tests, and lint checks before deciding. - Round-Based Review Lenses: Applies a different inspection lens per review round (artifact read, execution, contract audit) so repeated reviews catch different defect classes. - Three Terminal Verdicts: Approves with kanban_complete, returns correctable defects with kanban_request_changes, or escalates human decisions with kanban_block. - Use Case: An implementer marks a bug-fix task as review_requested; the reviewer checks out the branch, runs the failing test path, confirms the fix, and completes the task with a summary naming the exact checks performed. ## Quick Start Ask the agent to 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 by calling 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 record exactly one verdict: approve, request changes, or escalate.

How do I request changes on a Kanban implementation task?▼

First post a kanban_comment listing each defect with its 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 resolution requires a human decision or an external prerequisite that neither reviewer nor implementer can provide. Correctable implementation defects should always go through kanban_request_changes instead.

What is the difference between review rounds in Kanban re-review?▼

The round number equals the count of prior changes_requested entries plus one. Round 1 leads with a cold artifact read, round 2 leads with executing the work, and round 3 or later audits strictly against the original contract and prior requested corrections.

Can a reviewer edit the implementation during Kanban review?▼

No. The reviewer must preserve role separation and never edit the deliverable. Defects are returned to the implementer via kanban_request_changes, and the reviewer independently verifies the next candidate in a later review run.