Assignment

[Pavan-Everest]

Summary

This PR adds Spec Kit documentation for the full Scribble multiplayer game flow across four feature specs. Together, these specs define the intended behavior from room creation through round results and restart.

Specs Included

001 - Room Setup and Lobby

• Create and join rooms with unique room codes
• Assign the room creator as Host
• Validate empty, invalid, and non-existent room codes
• Keep room state isolated per room
• Sync lobby state through HTTP polling
• Restrict Start Game to the Host when enough players are present

002 - Round Start Setup

• Trim and validate player names
• Reject empty or whitespace-only names
• Assign the first drawer using Host-first behavior
• Select the secret word deterministically from the starter word list
• Reveal the secret word only to the assigned drawer

003 - Round Play and Scoring

• Support drawer-only freehand drawing and canvas clearing
• Persist drawing state with colors and stroke sizes
• Validate and trim guesses
• Compare guesses case-insensitively
• Sync guess history and scores through polling
• Award 100 points once per guesser for their first correct guess
• Reject late joins during active rounds

004 - Round Results and Restart

• Show correct word, final scores, and complete guess history when a round ends
• Keep result state consistent and final across clients
• Prevent drawing, clearing, guessing, and joining while results are displayed
• Allow only the Host to restart
• Return current players to the lobby on restart
• Preserve membership and Host identity
• Reset round-specific state before the next game

Artifacts Added

• Feature specifications
• Quality checklists
• Implementation plans
• Research notes
• Data models
• OpenAPI contracts
• Quickstart validation guides
• Task lists where generated

Validation

• Spec Kit quality checks completed for generated specs
• Planning artifacts align with project constraints:
  • TypeScript and ES Modules
  • Express backend and React/Vite frontend
  • In-memory state only
  • HTTP polling only
  • No WebSockets, databases, auth, sessions, or unrelated dependencies
• Ran cross-artifact analysis for 004-round-results-restart; no critical issues found

Notes

This PR focuses on specification and planning artifacts. The actual gameplay implementation remains the next phase and should follow the generated task lists.

Contributor

• Email: pavankumar.rao@everest.engineering
• Role:
  • Product
  • Developer