![[ e-networld.de ]](/img/logo.png){kind=logo}
Squad-Spec-Repository-Template
Template for spec-driven development with AI agents: a shared squad, one rule set for Claude, Codex and Copilot, and profiles for .NET, Go and Node.
Overview
The Squad-Spec-Repository-Template bundles everything a repository needs to work with AI agents: a team of fixed roles, a single rule set and the scaffolding for documentation and GitHub. It consists of a stack-neutral core plus one profile per technology stack. It is not used through GitHub’s “Use this template” button; the adopt-template skill applies it to an existing or new repository and refreshes it there later.
The squad runs through the skills squad-issue for bug fixes and squad-spec for new features. The flow: plan, challenge, security review, tests first, implementation to at least 80 % coverage, format and analyzer gate, review loop, Lead approval and finally the pull request.
CLAUDE.md for Claude Code, AGENTS.md for Codex and .github/copilot-instructions.md for GitHub Copilot are identical from their first ## heading on. The same goes for the skills create-pr, review-pr, squad-issue and squad-spec, which exist in all three environments.
Files in a target repository come in three kinds: managed files are overwritten on every refresh, marked files are rebuilt and keep their project blocks, and seed files are written once and never touched again. That keeps the core stack-neutral and means project-specific knowledge survives a refresh. Placeholders of the form {{TODO: …}} make config-check.py fail until they are filled in.