Verify application behavior against acceptance criteria and release requirements.
npx skills add https://github.com/sohei56/maul-team --skill po-acceptance-sohei56
Please help me install this Agent Skill. Skill: po-acceptance Source: https://github.com/sohei56/maul-team/tree/main/skills/po-acceptance Command: npx skills add https://github.com/sohei56/maul-team --skill po-acceptance-sohei56
This Skill prevents unverified features from reaching release by systematically launching the application, exercising acceptance criteria, and recording evidence-based Product Owner decisions.
Activate the po-acceptance skill in demo or uat mode and provide the current sprint identifier so it can run the appropriate acceptance walkthrough and report its verdicts.
High-intent search queries and answers about installing and using this skill.
You verify release readiness by systematically launching the application, exercising acceptance criteria, and recording evidence-based Product Owner decisions. This Skill applies to Sprint Review demos and Integration Sprint user acceptance testing to produce traceable verdicts.
You need Scrum artifacts, documented requirements, configured PO decision scripts, and a runnable application or documented startup path. These inputs allow the Skill to execute command-line, HTTP, browser, and persistence-store verification scenarios.
Acceptance criteria traceability works by deriving traceable user stories from requirements, validating release readiness, and capturing commands, outputs, transcripts, and decision records. This aggregated evidence supports Scrum Master follow-up and ensures unverified features do not reach release.
During release verification, startup failures are detected to preserve the acceptance bar. Defects are routed without modifying source code, and any launched application processes are safely stopped before exiting to ensure failure safety.
Yes, you can use command-line, HTTP, browser, and persistence-store verification scenarios for product acceptance. The Skill systematically exercises acceptance criteria across these interfaces to validate application behavior during Sprint Reviews.
To start, activate the Skill in demo or uat mode and provide the current sprint identifier. This triggers the appropriate acceptance walkthrough, which systematically tests the application and reports its verdicts.
cute-baobaoMerge server-side environment variables into user settings at runtime.
laraxotSummarize sprint status and recommend next workflow actions from sprint-status.yaml.
valkryhxAutomate browser interactions via command-line for navigation, form submission, and screenshots.
aquariuscookValidate software requirements by assessing SMART acceptance criteria and generating traceability matrices.
