Templates
Two kinds of starting point. Workflow templates are a built-in workflow and a first task: pick one and it opens in your workspace, ready to start. Document templates are policies and checklists for teams that ship AI-written code: read them here, or download them as Word or Markdown and make them yours.
Workflow templates
Plan
- Architecture decision: two designs, a critic and an ADR
Settle a design question with Architecture Debate: two Architect proposals, a Reviewer critique and a final synthesis, saved as a proposed ADR for a person.
- Feature spec: requirements and a phased delivery plan
Turn a one-line request into acceptance criteria and a phased plan with Discovery & Spec: a Researcher, a Product Analyst and a Project Planner, then a review.
Build
- Full-stack feature: requirements to user docs in one session
Feature SDLC runs eight agents in order, from requirements and design to backend, frontend, E2E scenarios, security review and docs, then tests and approval.
- Monorepo: cost-capped multi-agent refactor
Refactor one package of a monorepo with Plan, Build, Review & Test, under a workspace budget and a per-workflow cap, with tests scoped to the package changed.
Review
- Next.js PR: three reviews, your tests and a CI release check
A Next.js change reviewed for correctness, security and test coverage by Parallel Review, tested with your own suite, then checked again from CI before merge.
- Weekly codebase inspection on a schedule
Schedule Swarm Inspection to sweep one module every week: reviewer, security and tester slices merged into one summary, plus a fix for the worst issue it finds.
Test
- Python service: tests first, with a coverage floor in CI
Write missing pytest tests with Quality-Gated Change, record coverage from pytest-cov in the sandbox, and have CI deny the merge below an 80% coverage floor.
- Release candidate: E2E sanity, dependency audit and go/no-go
Run Release Readiness before a release: correctness, security, E2E scenarios and a dependency audit, then an Architect's go/no-go written to your release notes.
Secure
- Python service: SBOM and license gate
Audit a Python service's dependencies for copyleft licenses with Dependency Refresh, record a CycloneDX SBOM, and have CI deny releases that ship GPL code.
- Auth change: risk analysis before the code, audit after
Change auth code with Security-Sensitive Change: a risk analysis before it is written, a security audit after, your tests, and a CI gate on medium findings.
Deploy
- Next.js app: gated staging deploy, then production
Build a Next.js UI change with UI Implementation, merge it through the gate, call your staging deploy webhook, and release to production only after staging.
- Infrastructure change: risk review, with production off limits
Change Kubernetes manifests with DevOps Change: a plan, a security risk review and validation, under policy rules that keep sessions away from production.
Document templates
Policy
- AI coding policy template for engineering teams
A ready-to-adopt AI coding policy: approved tools, data rules, what agents may do, human review, quality gates and audit records. Free as .docx or .md.
Review
- Pull request description template for AI-written changes
A pull request template for changes an AI agent wrote: the task, the tool, what was verified and what wasn't, and where reviewers should look first.
- CODEOWNERS starter for repositories with AI coding agents
A commented CODEOWNERS starter that puts named owners on the paths coding agents shouldn't change alone: CI, infrastructure, auth, migrations, dependencies.
Release
- Release checklist for teams shipping AI-written code
A release checklist in four stages, before the cut, the candidate, the deploy and after: gates, approvals, SBOM, rollback, and who signs off on each step.
Security
- Threat model template for AI coding agents
A threat model template for coding agents: what the agent can reach, where untrusted text gets in, ten threats with controls, and a table for your setup.
- Security questionnaire template for AI coding tool vendors
A fill-in security questionnaire for AI coding tools: data flow, training, retention, agent permissions, isolation, audit and incidents, with good answers.
- SBOM review checklist: what to check before you trust one
An SBOM review checklist: the NTIA minimum elements, depth and known unknowns, licenses, vulnerabilities and what changed since the last one, ready to copy.
Incidents
- Incident postmortem template for an AI-written change
A blameless postmortem template for incidents caused by AI-written changes: the task, the tool, the evidence at merge, and which review step or gate missed it.