po-acceptance

Delegate product-owner acceptance validation to a bounded subagent on a feature branch.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/patrob/skills --skill po-acceptance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: po-acceptance
Source: https://github.com/patrob/skills/tree/main/plugins/claude-skills/skills/po-acceptance
Command: npx skills add https://github.com/patrob/skills --skill po-acceptance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates end-to-end product-owner acceptance validation to a bounded subagent to avoid manual triage and ensure consistent sign-off.

Core Features & Use Cases

  • Bounded PO subagent that reads project inputs, applies success and acceptance criteria, and returns a structured verdict.
  • JSON verdict integrates with orchestration workflows to route outcomes and update criteria for subsequent cycles.
  • Enforces tool-bounds to prevent source changes or unauthorized installs while enabling read-only verification.

Quick Start

Run po-acceptance on a feature-branch with the appropriate criteria payload to obtain a formal verdict for gating merges.

Frequently Asked Questions about po-acceptance

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

FAQPage Schema
How do I automate product owner acceptance testing for feature sign-off?

Automated product owner acceptance testing delegates end-to-end validation to a bounded subagent on a feature branch, proving success and acceptance criteria before returning a structured verdict for merge gating.

What is a bounded subagent workflow for acceptance validation?

A bounded subagent workflow for acceptance validation reads project inputs, applies criteria, and enforces tool bounds to restrict actions to read-only checks, preventing source changes or unauthorized installs during verification.

How do I generate a verdict JSON for orchestrating acceptance workflows?

You generate a verdict JSON by running the acceptance subagent with a criteria payload on a feature branch. The JSON output integrates with orchestration workflows to route outcomes and update criteria for subsequent cycles.

Can I use read-only checks for acceptance criteria without modifying source code?

Yes, read-only checks enforce tool bounds that restrict the subagent to verification actions only, preventing source modifications and unauthorized installs while validating acceptance criteria.

What's the best way to validate success criteria across multiple workstreams?

Validating success criteria across multiple workstreams requires a bounded subagent that operates on a feature branch, applying criteria payloads and emitting structured verdict JSON to update subsequent verification cycles.