PRODUCTSPEC: 60 GITHUB STARS!
The ProductSpec open source project has crossed 60 GitHub stars within 2 days of launch. Obviously, this is tiny compared to mega-repos that get 10,000 stars within a day. But it's a great start and I'm very excited.
Thank you to everyone who starred it, read it, shared it, opened issues, and pushed on the thinking.
Even more exciting: 5+ companies are already using it, including a $10B+ public company.
That last part matters more than the stars.
The original idea was simple: the classic PRD needs to evolve.
Software used to be bottlenecked by implementation. Now AI agents can turn instructions into code much faster than teams can decide what should be built.
That shifts the bottleneck upstream.
The hard problem is intent.
-- What problem are we solving?
-- What is the hypothesis?
-- What is in scope?
-- What must be true before launch?
-- How will we know whether this mattered after launch?
-- What happens when the implementation drifts from the original intent?
ProductSpec is an open standard for that layer: software intent before implementation.
Over the last couple of days, we've added a lot to the open source repo:
• A before-and-after example: loose PRD to ProductSpec
• Adoption levels for teams getting started
• A repo starter kit for storing specs beside code
• A GitHub Action for validating ProductSpec files in CI
• More real examples: AI-agent handoff, platform migration, AI support triage, internal APIs
• A ProductSpec vs. PRD / Jira / Git / Figma / OpenSpec / Spec Kit guide
• Decision Trace: a companion standard for recording decisions, drift, revisions, outcomes, and learnings
The deeper insight is this:
A Product Spec should not be a one-time planning doc.
It should be the durable control file for the work.
Humans can read it.
AI agents can execute against it.
Teams can review it in Git.
Tickets can link to it.
Engineering specs can compile from it.
Decision Traces can record how intent changed after reality pushed back.
That is the direction software development is heading.
ProductSpec is still early. The spec will get better only if more builders, PMs, founders, engineers, designers, and product leaders pressure-test it against real work.
If you care about the future of software development, please star the repo, try it on one consequential project, and contribute an example or issue.
ProductSpec is open source, portable, and broadly owned by the builders who use it.