---
id: verify-confirmed-decisions-with-subagents
trigger: "after implementing decisions that the user and Codex explicitly confirmed"
confidence: 0.9
domain: "workflow"
source: "user-directive-2026-08-12"
---

# Verify Confirmed Decisions With Subagents

## Action

After implementing explicitly confirmed discussion decisions, assign subagents to check every confirmed item against the specification, code, tests, migrations, and user-facing behavior. Report each omission and resolve it before claiming completion.

Do not ask the user to approve every verification item. Use the confirmed decisions as the review checklist.

Use milestone-based batch reviews instead of fragmented "find one, fix one, review again" loops:

1. **Design review before implementation**: give each subagent the same frozen, complete specification and a distinct review scope. Require each reviewer to finish its whole checklist and return all Critical/Important findings in one report, even after finding a blocker.
2. **Implementation review after a complete milestone**: first compile and run the relevant tests, then freeze the workspace snapshot. Have subagents review the complete implementation and collect findings in one consolidated issue list. Batch-fix the list instead of interrupting implementation for every incoming finding.
3. **Final confirmation before delivery**: after all fixes and verification pass, have each relevant subagent confirm its previously reported items and state whether the final snapshot has any remaining Critical/Important issues.

For an ordinary localized fix, only the subagent that raised the issue performs a targeted confirmation. Repeat a full multi-subagent review only when a fix materially changes a payment/refund state machine, database uniqueness or transaction boundary, external financial side-effect ordering, order completion/cancellation/refund mutual exclusion, or when preparing final delivery.

Subagents performing a review should be read-only and should not review a workspace that is still being edited. The main agent owns consolidation, implementation, and user communication.

## Evidence

- The user explicitly required this workflow for future confirmed discussions on 2026-08-12.
- The current LINE Pay implementation must receive this item-by-item subagent verification after implementation.
- After the LINE Pay retrospective, the user explicitly required future subagent reviews to use staged, complete reports rather than repeated one-finding-at-a-time loops on 2026-08-12.
