verify-phase

Name: verify-phase
Availability: InStock
Author: VirtEngine

Verify project phase goals by checking artifacts, truths, and wiring.

17|4|Updated Oct 8, 2021

Search Tags:#automation #workflow #verification #quality #goals #code-review #phase

Ready to run

npx skills add https://github.com/virtengine/virtengine --skill verify-phase-virtengine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-phase
Source: https://github.com/virtengine/virtengine/tree/main/.github/skills/verify-phase
Command: npx skills add https://github.com/virtengine/virtengine --skill verify-phase-virtengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify phase goal achievement through goal-backward analysis. Check that the codebase actually delivers what the phase promised, not just that tasks were completed.

Core Features & Use Cases

Load context from ROADMAP and phase requirements to identify the phase goal and necessary conditions.
Derive and verify must-haves (truths, artifacts, and wiring) for end-to-end phase validation.
Generate structured VERIFICATION.md reports, anti-pattern scans, and clear human-verification prompts.
Produce actionable fix plans when gaps are found and support re-verification cycles.

Quick Start

Invoke this workflow for the target phase to automatically verify goals and generate a VERIFICATION.md 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 project phase goals are actually met in the codebase?▼

To verify phase goals, goal-backward verification checks that the codebase delivers promised outcomes by ensuring artifacts, truths, and wiring exist, are substantive, and are correctly wired with evidence.

What is goal-backward verification in software delivery workflows?▼

Goal-backward verification identifies the phase goal from ROADMAP requirements and validates must-haves, checking that artifacts and wiring exist substantively rather than merely confirming task completion.

How do I generate a VERIFICATION.md report for a CI pipeline phase?▼

Invoke automated phase verification on the target phase to derive necessary conditions, scan for anti-patterns, and output a structured VERIFICATION.md report containing evidence and human-verification prompts.

Can automated phase validation detect missing artifacts and wiring across codebases?▼

Yes, phase validation loads context from ROADMAP and phase requirements to derive must-haves, identifying gaps where artifacts, truths, or wiring are missing or incorrectly wired within the codebase.

What should I do when phase verification finds gaps in required outcomes?▼

When verification finds gaps, it produces actionable fix plans detailing required corrections and supports re-verification cycles to confirm the codebase ultimately delivers the promised phase outcomes.

Does phase verification work for CI pipelines and codebase workflows?▼

Yes, goal-backward verification applies directly to software delivery phases, codebases, and verification workflows across CI pipelines to ensure end-to-end phase validation with required evidence.