Product OS
Spec-as-code for product managers. A CLI, a GitHub App, and a dashboard that turn product specs into reviewable, version-controlled artifacts — specs moving through pull requests like the code they describe.
- Status
- In development
- Surfaces
- CLI · GitHub App · dashboard
- Model
- Planned open-source core, commercial layer
- Used by
- The practice that built this site
Specs decay the moment they leave the document.
A spec in a shared doc is read once and then quietly diverges from the thing it describes. Engineering solved this for code decades ago — version control, review, checks on merge — and product work never adopted it.
The result is decision debt: teams re-litigating choices because the reasoning behind them was never written anywhere durable.
The spec lives in the repo it governs.
The CLI scaffolds and lints specs. The GitHub App runs those checks on pull requests — are requirements traceable to test cases, is there an owner, has a decision log entry been recorded. The dashboard reports spec coverage and review velocity.
Because the spec sits beside the code, a change to one shows up as a diff against the other.
It is the tooling this practice already needed.
Product OS is not a hypothesis about how teams should work. It is the extraction of a working method: the specs, decision logs, and commit-time validation that govern every other product on this site.
That is also the honest limit on it. It is built for the way one operator works, and opening the core is how that assumption gets tested against everyone else's — once there is something worth opening.