kata-verify-work

<objective> Validate built features through conversational testing with persistent state. <context> Phase: $ARGUMENTS (optional) - If provided: Test specific phase (e.g., "4") - If not provided: Check for active sessions or prompt for phase <process> 1. Check for active UAT sessions (resume or start new) 2. Find SUMMARY.md files for the phase 3. Extract testable deliverables (user-observable outcomes) 4. Create {phase}-UAT.md with test list 5. Present tests one at a time: - Show expected behavior - Wait for plain text response - "yes/y/next" = pass, anything else = issue (severity inferred) 6. Update UAT.md after each response 7. On completion: commit UAT.md 7.5. Finalize changes (pr_workflow only) — commit fixes, push, mark PR ready 7.6. Run PR review (pr_workflow only, optional) — offer automated review 7.7. Handle review findings — fix issues or add to backlog 8. If issues found: - Spawn parallel debug agents to diagnose root causes - Spawn kata-planner in --gaps mode to create fix plans - Spawn kata-plan-checker to verify fix plans - Iterate planner ↔ checker until plans pass (max 3) - Present ready status with `/clear` then `/kata-execute-phase` </process>

1. Check for uncommitted changes:
   bash

   git status --porcelain

2. If changes exist, stage and commit them:
   bash

   git add -u
   git commit -m "fix({phase}): UAT fixes"

3. Push to branch:
   bash

   BRANCH=$(git branch --show-current)
   git push origin "$BRANCH"

4. Check if PR exists:
   bash

   PR_NUMBER=$(gh pr list --head "$BRANCH" --json number --jq '.[0].number' 2>/dev/null)

5. If PR exists, mark ready (if still draft):
   bash

   gh pr ready "$PR_NUMBER" 2>/dev/null || true
   PR_URL=$(gh pr view --json url --jq '.url')

PR_WORKFLOW=$(cat .planning/config.json 2>/dev/null | grep -o '"pr_workflow"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "false")

• header: "PR Review"
• question: "Run automated PR review before team review?"
• options:
  • "Yes, run full review" — Run kata-review-pull-requests with all aspects
  • "Quick review (code only)" — Run kata-review-pull-requests with "code" aspect only
  • "Skip" — Proceed without review

1. Invoke skill:

   Skill("kata:review-pull-requests", "<aspect>")

2. Display review summary with counts: {N} critical, {M} important, {P} suggestions
3. STOP and ask what to do with findings (see step 7.7)

• header: "Review Findings"
• question: "How do you want to handle the review findings?"
• options (show only applicable ones):
  • "Fix critical issues" — (if critical > 0) Fix critical, then offer to add remaining to backlog
  • "Fix critical & important" — (if critical + important > 0) Fix both, then offer to add suggestions to backlog
  • "Fix all issues" — (if any issues) Fix everything
  • "Add to backlog" — Create issues for all findings without fixing
  • "Ignore and continue" — Skip all issues

1. Fix each critical issue
2. If important or suggestions remain, ask: "Add remaining {N} issues to backlog?"
   • "Yes" → Create issues, store TODOS_CREATED count
   • "No" → Continue
3. Commit and push fixes
4. Continue to offer_next

1. Fix each critical and important issue
2. If suggestions remain, ask: "Add {N} suggestions to backlog?"
   • "Yes" → Create issues, store TODOS_CREATED count
   • "No" → Continue
3. Commit and push fixes
4. Continue to offer_next

1. Fix all critical, important, and suggestion issues
2. Commit and push fixes
3. Continue to offer_next

1. Create issues for all findings using

   /kata-add-issue

2. Store TODOS_CREATED count
3. Continue to offer_next

1. Continue to offer_next

• Don't use AskUserQuestion for test responses — plain text conversation
• Don't ask severity — infer from description
• Don't present full checklist upfront — one test at a time
• Don't run automated tests — this is manual user validation
• Don't fix issues during testing — log as gaps, diagnose after all tests complete </anti_patterns>

---

• header: "PR Ready for Merge"
• question: "PR #{pr_number} is ready. Merge before continuing to next phase?"
• options:
  • "Yes, merge now" — merge PR, then show completion
  • "No, continue without merging" — show completion with PR status

gh pr merge "$PR_NUMBER" --merge --delete-branch
git checkout main && git pull

• /kata-plan-phase {Z+1} — skip discussion, plan directly
• /kata-execute-phase {Z+1} — skip to execution (if already planned) {If PR_WORKFLOW and not MERGED: -

  gh pr view --web

  — review PR in browser before next phase}

---

• header: "PR Ready for Merge"
• question: "PR #{pr_number} is ready. Merge before completing milestone?"
• options:
  • "Yes, merge now" — merge PR, then show completion
  • "No, continue without merging" — show completion with PR status

gh pr merge "$PR_NUMBER" --merge --delete-branch
git checkout main && git pull

• /kata-complete-milestone — skip audit, archive directly {If PR_WORKFLOW and not MERGED: -

  gh pr view --web

  — review PR in browser before audit}

---

• cat ${PHASE_DIR}/*-PLAN.md — review fix plans
• /kata-plan-phase {Z} --gaps — regenerate fix plans

---

1. Provide guidance for fix planning
2. Manually address blockers
3. Accept current state and continue

• /kata-plan-phase {Z} --gaps — retry fix planning with guidance
• /kata-discuss-phase {Z} — gather more context before replanning

• UAT.md created with tests from SUMMARY.md
• Tests presented one at a time with expected behavior
• Plain text responses (no structured forms)
• Severity inferred, never asked
• Batched writes: on issue, every 5 passes, or completion
• Committed on completion
• If issues: parallel debug agents diagnose root causes
• If issues: kata-planner creates fix plans from diagnosed gaps
• If issues: kata-plan-checker verifies fix plans (max 3 iterations)
• Ready for

  /kata-execute-phase

  when complete </success_criteria>