verify

Align documentation, behavioral tests, and source code on feature branches.

Updated May 6, 2026
One-click install
npx skills add https://github.com/SuSuSleep/scaffold --skill verify-sususleep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/SuSuSleep/scaffold/tree/main/skills/verify
Command: npx skills add https://github.com/SuSuSleep/scaffold --skill verify-sususleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the deployment of features where documentation, behavioral tests, and implementation code have drifted apart, ensuring high-quality PRs.

Core Features & Use Cases

  • Three-Way Alignment: Validates that test scenarios match documentation requirements and that code implementation reflects those tests.
  • Diagnostic Reporting: Surfaces missing test cases, TBD placeholders, and behavioral mismatches before code reaches the main branch.
  • Use Case: Use this after merging your draft documentation to ensure that your behavioral tests are fully synced with your user stories and that no implementation gaps remain.

Quick Start

Run the verify skill to check if the current feature branch is aligned and ready for a pull request.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I check if my behavioral tests match documentation and code?

To check if behavioral tests match documentation and code, perform a three-way alignment validation comparing scenario counts, reference correctness, and behavioral assertions across changed files in a feature branch.

Why does my feature branch have missing test cases and TBD placeholders?

Missing test cases and TBD placeholders occur when documentation, behavioral tests, and source code drift apart during development. Diagnostic reporting surfaces these behavioral mismatches before a pull request reaches the main branch.

Do I need git integration to verify documentation and test alignment?

Yes, you need git integration to verify documentation and test alignment. Git identifies the scope of changed files within a feature branch, enabling the three-way alignment check against defined documentation schemas and test conventions.

What's the best way to prevent feature drift before merging a pull request?

The best way to prevent feature drift before merging a pull request is running a final alignment gate. This validates that test scenarios match documentation requirements and code implementation reflects those tests.

When do I need to run a three-way alignment check on my source code?

You need to run a three-way alignment check on your source code after merging draft documentation. This ensures behavioral tests are fully synced with user stories and confirms no implementation gaps remain.