About · OpenSpec Spec Generator

About this site

The short version: this is a one person site. It was built by an independent developer, it has no company behind it, and it does two things. It generates OpenSpec change proposals in your browser, and it publishes field notes about what actually breaks when you run spec driven development with AI coding agents.

The generator takes a project name, a feature name and one sentence of requirement, and writes out four files in the OpenSpec layout. It runs entirely in your browser. It calls no model and uploads nothing.

The field notes are the reason the site exists. They are written from things that go wrong in practice, with the error text reproduced exactly, and every number attributed to whoever reported it.

What the generator actually produces

Four files, in the layout the OpenSpec project expects:

openspec/changes/<feature>/proposal.md
openspec/changes/<feature>/specs/<feature>/spec.md
openspec/changes/<feature>/design.md
openspec/changes/<feature>/tasks.md

Each one is a filled in template with the parts you still have to write marked as TODO, not invented for you. You copy them or download them from the page. The files are built in your browser and handed to you directly, which is why nothing you type leaves your machine.

It does not call an AI model. If you want the prose to be better than a template, you edit it yourself or hand it to an agent afterwards.

Who makes it

This site is made by an independent developer. One person, no company, no staff, no investors. The name on the site is the name of the thing it generates for, not an organisation.

It is not affiliated with, funded by, or endorsed by any of the tools written about here, including the OpenSpec project, GitHub Spec Kit, AWS Kiro, and Anthropic Claude Code. Those are covered because people using them hit the problems described, not because of any relationship.

What is on it

Page	What it is
Home	The generator, plus a short FAQ
Spec driven development	What the workflow is, four failure modes with the exact text they produce, and a downloadable failure matrix
Spec Kit	What init puts on your disk, five ways init fails, and a preflight worth running first
Kiro	Where the first hour breaks on Windows, and a first hour that finishes
Claude Code skills	Why a skill installs and never fires, and the setup that fixes it

How the field notes are written

Four rules, applied to every page:

Error text is reproduced as it appeared. Version numbers, commands and file paths are not paraphrased. If a string was printed with a typo, the typo is in the page.
Numbers carry a date and a source. Each page has a table saying which day something was reported, who reported it, and what the number was. Figures a vendor published about itself are labelled vendor reported. Figures one person measured on their own machine are labelled self reported.
None of it is a benchmark. A trigger rate or a CPU reading measured on one machine is one measurement. It is not a rate, and the pages say so.
Claims get checked before they go up. Commands and parameters are checked against the official source. Issue numbers are checked against the tracker for their state and their dates. Where a claim turned out to be wrong, the page says what the correct version is rather than quietly dropping the number.

Every field notes page also ships its failure matrix as a real CSV file on this site, with a plain link you can click or curl, rather than a button that assembles something in your browser.

What this site is not

Not official documentation. If you are looking for how a tool is meant to be used, read that tool's own docs. These pages are about what happens when it does not go to plan.
Not a benchmark or a review site. Nothing here is scored or ranked, and no page tells you which tool to pick.
Not a product. There is no account, no login, no payment, and no mailing list. There is no advertising on the site today.
Not finished. Pages get corrected when something in them is wrong, and the correction is written into the page rather than silently applied.

Corrections are welcome. The contact page carries the address to send them to.