# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **Movement (R1).** Build what `R1. Movement` asks for, to the numbers in `design.md`. In particular: A ship has position, heading, and velocity. Thrust adds 180 units/s² along heading, capped at 260 units/s. Turn rate is 180 degrees/s. Check: the `R1. Movement` acceptance checks pass. 3. **Shots and hits (R2).** Build what `R2. Shots and hits` asks for, to the numbers in `design.md`. In particular: A shot starts 20 px ahead of the nose, travels 420 units/s, and lives 0.7 s. Radius is 3 px. A ship is a 16 px radius. Check: the `R2. Shots and hits` acceptance checks pass. 4. **Scoring and respawn (R3).** Build what `R3. Scoring and respawn` asks for, to the numbers in `design.md`. In particular: The firer of a hitting shot gains one point. The hit ship loses a life and, 1.5 s later, spawns at a documented pad with velocity 0. Check: the `R3. Scoring and respawn` acceptance checks pass. 5. **Two-client fixture (R4).** Build what `R4. Two-client fixture` asks for, to the numbers in `design.md`. In particular: Tests start an in-process server and two clients. Each client sends input for a listed step. The server broadcasts state. Check: the `R4. Two-client fixture` acceptance checks pass. 6. **Files (R5).** Build what `R5. Files` asks for, to the numbers in `design.md`. In particular: One command runs movement, hit, and two-client tests, and writes the four screenshots. Check: the `R5. Files` acceptance checks pass. 7. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 8. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.