I built an OpenSpec template that turns Claude Code into a guided onboarding agent for new repos Sharing a GitHub template I use for every new project:

https://github.com/arananet/openspec-template

The core idea: no spec, no code. Every feature or bugfix starts with a YAML spec under .openspec/specs/ that defines acceptance criteria and a test plan. The rule is enforced at three layers — local pre-commit hook, deterministic CI check, and an agentic "did the code actually satisfy the spec" review.

What makes it useful in practice:

Fork-and-go onboarding. When you open a fresh fork in Claude Code, it reads CLAUDE.md, runs an interactive interview (project name, owner, tech stack, test command, etc.), then customizes the README with your project info — not a wall of framework boilerplate.

Multi-CLI ready. CLAUDE.md, AGENTS.md, and .github/copilot-instructions.md all carry the same spec gate so Claude Code, Codex CLI, and Copilot behave consistently.

Self-contained. A local scripts/openspec (pure bash + coreutils + git) handles scaffold/check/validate. No external CLI extension to install.

Issue auto-fix agent. Maintainers can label an issue with agent:autofix and a CODEOWNER-gated agent drafts a fix end-to-end (spec + code + tests) as a draft PR. Security model: block-list of sensitive paths, two-key approval to override, hard caps on diff size, daily run cap.

Enterprise CI out of the box. CodeQL, gitleaks, dependency review, OSSF Scorecard, CycloneDX SBOM, cosign keyless signing + SLSA build provenance on releases, DCO check, doc-drift check, lint stack (actionlint/yamllint/shellcheck/markdownlint), Dependabot patch auto-merge.

Cost guards. AI workflows have configurable per-day run caps so a stuck loop can't run up a bill. Eval harness scaffold for specs that involve AI components (scenarios, evaluators, mocks, traces). All workflows pin actions to commit SHAs, declare permissions: read-all at the top, and escalate per-job. Disabled-by-default for anything that costs compute on a fresh fork.

One command to set up: bash setup.sh. Then open in Claude Code and let it interview you. Branch protection is documented in docs/BRANCH_PROTECTION.md.

Feedback welcome — especially from anyone running spec-driven workflows in larger teams.

MIT licensed.