verify-phase

Verify phase goal achievement in codebases against ROADMAP and output VERIFICATION.md reports.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill verify-phase-rayofsteel-dhbw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-phase
Source: https://github.com/RayOfSteel-DHBW/TeilAutoNeu/tree/main/.github/skills/verify-phase
Command: npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill verify-phase-rayofsteel-dhbw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end verification of phase goals to ensure that delivered code and tasks truly satisfy the promises made in the roadmap.

Core Features & Use Cases

  • Verifies phase goal achievement by cross-referencing ROADMAP, REQUIREMENTS, and phase summaries.
  • Checks artifact existence, substance, and wiring, and validates key links between components.
  • Produces a VERIFICATION.md report and suggested fix plans when gaps are found.

Quick Start

Run the verify-phase workflow for the target phase to generate a complete verification report.

Frequently Asked Questions about verify-phase

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

FAQPage Schema
How do I verify phase goals are achieved in my codebase after development?

To verify phase goals, run the verify-phase workflow against the target phase to derive must-haves from the ROADMAP or PLAN frontmatter. It checks artifact existence, substance, and wiring, then generates a VERIFICATION.md report with evidence and suggested fix plans for any gaps found.

What is goal-backward analysis for phase verification?

Goal-backward analysis is a verification mechanism that starts from phase goals defined in the ROADMAP and works backward to check if the actual codebase artifacts satisfy them. It validates key links between components to ensure delivered code truly meets roadmap promises.

How do I check if my codebase artifacts have substance and proper wiring?

Checking artifact substance and wiring involves validating that required artifacts exist, contain meaningful content, and are correctly connected to other components. The verification process also scans for anti-patterns and validates key links to ensure phase goals are truly delivered.

Can I generate fix plans automatically when phase verification finds gaps?

Yes, when verification identifies gaps in phase goal achievement, it produces optional fix plans alongside the VERIFICATION.md report. These suggested plans address missing artifacts, insufficient substance, or improper wiring found during the goal-backward analysis.

Does phase verification work without external dependencies or pipeline tools?

Yes, phase verification operates with no external dependencies, relying solely on the ROADMAP, REQUIREMENTS, and PLAN frontmatter within your codebase. It returns results directly to the orchestrator after generating the verification report.