skills.rest
yutna
yutnaCOMMUNITY
Explore all skills by this author →
GitHub

delivery-validation

Validate delivery readiness after verification and quality gates.

2|Updated Feb 13, 2026
Search Tags:#validation#verification#handoff#delivery#quality-gates#workflow-state#pre-delivery
One-click install
npx skills add https://github.com/yutna/vibe-next-template --skill delivery-validation-yutna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-validation
Source: https://github.com/yutna/vibe-next-template/tree/main/.claude/skills/delivery-validation
Command: npx skills add https://github.com/yutna/vibe-next-template --skill delivery-validation-yutna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivery validation ensures that software is production-ready after quality gates, verification, and stakeholder sign-off, by confirming criteria are met and surfacing any blockers before handoff.

Core Features & Use Cases

  • Pre-delivery checklist verification: ensures requirements are satisfied, automated gates are green or explicitly not applicable, and blockers are explicit.
  • Workflow state updates and handoff generation: updates phase to "delivery" and sets delivery.status to "ready-for-review" when the work is truly reviewable, producing a clear, user-facing handoff.
  • Reference guided process: leverages CLAUDE.md and .claude/workflow-state.json to maintain traceability and auditability during delivery.

Quick Start

Review the current verification results and trigger the delivery-readiness check to prepare the handoff.

Frequently Asked Questions about delivery-validation

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

FAQPage Schema
How do I validate software delivery readiness after quality gates pass?▼

Pre-delivery checklist verification ensures requirements are met, automated gates are green or explicitly not applicable, and blockers are surfaced, enabling a workflow state update to ready-for-review.

How do I generate a delivery handoff that confirms changed files and user impact?▼

Generating a delivery handoff involves reviewing verification results, confirming changed files and user impact, and updating the workflow state to produce a clear, user-facing ready-for-review handoff.

What is the best way to update workflow state for a project transitioning to delivery?▼

Updating workflow state for delivery involves leveraging CLAUDE.md and .claude/workflow-state.json to maintain traceability, setting the phase to delivery and the status to ready-for-review when criteria are met.

Can I use workflow-state.json to maintain traceability during delivery validation?▼

Yes, delivery validation leverages CLAUDE.md and .claude/workflow-state.json to maintain traceability and auditability, ensuring workflow state updates and handoff generation are reference-guided.

When should I not use an automated pre-delivery checklist for software handoff?▼

Avoid automated pre-delivery checklist verification when quality gates are failing without explicit non-applicable status, or when blockers remain unresolved before transitioning to the delivery workflow state.

Related Skills

Explore More Software Engineering Skills→
tody-agenttody-agent
48

cm-quality-gate

Enforce test gates and evidence-based verification before deployment in CI/CD workflows.

Community
Advanced
rajnishkhatrirajnishkhatri

sdd-converge

Classify gaps between built and specified requirements and spawn fix tasks.

Community
Intermediate
yutnayutna
2

state-sync

Synchronize task state changes to .claude/workflow-state.json across workflow phases.

Community
Advanced
rajitsaharajitsaha
10

release

Coordinate software release cycles with quality gates, versioning, tagging, and verification.

Community
Advanced