Monopoly Multi Agent Delivery

• Use the Monopoly Senior Implementer agent for code changes and validation.

11. Build the quality gate.

• Use the Monopoly QA Lead agent to define or review unit, integration, and Playwright coverage.
• Require an explicit verdict on whether any of those layers are lagging and whether failing checks imply stale tests or business-logic regressions.

12. Review long-lived documentation impact.

• Use the Monopoly Documentation Owner agent every substantial round to decide whether README or official docs must be updated.
• Record an explicit "updated" or "checked and no changes needed" conclusion before commit.

13. Simulate the player experience.

• Use the Monopoly Simulated Player agent before tagging or declaring a milestone ready.

14. Wait for user confirmation when the change is user-facing or milestone-like.

• Treat user approval as a release or commit boundary, not as an AI specialist role.

15. Review version impact before commit or release handoff.

• Use the Monopoly Versioning Manager agent to confirm semantic version impact, commit classification, and changelog-ready release facts.

16. Start with workspace hygiene.

• Check git status before new implementation work.
• If completed agent-owned work is still uncommitted, decide whether to commit and push it before starting the next slice.
• Keep unrelated user changes out of agent commits and report them explicitly.

17. Record the workflow state after every role handoff.

• After each required role or waiver decision, run .github/hooks/scripts/role_rotation.py complete --role "<role name>" --note "<summary>" or .github/hooks/scripts/role_rotation.py waive --role "<role name>" --reason "<reason>".
• Use .github/hooks/scripts/role_rotation.py status --json before editing, committing, or preparing release work.

18. Close the loop with management reporting.

• In progress updates and the final summary, include a role-by-role account of which AI roles were used, what each one contributed, and which work remained with the main coding agent.
• If no supporting roles were used, state that explicitly.

19. Use repository-friendly commits.

• Prefer conventional commit messages with Chinese subjects when committing implementation slices.

Role Boundary Reminder

• Monopoly Documentation Owner is now an every-round governance checkpoint for substantial work.
• Monopoly Full-Stack Performance Expert is a fixed workflow role for substantial rounds, while Monopoly Pixi Scene Engineer remains a specialized opt-in role when board rendering is central.
• Monopoly Release Marketer still exists, but it remains a release and external-facing messaging role rather than an implementation-round default gate.

Output

• A recommended agent sequence
• The OpenSpec change to create or continue
• The next implementation slice
• The required validation and playtest gate
• A role-by-role execution summary suitable for manager review