Four spec standards, one baseline, two different decisions

Description and use

The article explains how the author used AI to generate specifications in four formats and chose OpenSpec for the app (drift risk) and Spec Kit for the game (closure risk), keeping documentation current and reducing manual effort.

Problem

Side projects often lack consistent documentation, leading to drift or unfinished work. The developer needed a way to keep specs aligned with reality without excessive discipline.

Outcome

The app now stays aligned with its baseline, eliminating drift. The game maintains a single open milestone at a time, preventing endless open work. Both projects benefit from automated spec updates and reduced manual documentation effort.

Workflow

• 1. Use AI assistant to rewrite baseline spec in four formats.
• 2. Evaluate each format against project risks.
• 3. Select OpenSpec for the app (drift risk) and Spec Kit for the game (closure risk).
• 4. Augment chosen format with Constitution Check and ADR log.
• 5. Adopt spec → plan → tasks cycle with gates for the game.
• 6. Update specs automatically as new items arise, ensuring spec precedes code changes.
• 7. Record tuning parameters and decisions in the spec to avoid back‑documentation.

Evidence

I wrote the same baseline four times

Source

OpenSpec makes discipline unnecessary: the current specs are the truth

Source

Spec Kit answers that with two constraints… one open milestone at a time

Source