| name | post-deploy-qa |
| description | Post-deploy verification: execute AVP from tech-spec on live environment,
verify all acceptance criteria (user-spec + tech-spec), pick up deferred
criteria from pre-deploy QA report. Uses MCP tools (Telegram MCP, Playwright, curl, bash).
Use when: "пост-деплой проверка", "post-deploy verification", "проверь после деплоя",
"MCP verification", "верификация на живом окружении", "проверь деплой",
"запусти AVP", "agent verification plan"
|
Post-deploy QA
Input Requirements
Read before starting:
user-spec.md — acceptance criteriatech-spec.md — Agent Verification Plan (AVP) section + technical acceptance criteriadecisions.md — deviations from plan (if exists)- Pre-deploy QA report (
logs/working/qa-report.json) — check deferredToPostDeploy section for criteria that could not be verified pre-deploy
- Confirmation that deploy is complete and environment is live
If tech-spec has no AVP section — still proceed with acceptance criteria verification.
Verification Methodology
Two verification directions (both required):
1. Agent Verification Plan (AVP)
Execute each step from AVP section in tech-spec:
- Read AVP section — it lists verification steps with expected outcomes and MCP tools to use
- For each step:
- Use the specified MCP tool (Telegram MCP, Playwright, curl, bash, etc.)
- Perform the described action on live environment
- Compare result with expected outcome
- Record: tool used, step performed, result
- If MCP tool is unavailable — mark step as
not_verifiable, continue with remaining steps
Checkpoint: All AVP steps executed or marked not_verifiable. Proceed to acceptance criteria.
2. Acceptance Criteria Verification
Verify all acceptance criteria from user-spec and tech-spec on live environment. This catches criteria that pre-deploy QA could not verify without a live system.
- Read pre-deploy QA report (
logs/working/qa-report.json) — check deferredToPostDeploy section
- For each deferred criterion — follow the verification steps specified in the pre-deploy report
- Also re-check all acceptance criteria from user-spec and tech-spec against live behavior
- For each criterion:
- passed — verified on live environment, evidence provided
- failed — live behavior does not meet the criterion
- blocked — cannot verify due to external conditions (no data, third-party service down). Provide a concrete manual verification plan for the user: what to check, when, how
A blocked criterion requires user follow-up before the feature can count as fully verified.
Checkpoint: All acceptance criteria verified, or marked blocked with manual verification plan.
Severity Classification
- critical — verification step failed, live functionality broken, data integrity at risk
- major — works but with significant issues visible in production
- minor — cosmetic, non-functional discrepancies
Output Format
Return findings as JSON. Reason: orchestrator parses this to decide pass/fail and log findings.
{
"status": "passed | failed",
"summary": {
"totalSteps": 0,
"passed": 0,
"failed": 0,
"blocked": 0,
"notVerifiable": 0,
"criticals": 0,
"majors": 0,
"minors": 0
},
"agentVerification": [
{
"step": "Send /start to bot",
"tool": "telegram_mcp",
"status": "passed | failed | not_verifiable",
"details": "Bot responded with welcome message"
}
],
"acceptanceCriteria": [
{
"id": "US-5",
"criterion": "Titles generated with correct declensions",
"source": "user-spec | tech-spec | deferred-from-pre-deploy",
"status": "passed | failed | blocked",
"evidence": "Checked live output, generated title uses correct declension/grammar",
"manualVerificationPlan": "Only if blocked — what the user should check, when, how"
}
],
"findings": [
{
"severity": "critical | major | minor",
"title": "Bot does not respond to /start",
"expected": "Welcome message within 3 seconds",
"actual": "No response after 10 seconds",
"reproduction": "Steps to reproduce..."
}
]
}
Status decision: passed if zero criticals, failed if one or more criticals.
Guidelines
- Every finding includes concrete reproduction: steps, expected vs actual, tool output.
- If all MCP tools are unavailable — report that automated verification is not possible, suggest manual steps.
- Empty findings array = clean verification.
Final Check
Before finishing, verify:
