unity-to-spec
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know
Process
-
Explore the repo to understand the current state of the codebase if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
-
Sketch out the EditMode, PlayMode, player-build, and human-playtest seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
- EditMode for deterministic code that does not require a running scene.
- PlayMode for Unity lifecycle or engine integration.
- Player-build smoke tests for platform-sensitive behavior
- Human playtests for feel, visuals, audio, and usability.
Check with the user that these seams match their expectations.
- Write the spec using the template below and save it to
docs/<feature-name>/SPEC.md.