One page, every comparison. Productizer is an open-source Claude Code plugin that keeps one living spec per product in your own repository — permanent requirement ids that are never reused or renumbered, a superseded requirement that keeps its original text, every new intent classified against the whole spec as extend / refine / duplicate / contradict, and a contradiction that halts the work until a human rules on it. Below are the ten structural properties that separate it from the four tools people evaluate it beside. Structural, deliberately: these are architecture decisions that do not move with the next release, not feature counts that go stale in a month. Open any column for the full per-competitor page.
| Productizer | AI Unified Process | Entire | 8090 | Lightsprint | |
|---|---|---|---|---|---|
| One living spec per product, not per feature | ✓ | ✗one file per use case | ✗ | ✗blueprints per feature | ✗ |
| Permanent requirement ids, never renumbered | ✓ | ✗renumbered gaplessly on save | ✗ | ✓ids preserved once assigned | ✗ |
| Superseded requirement keeps its original text | ✓ | ✗ | ✗ | — | ✗ |
| Every intent classified against the whole spec | ✓ | ✗ | ✗ | ✗ | ✗ |
| A contradiction halts the work | ✓ | ✗ | ✗ | ✗ | ✗ |
| Principles layer above the requirements | ✓ | ✗ | ✗ | ✗ | ✗ |
| Artifacts live in your own repo | ✓ | ◐files, but Studio is closed | ◐checkpoints in-repo, platform hosted | ✗hosted | ✗hosted workspace |
| Nothing native to install | ✓ | ✓plugin; IDE plugin optional | ✗Go CLI + control-plane login | ✗account + GitHub App | ✗account + CLI |
| Open source end to end | ✓ | ◐Apache-2.0 plugin, closed Studio | ◐MIT CLI, closed platform | ✗engine closed | ✗main repo private |
| Free | ✓ | ◐free plugin; paid workshops and book | —no public pricing | ✗enterprise | —no public pricing |
| Learn more ↓ | The product → | Full page → | Full page → | Full page → | Full page → |
— = unconfirmed, not necessarily absent: it marks a property the vendor does not clearly document. Every cell is read from the vendor’s own public material and matches that vendor’s dedicated comparison page.
A matrix where one column is ✓ on every row is a rigged matrix, and you would be right to distrust it. The table above is narrow on purpose — it asks only how a spec is structured, which is the one question Productizer was built to answer differently. Widen the question and each of these four is ahead of us, in named, specific places. Here they are.
| Competitor | What it does better than Productizer |
|---|---|
| AI Unified Process | A working end-to-end CI lifecycle that opens real pull requests — the cleanest win on this page, and one we still have no answer to. Their format validator and their coverage audit run in CI; as of v4.2.0 we ship both mechanisms, but ours are run by hand. An eval corpus of 36 scenarios across 410 scored criteria that is actually graded, where our 26 cases have never been scored by a model. Broader editor and IDE reach. |
| Entire | Line-level provenance — entire blame and entire why map a live line of code back to the prompt that wrote it. Ours is a Productizer-Req: commit trailer, which is provenance at the commit, not at the line, and it is a claim rather than evidence. A nine-layer redaction pipeline of roughly 2,700 lines of tested Go, where we have none. Support for eight coding agents against our one. Scored merge gates that re-run on every push: we ship the runner format and a scorer you invoke, and no executor and no push trigger. |
| 8090 | A funded delivery and support organisation behind the product. A delegated review agent working across six fixed dimensions. Test-to-requirement coverage traceability that is enforced inside their platform, where ours is a textual scan for COV_ ids that cannot tell a test from a comment. A real three-layer evaluation framework with an F2-weighted score, a golden dataset and quarterly recalibration — graded, where our corpus is not. |
| Lightsprint | A gate anchored to observed GitHub evidence rather than to declarations — still the honest distinction, because v4.2.0 anchors ours to declarations plus signals collected on the local machine. Role-scoped approval that binds a non-engineer, where our hooks bind whoever is at the terminal. A published audit of their own agents’ error rate. Splitting judgment from evidence and keying it to an evidence hash is no longer a row they win alone: we now do both. |
Productizer is Claude Code only. There is no IntelliJ plugin, no VS Code extension, no support for the seven other coding agents Entire handles. Its lifecycle has not yet been exercised end to end through CI — the stages, hooks and gates run under a human driving the agent, and the unattended path is unproven. The runner format ships without an executor: templates/runners/*.json defines the contract for a scored judgment, and nothing in the repository runs one — the scorer beside it runs when you invoke it, not on every push. The eval corpus has never been graded: 26 cases load and both ablation arms configure, but claude plugin eval is early-access gated and no case has been scored by a model. The only accuracy figure we have covers the symbolic cross-check that runs beside the model classifier: 1.00 precision and 0.70 recall on 21 cases we wrote ourselves, all three misses semantic. A harder 26-case corpus scores the same checker at 0.67 precision and 0.12 recall, so the figure tracks the corpus more than the checker. That number describes the symbolic checker alone, on a small self-authored corpus — the end-to-end system’s recall is unmeasured, and nothing here should be read as “Productizer has 0.70 recall”. It is a free one-person open-source project, not a supported platform: no SLA, no support contract, no organisation behind it.
No independent third party has validated any of this — not our marks and not theirs. Every cell above is read from public material and from our own repository, by us. Where a vendor publishes its own numbers we have repeated them without re-testing them. Both sides evolve; verify specifics against current documentation before you decide anything.
Nothing on this page implies that AI Unified Process, Entire, 8090 or Lightsprint endorses, partners with, or is affiliated with Productizer or glick.run. Each name is the trademark of its owner and is used here only to identify the product being compared.