mcpbeat

Uat Signoff

hoangnguyen0403/uat-signoff

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

723 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill uat-signoff

The instruction itself

8 sections, as written by the author

Uat Signoff Skill

> [!IMPORTANT]

> Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

UAT Signoff Workflow

Goal: Convert a verify-work PASS into an explicit, evidence-linked business acceptance decision before release.

Steps

  • Load scope:
  • verify-work report, AC list, PRD/BRD-lite business objective, and inherited operator_profile (carry, do not re-infer).
  • Load common-operator-profile.
  • Draft demo script:
  • Map each AC to an observable business outcome in plain language; omit file paths, commands, and code identifiers from the primary script.
  • For operator_profile=business or hybrid, this plain-language script is the primary artifact; keep technical trace in a trailing appendix.
  • Walk the signoff:
  • Present each AC outcome and ask the approver to accept or reject.
  • Ask max 3 blocking questions at a time with a recommended default and 2-3 options.
  • Record conditions attached to any conditional acceptance.
  • Capture decision:
  • Signoff owner, date, and per-AC accept/reject status.
  • Reject on any AC -> route to dev-fix.
  • Full accept -> route to deploy-release.

Runtime Contract

  • Use after verify-work PASS on a feature, before deploy-release.
  • Required inputs: a PASS verification report with an AC list to demo against.
  • Return BLOCKED only when no verification report exists or the approver is unavailable in autonomous/channel mode.

Handoff Payload

  • slug, operator_profile, signoff owner, per-AC decision, conditions, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# UAT Signoff: [Name]

## Demo Script (Plain Language)

## Per-AC Decision

| AC ID | Outcome Demonstrated | Decision | Conditions |
| --- | --- | --- | --- |
| [ac-id] | [outcome] | [accept/reject] | [conditions] |

## Signoff Owner And Date

## Technical Appendix

## Outcome Report
feature_status: implemented | partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: deploy-release | dev-fix

## Next Workflow
deploy-release | dev-fix

## Cost Report
Call `get_session_cost(workflow="uat-signoff")` before final handoff.

How to use it

Copy the folder

Take hoangnguyen0403/uat-signoff from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.