Specfork

Recipes for software. Fork an app spec, change what you need, and let your coding agent build it. Specs don't depend on a stack: one recipe, many implementations.

Browse: https://specfork.dev

npx specfork search booking
npx specfork resolve @specfork/scheduling

Install the command instead with npm i -g specfork, brew install specfork/tap/specfork, curl -fsSL https://specfork.dev/install.sh | sh or go install github.com/specfork/specfork/cmd/specfork@latest.

resolve (or add) writes specfork-bundle/ (the spec and everything it requires, IDs made global, overrides applied) and specfork.lock. Point your agent at specfork-bundle/BUNDLE.md, or let it fetch specs itself: claude mcp add specfork -- npx -y specfork mcp. specfork serve runs the same tools as a hosted MCP server (streamable HTTP) with anonymous daily usage counters.

• Use Specfork with your agent
• Publish a spec
• Claim a name

How it works

• Specs live in their own repos; the index stores no spec text, and the site shows open-licence specs with credit (IDX, WEB).
• Names are bound to GitHub repo and owner IDs, so a renamed repo is followed and a transferred one is frozen (REG).
• An hourly workflow crawls GitHub and publishes index.json and the site.
• resolve uses minimal version selection, pins commits in specfork.lock, and fetches files by SHA (CMP).
• Seed specs are extracted from open-source apps (EXT).

Specs: specs/README.md.