verify-work
$
npx mdskill add HoangNguyen0403/agent-skills-standard/verify-work> [!IMPORTANT] > Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
SKILL.md
.github/skills/verify-workView on GitHub ↗
---
name: verify-work
description: "Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria."
metadata:
triggers:
keywords:
- verify work
- workflow
---
# Verify Work Skill
> [!IMPORTANT]
> Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
## Instructions
When the user asks to perform this workflow, execute the following steps:
# Verify Work Workflow
Goal: Prove the delivered change works against explicit acceptance criteria before handoff.
## Steps
1. Load scope:
- BRD-lite, PRD, SRS/FRS, ticket, implementation plan, or release note.
- Acceptance criteria and non-goals.
- Changed files and matched skills.
2. Select verification lanes:
- Unit or component tests
- Integration or API tests
- E2E or visual checks
- Mobile emulator checks
- Security checks
- Migration or deployment smoke
3. Execute:
- Run the smallest reliable automated checks first.
- Use Playwright/Appium only when user-facing behavior changed.
- Use Zephyr/Jira/GitHub/GitLab/ADO MCPs only when configured; otherwise record local evidence.
- If external MCP is unavailable, ask for exported ticket/PR/TC data or mark that lane BLOCKED.
- Capture logs, screenshots, traces, or command output summaries.
- Re-run failed checks after fixes.
4. Judge:
- PASS: all acceptance criteria proven.
- FAIL: original bug or missed requirement still reproducible.
- BLOCKED: environment, credentials, or approval prevents proof.
5. Record evidence:
- If verification reveals behavior drift, require PRD/SRS updates before PASS.
- Update traceability notes from BRD objective -> PRD requirement -> SRS/FRS contract -> verification evidence.
- Update project-local `docs/templates/walkthrough.md`.
- Route next step back to implementation or `dev-fix`.
## Output
## Artifact Templates
### Walkthrough Template
```md
# Walkthrough: [Name]
## Scope
## Acceptance Criteria
## Evidence
## Risks
## Next Workflow
```
## Output Template
```md
# Verification Report: [Name]
## Scope
## Checks Run
## Acceptance Criteria
## Requirement Trace Status
## Risks
## Next Workflow
implement-feature | dev-fix
## Cost Report
```
More from HoangNguyen0403/agent-skills-standard
- android-agp-upgradeUpgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
- android-architectureApply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns.
- android-background-workImplement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers.
- android-composeBuild high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects.
- android-compose-migrationMigrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
- android-concurrencyWrite correct coroutine scopes, Flow collection, and dispatcher injection in Android. Use when writing suspend functions, choosing between StateFlow and SharedFlow, or injecting Dispatchers for testability.
- android-deploymentConfigure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
- android-design-systemEnforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
- android-diConfigure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when setting up Hilt DI, defining modules, or configuring component scoping.
- android-edge-to-edgeMigrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.