verify-work

Validate built software features through conversational testing with persistent state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of validating built features by engaging the user in a conversational testing loop, ensuring that implemented functionality matches expected outcomes and capturing any discrepancies.

Core Features & Use Cases

  • Conversational Testing: Guides users through testing scenarios, asking if reality matches expectations.
  • Persistent State: Tracks test progress across sessions, surviving context resets.
  • Automated Issue Capture: Logs any deviations from expected behavior as issues with inferred severity.
  • Gap Analysis: Feeds identified issues into a planning phase for resolution.
  • Use Case: After a new feature is deployed, use this Skill to systematically walk through its functionality, confirming each step works as intended and automatically documenting any bugs found.

Quick Start

Use the verify-work skill to start testing phase 4.

Frequently Asked Questions about verify-work

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

FAQPage Schema
How do I validate software features through conversational testing?

Conversational testing validates software features by guiding you through interactive scenarios, asking if reality matches expectations, and capturing deviations as issues with inferred severity. It creates a UAT.md file to track progress and feeds identified gaps into a planning phase.

What is the best way to track UAT progress across context resets?

Tracking UAT progress across context resets requires persistent state management. This approach creates UAT.md files to log test progress, ensuring your validation sessions survive interruptions and maintain continuity without losing tracked issues.

How does automated issue capture work during user acceptance testing?

Automated issue capture during user acceptance testing logs discrepancies between expected and actual outcomes. It presents expected results, captures your feedback, and automatically records bugs with inferred severity to streamline gap analysis.

Can I use conversational AI to document bug tracking gaps for planning?

Conversational AI can document bug tracking gaps by validating built features interactively and feeding identified issues into a planning phase. This automates resolution tracking by capturing deviations and inferring severity for downstream planning.

When do I need persistent state management for feature validation?

Persistent state management for feature validation is needed when testing spans multiple sessions or faces context resets. It ensures your UAT.md progress files survive interruptions, maintaining test continuity and tracking gaps without data loss.