sdlc-review

Review Kanban handoffs and route verified outcomes to approval, changes, or escalation.

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

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 with kanban_complete, request changes with kanban_request_changes, or escalate with kanban_block, each with concrete evidence recorded in the transition. - Round-based review lenses: Rotate between artifact, execution, and contract lenses across review rounds so repeated reviews catch different defect classes instead of re-finding the same issues. - Role separation enforcement: The reviewer never edits the implementation, preserving ownership boundaries and keeping re-review independent. - Use Case: An implementer submits a review_requested handoff claiming a bug fix with passing tests. The reviewer reads the task via kanban_show, checks out the diff, runs the focused tests, finds an unhandled edge case, and returns the task with actionable findings. ## Quick Start Ask the agent to review the current Kanban review-lane task by reading the handoff with kanban_show, verifying the deliverable against the acceptance criteria, and submitting exactly one 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 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 verification, and submit exactly one verdict: kanban_complete, kanban_request_changes, or kanban_block.

How to request changes on a Kanban task as a reviewer?▼

First record actionable findings with kanban_comment, stating where the defect is, how it reproduces, and the minimum fix. Then call kanban_request_changes with a concise reason, which returns the task to its original implementer.

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 it. Correctable implementation defects belong in kanban_request_changes, not blockers.

Can the reviewer edit the implementation during review?▼

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

Why do repeated review rounds find the same defects?▼

Repeating the same inspection lens re-finds what earlier rounds already found. This Skill rotates lenses by round: artifact cold-read on round 1, execution and testing on round 2, and strict contract audit against the original acceptance criteria on round 3 and beyond.