verify-workstream

Validates project documentation and codebase metadata alignment via configurable checks and CLI output.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/fall-out-bug/sdp_lab --skill verify-workstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-workstream
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/verify-workstream
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill verify-workstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that workstream documentation matches the codebase, reducing drift between planned scope and actual implementation.

Core Features & Use Cases

  • Frontmatter validation: ensures required metadata exists and aligns with repository reality.
  • Scope/file verification: checks that all declared scope_files exist and are accessible.
  • Discrepancy reporting: outputs a comparison table of Documentation vs. Reality and provides remediation guidance.

Quick Start

Run the verify-workstream skill before build or oneshot to ensure the documentation matches the codebase.

Frequently Asked Questions about verify-workstream

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

FAQPage Schema
How do I verify that workstream documentation aligns with the codebase?▼

To verify workstream documentation aligns with the codebase, cross-reference frontmatter goals and acceptance criteria with actual files. This validation checks that declared scope_files exist and implementation matches documented patterns.

What is frontmatter validation for a codebase workflow?▼

Frontmatter validation ensures required metadata exists and aligns with repository reality. It checks that declared scope_files are accessible and match the actual codebase, reducing drift between planned scope and implementation.

How do I check if declared scope_files exist before a build?▼

Run a pre-build validation to check if declared scope_files exist and are accessible. This process cross-references workstream documentation against the codebase to ensure the implementation matches documented patterns.

What does a documentation vs reality comparison table include?▼

A documentation vs reality comparison table includes a severity score, recommended action, and discrepancy reporting. It maps workstream documentation against the codebase to guide remediation efforts directly.

When should I validate workstream documentation to prevent codebase drift?▼

You should validate workstream documentation during pre-build and pre-run stages. Applying validation at these stages verifies declared scope_files exist and ensures the actual implementation matches the documented patterns.

What to do if workstream documentation does not match the codebase implementation?▼

If workstream documentation does not match the codebase implementation, review the structured output containing a severity score and comparison table. Use the provided remediation guidance and recommended actions to resolve the discrepancies.