review

Run automated three-layer checks and guided UAT against must-haves.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SienkLogic/towline --skill review-sienklogic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/SienkLogic/towline/tree/main/plugins/dev/skills/review
Command: npx skills add https://github.com/SienkLogic/towline --skill review-sienklogic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The /dev:review skill verifies that built work aligns with the plan by performing automated three-layer verification against must-haves and guiding you through a conversational UAT for each deliverable.

Core Features & Use Cases

  • Automated three-layer checks (existence, substantiveness, wiring) against must-haves to surface gaps early.
  • Guided User Acceptance Testing (UAT) that walks through each deliverable and records actionable feedback.
  • Escalation paths and re-planning support for gaps, with plan creation and verification bridging.
  • Lightweight orchestration with Towline subagents and VERIFICATION.md as the ground truth.

Quick Start

Start a phase review by running /dev:review <phase-number> to begin automated verification and guided UAT.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate user acceptance testing for software builds?

Automated UAT for software builds is achieved by running conversational walkthroughs for each deliverable, verifying that built work aligns with the plan while recording actionable feedback.

What is three-layer verification for build validation?

Three-layer build validation verifies deliverables across existence, substantiveness, and wiring against must-haves to surface gaps early, using VERIFICATION.md as the ground truth.

How do I run a phase review for multi-phase builds?

Phase review for multi-phase builds is initiated by running the review command with the phase number, triggering automated verification and guided UAT against phase artifacts like SUMMARY.md and PLAN.md.

Do I need specific artifacts to verify that built software matches the plan?

Yes, verifying that built software matches the plan requires phase artifacts such as SUMMARY.md, PLAN.md, and VERIFICATION.md, with VERIFICATION.md serving as the ground truth for automated checks.

Can I use subagents for automated verification and escalation?

Subagents can be spawned for automated verification, reporting, and escalation during phase reviews, providing lightweight orchestration and supporting re-planning for gaps found during build validation.

What is the best way to surface gaps during build validation?

The best way to surface gaps during build validation is performing automated three-layer checks against must-haves, identifying missing deliverables early and providing escalation paths for re-planning.