verify-phase

Verify phase goal achievement via goal-backward analysis of codebase artifacts.

Updated Jan 12, 2026

Search Tags:#quality assurance #verification #codebase analysis #phase completion #goal achievement #gsd-tools

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gsd-tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that completed tasks have actually delivered on the promised phase goals, preventing the common pitfall of tasks being marked complete without achieving the overarching objective.

Core Features & Use Cases

Goal-Backward Analysis: Verifies if the codebase meets the phase's intended outcomes by analyzing requirements, artifacts, and wiring.
Automated Verification: Leverages gsd-tools to check artifact existence, substance, and connectivity.
Use Case: After a development phase, this Skill can be run to confirm that a new feature, like a "working chat interface," is truly functional and not just a placeholder component with a connected API stub.

Quick Start

Run the verify-phase skill for the current phase to check if the codebase meets its goals.

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 completion beyond just checking off tasks?▼

Phase completion verification requires goal-backward analysis to ensure the codebase meets phase promises. This approach checks that completed tasks actually deliver the intended outcomes, preventing the common pitfall of marking tasks done without achieving the overarching objective.

What is goal-backward analysis in quality assurance?▼

Goal-backward analysis is a verification method that evaluates codebase deliverables against phase goals rather than task lists. It analyzes requirements, artifacts, and wiring to confirm that implemented features are truly functional, not just placeholder components.

How do I check if codebase artifacts align with phase requirements?▼

Checking codebase artifact alignment involves verifying artifact existence, substance, and connectivity. Automated tools like gsd-tools perform these checks alongside manual anti-pattern scanning to confirm deliverables match the phase's intended outcomes.

Do I need gsd-tools to run phase verification checks?▼

Yes, gsd-tools is a required dependency for phase verification checks. The Skill leverages gsd-tools to verify artifact existence, substance, and key-link connectivity, and also requires shell commands for context loading and anti-pattern scanning.

What's the best way to confirm a new feature is functional and not a stub?▼

The best way to confirm a feature is functional is running a goal-backward verification to analyze requirements and wiring. This ensures the codebase contains a working implementation with proper connectivity, not just a placeholder component with a connected API stub.

Why does task completion not guarantee phase goal achievement?▼

Task completion does not guarantee phase goal achievement because individual tasks can be marked complete without delivering the overarching objective. Goal-backward analysis solves this by verifying that codebase deliverables and artifacts actually align with the promised phase outcomes.