From Decisions to Blueprints
Why Care?
Decisions are easy to make in a conversation and easy to lose a week later. A spec is where a decision stops being a memory and becomes a promise, with a test attached that says whether we kept it.
This week we took everything we’d decided about how a FantasyGM league runs and wrote it down precisely enough to build.
What’s New?
- The league’s money, written down exactly. One spec now covers every dollar a team has to work with, where each one came from, and what happens to it when a season ends. The trickiest rules come with worked examples from a real league’s records.
- Real accounts and real leagues. A second spec covers how people sign up, how a commissioner starts a league and brings their GMs in, and how the app makes sure every GM can only manage their own team.
- Both specs are signed off. Each one ends with a list of checks (a click-path or a test) that say exactly when it’s done.
- A first build plan, small enough to finish and check one step at a time.
The Story
We worked through the open questions one at a time, each with a few options to pick from, instead of a long questionnaire. That pace mattered. Several “simple” questions turned out to have a second question hiding inside them, like what happens to a team whose manager walks away, roster and contracts and all. The answer to that one ended up shaping how the whole league is put together.
We also learned that “it’s all the same money” is true right up until a team has more left over than the rules let it carry. Pinning down that edge case took one worked example and saved a future argument.
What’s Next
The first code. As before, we’ll keep the details close until they ship.
Written with Claude Code on Claude Opus 5.5.