skills.rest
tapania
tapaniaCOMMUNITY
Explore all skills by this author →
GitHub

5d-verify

Automate multi-layer verification of implemented features against plan and spec.

5|Updated Jan 30, 2026
Search Tags:#workflow#QA#build#spec#verify#lint#tests
One-click install
npx skills add https://github.com/tapania/5d-skills --skill 5d-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 5d-verify
Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-verify
Command: npx skills add https://github.com/tapania/5d-skills --skill 5d-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured, multi-layer verification to ensure implemented features align with the original plan, spec, and user intent, reducing defects before release.

Core Features & Use Cases

  • Layered Verification: Checks technical correctness, spec fidelity, and plan validity across the development lifecycle.
  • Failure Routing & Reporting: Routes issues to BUILD, SPEC, PLAN, or SPAR phases and produces a clear Verification Report.
  • Acceptance & Documentation: Supports automated checks, manual comparisons, and user acceptance testing with traceable outcomes.

Quick Start

Activate the verify phase after finishing BUILD and run the verification workflow to generate a report.

Frequently Asked Questions about 5d-verify

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

FAQPage Schema
How do I verify implemented features against the original spec after a build?▼

To verify implemented features against the original spec, run multi-layer validation checks across technical correctness, spec fidelity, and plan validity after the build phase to ensure alignment and reduce defects.

What is multi-layer verification in software QA workflows?▼

Multi-layer verification in software QA is a process that checks technical correctness, spec fidelity, and plan validity across the development lifecycle to ensure implemented features align with the original plan and user intent.

How do I route verification failures back to the correct development phase?▼

Route verification failures by categorizing issues into BUILD, SPEC, PLAN, or SPAR phases during the validation workflow, which produces a structured Verification Report with clear failure routing for targeted fixes.

What checks are required for user acceptance testing and spec comparison?▼

User acceptance testing and spec comparison require running automated checks for build and lint, executing tests, and performing manual spec comparisons to generate traceable validation outcomes and a comprehensive Verification Report.

Can I use automated lint and tests for manual spec comparison workflows?▼

Yes, automated lint and test checks run alongside manual spec comparison workflows to validate technical correctness, ensuring implemented features match the original plan and spec before producing a structured Verification Report.

When should I run the verification workflow in the development lifecycle?▼

Run the verification workflow after finishing the build phase and before release, applying it during validation, testing, and user acceptance to check technical correctness, spec fidelity, and plan validity.

Related Skills

Explore More Software Engineering Skills→
michael-conradmichael-conrad

writing-plans

Convert approved specs into structured implementation plans with phases, tasks, and validation steps.

Community
Advanced
windyskywindysky

moai-workflow-spec

Orchestrate SPEC workflows with EARS format and Plan-Run-Sync lifecycle.

Community
Basic
MomoDavilukeMomoDaviluke
2

verification-loop

Automate builds, type checks, linting, tests, and security scans for Claude Code sessions.

Community
Advanced
fdshg693fdshg693

copilot-test-skill

Validate Copilot integration with a minimal YAML frontmatter Skill unit.

Community
Basic