name	monopoly-playtest-gate
description	Run a pre-tag playtest gate for Monopoly, 大富翁, releases by combining QA coverage review, simulated-player feedback, and final ship or hold recommendations.
argument-hint	Describe the milestone, branch, or release candidate to evaluate
user-invocable	true

Monopoly Playtest Gate

Use this skill when a milestone is close to release and needs a player-focused go or no-go recommendation.

Before creating a release tag or allowing CI to publish a release.
After a feature-complete milestone needs experiential validation.
When regression risk exists in gameplay clarity, pacing, or reconnect stability.

Review the implemented scope and known issues.
Ask the Monopoly QA Lead agent for the objective test gate.
- Confirm that unit, integration, and Playwright evidence are all current enough for the slice, and that Playwright is not the only meaningful regression proof.
Ask the Monopoly Simulated Player agent for experiential feedback.
Review the latest performance risk verdict when the slice affects runtime cost, long-session stability, or recovery latency.
- Use the Monopoly Full-Stack Performance Expert agent when those risks are in scope.
Reconcile the two views.
- Bugs that break rules or progression are blockers.
- Confusing ownership, turn feedback, or cash flow are release-significant even if technically functional.
Produce a ship, ship-with-risk, or hold recommendation.
Record the release gate outcome in repository workflow state.
- Mark completed roles with .github/hooks/scripts/role_rotation.py complete --role "Monopoly QA Lead" --note "<summary>" and .github/hooks/scripts/role_rotation.py complete --role "Monopoly Simulated Player" --note "<summary>".
- If a release role is intentionally skipped, record the waiver and reason instead of bypassing the gate.
Hand release facts to the versioning role.
- Use the Monopoly Versioning Manager agent before commit or release handoff so semantic version impact and changelog facts match the validated player experience.

Monopoly Playtest Gate

Use this skill when a milestone is close to release and needs a player-focused go or no-go recommendation.

When To Use

Before creating a release tag or allowing CI to publish a release.

After a feature-complete milestone needs experiential validation.

When regression risk exists in gameplay clarity, pacing, or reconnect stability.

Procedure

Review the implemented scope and known issues.

Ask the Monopoly QA Lead agent for the objective test gate.

Confirm that unit, integration, and Playwright evidence are all current enough for the slice, and that Playwright is not the only meaningful regression proof.

Ask the Monopoly Simulated Player agent for experiential feedback.

Review the latest performance risk verdict when the slice affects runtime cost, long-session stability, or recovery latency.

Use the Monopoly Full-Stack Performance Expert agent when those risks are in scope.

Reconcile the two views.

Bugs that break rules or progression are blockers.
Confusing ownership, turn feedback, or cash flow are release-significant even if technically functional.

Produce a ship, ship-with-risk, or hold recommendation.

Record the release gate outcome in repository workflow state.

Mark completed roles with .github/hooks/scripts/role_rotation.py complete --role "Monopoly QA Lead" --note "<summary>" and .github/hooks/scripts/role_rotation.py complete --role "Monopoly Simulated Player" --note "<summary>".
If a release role is intentionally skipped, record the waiver and reason instead of bypassing the gate.

Hand release facts to the versioning role.

Use the Monopoly Versioning Manager agent before commit or release handoff so semantic version impact and changelog facts match the validated player experience.

Output

Objective quality gate summary

Player-experience findings

Blocking issues

Final release recommendation

monopoly-playtest-gate