verify

Run goal-backward checks, E2E browser tests, and user acceptance testing on software artifacts.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/progremir/pluto --skill verify-progremir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/progremir/pluto/tree/main/skills/verify
Command: npx skills add https://github.com/progremir/pluto --skill verify-progremir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a crucial quality gate, ensuring that implemented code meets rigorous standards through automated checks and user validation before proceeding or finalizing.

Core Features & Use Cases

  • Goal-Backward Verification: Enforces EXISTS, SUBSTANTIVE, and WIRED checks for every story to prevent stubs and dead code.
  • E2E Browser Testing: Validates user-facing functionality and UI flows within a browser environment.
  • User Acceptance Testing (UAT): Facilitates formal review and approval of completed work by stakeholders.
  • Use Case: After an autonomous development phase, this Skill systematically checks that all new code is functional, integrated, and meets acceptance criteria, providing a clear report for review and approval.

Quick Start

Run the verify skill to perform goal-backward checks, E2E browser testing, and user acceptance testing on the completed stories.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate user acceptance testing and code verification before final delivery?

Automate user acceptance testing and code verification by running multi-stage checks that enforce goal-backward validation, browser UI flow testing, and stakeholder review. This ensures implemented code meets integration requirements and acceptance criteria before phase transitions or final delivery.

What are goal-backward checks for software quality assurance?

Goal-backward checks for software quality assurance validate that every story passes EXISTS, SUBSTANTIVE, and WIRED inspections. This mechanism prevents stubs and dead code by confirming implemented features are fully present, functionally substantive, and correctly integrated into the system.

How does end-to-end browser testing validate user-facing functionality?

End-to-end browser testing validates user-facing functionality by executing UI flows within a browser environment. This process confirms that new code operates correctly across user interfaces, ensuring functional integration and adherence to requirements before user acceptance testing.

Can I use automated verification to prevent stubs and dead code in autonomous development?

You can use automated verification in autonomous development to prevent stubs and dead code. The process enforces rigorous goal-backward checks, specifically the SUBSTANTIVE and WIRED validations, to ensure all generated code is functional, fully integrated, and meets required standards.

When do I need a quality gate for phase transitions in software engineering?

You need a quality gate for phase transitions when implemented code must meet rigorous standards before proceeding. It systematically checks that new development artifacts are functional, integrated, and meet acceptance criteria, providing a clear report for stakeholder review and approval.

Does automated code review work with user acceptance testing for final delivery?

Automated code review works with user acceptance testing by combining multi-stage artifact verification with formal stakeholder approval. This integration ensures code quality, functional integration, and adherence to requirements are validated before finalizing software delivery.