verify-phase

Verify phase goal achievement through goal-backward analysis and artifact wiring checks.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/bhanukushwah/parinaya-os --skill verify-phase-bhanukushwah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-phase
Source: https://github.com/bhanukushwah/parinaya-os/tree/main/.kilocode/skills/verify-phase
Command: npx skills add https://github.com/bhanukushwah/parinaya-os --skill verify-phase-bhanukushwah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that completed development phases have actually achieved their intended goals, not just completed individual tasks, by performing goal-backward analysis.

Core Features & Use Cases

  • Goal-Backward Analysis: Verifies if the codebase delivers on the phase's promise by working backward from the desired outcome.
  • Artifact & Wiring Verification: Checks for the existence, substance, and correct connection of code artifacts (files, components, APIs).
  • Use Case: After a phase to "implement user authentication," this Skill would verify not just that login/logout files exist, but that a user can successfully log in, remain authenticated, and log out, confirming the goal of authentication was met.

Quick Start

Verify the current phase's goals by running the verify-phase skill.

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 uses goal-backward analysis to ensure the codebase delivers on phase promises. It checks artifact existence, substance, and wiring to confirm outcomes are met, not just individual tasks.

What is goal-backward analysis in software verification?

Goal-backward analysis works backward from the desired phase outcome to verify codebase delivery. It confirms that artifacts exist, contain substance, and are correctly wired together to achieve the stated goal.

How do I check if my code artifacts are properly wired together after a development phase?

Artifact and wiring verification scans the codebase to confirm files, components, and APIs exist, contain actual substance, and are correctly connected. This ensures the phase goal is functionally achieved.

Can I use automated verification to detect anti-patterns after finishing a development phase?

Yes, phase verification scans for identified anti-patterns during the analysis process. It checks artifact substance and wiring, then generates a verification report detailing the overall status of phase goals.

Does phase verification work without external dependencies?

Yes, phase verification operates without external dependencies. It loads context, establishes must-haves, verifies truths and artifacts, scans anti-patterns, and determines overall status entirely within its own framework.

What does a phase verification report include?

A verification report includes the overall status of phase goal achievement. It details artifact existence, substance checks, wiring verification, and any anti-patterns identified during the goal-backward analysis.