Execute end-to-end playtesting of the D&D 5E game using the embedded MCP server. Use this skill when the user says "let's playtest", "test our fix", "qa the game", "playtest this", "test the game", or wants to verify game functionality through actual gameplay. When working on a ticket, focuses testing on the specific functionality being addressed.
QA the D&D 5E game by playing it as a human player would, using the embedded MCP server.
Start the game with MCP enabled:
uv run dnd-2d --mcp
| Tool | Usage |
|---|---|
game_state() | Get ASCII map + JSON state |
game_move(direction) | Move "north"/"south"/"east"/"west" |
game_attack(target_index) | Attack enemy by 0-based index (0=A, 1=B, etc.) |
game_wait() | Wait/pass turn in combat |
If working on a ticket/issue, identify the specific functionality to test. Read the ticket to understand:
game_state() → Observe initial state
Move systematically to reach the area/feature being tested. For ticket work, navigate to where the bug/feature manifests.
Perform actions to exercise the functionality:
After each action, check game_state() for:
When a bug is found:
Create a GitHub issue immediately:
gh issue create --title "Bug: [brief description]" --body "[details]"
Include in the issue:
Severity decision:
Exploration test: Move in all directions, reveal full map, check fog of war
Combat test: Find enemy, attack until resolved, verify HP changes and death
Boundary test: Try invalid moves (into walls), verify rejection
State persistence: Check that position/HP persist across turns