uat-signoff
Facilitates UAT signoff. Use this to demo verified work and collect acceptance.
Install
mkdir -p .claude/skills/uat-signoff && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18839" && unzip -o skill.zip -d .claude/skills/uat-signoff && rm skill.zipInstalls to .claude/skills/uat-signoff
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.Key capabilities
- →Load verification reports and acceptance criteria
- →Draft demo scripts mapping ACs to business outcomes
- →Present AC outcomes to approvers for acceptance or rejection
- →Capture signoff owner, date, and per-AC decisions
- →Route to `deploy-release` or `dev-fix` based on signoff
How it works
This skill guides a business or UAT approver through a demo of a verified feature, capturing their acceptance decision.
Inputs & outputs
When to use uat-signoff
- →Collect business acceptance
- →Demo features to stakeholders
- →Verify UAT status
- →Document signoff artifacts
About this skill
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-workreport, AC list, PRD/BRD-lite business objective, and inheritedoperator_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=businessorhybrid, 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-workPASS on a feature, beforedeploy-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.
When not to use it
- →Before a `verify-work` PASS on a feature
- →When no verification report exists
- →When the approver is unavailable in autonomous or channel mode
Limitations
- →Requires a `verify-work` PASS report as input
- →Cannot proceed without an existing verification report
- →Cannot proceed if the approver is unavailable in autonomous/channel mode
How it compares
This skill formalizes the UAT signoff process by linking acceptance criteria to observable business outcomes, ensuring clear decision capture compared to informal approvals.
Compared to similar skills
uat-signoff side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| uat-signoff (this skill) | 0 | 16d | No flags | Intermediate |
| linear-ci-integration | 1 | 9d | Caution | Intermediate |
| work-on-issue | 0 | 5mo | Review | Intermediate |
| regression | 0 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by HoangNguyen0403
View all by HoangNguyen0403 →You might also like
linear-ci-integration
jeremylongshore
Configure Linear CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Linear sync into your build process. Trigger with phrases like "linear CI", "linear GitHub Actions", "linear automated tests", "CI linear pipeline", "linear CI/CD".
work-on-issue
meta-pytorch
Start work on a GitHub issue. Extracts requirements, creates worktree, sets up TDD workflow.
regression
ThePalaceProject
Run a full release regression test — sets up workspace, runs automated tools, guides manual testing, generates report and Jira tickets. Use for release gates and QA cycles.
team-qa
bullish0x
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sig
ticket-implementation-copilot
Newton-School
Execute DSDS roadmap tickets using dependency-aware, acceptance-criteria-first delivery. Use when selecting the next unblocked ticket, implementing code changes, validating behavior, and reporting completion against ticket AC.
jira-api-test-cases
DiasLuc
Create API test cases from a Jira user story and the project's Swagger or OpenAPI file. Use when the task is to read a Jira story, derive functional API test cases from its acceptance criteria, propose the list for approval, and then create the approved cases as Jira subtasks with a consistent templ