Repository navigation
FAQ
Why is there no config file?
The kit tracks no work and reads no config file. Hooks read env vars (AGENTIC_SDLC_*) and workflows read inputs. A config file would be one more thing to keep in step with the repo. See Hooks reference and CI checks.
Why is Sonnet the default model? Most agent work is well-scoped coding, and Sonnet does it at lower cost and latency. Opus is for review and architecture, where a wrong call costs more than the extra tokens. The full rule list is in AGENTS-AND-MODELS.md, which is the single source.
Hooks or CI checks: which one enforces? CI. A hook is an early warning inside one tool. A CI check runs for every provider and for people. Codex runs 3 of the 4 hooks and Claude Code runs all 4: see Install for Codex.
A hook blocked a command I need. What do I do?
Read the 1-line reason on stderr. git-denylist can be turned off with AGENTIC_SDLC_GIT_DENYLIST=0. A hook that errors fails open; it never blocks by accident.
Does the kit track my work or issues? No. 2.x did; 3.0 removed it: Migrating from 2.x to 3.0.
Using the kit
- Install for Claude Code
- Install for Codex
- Hooks reference
- CI checks
- Workflow split
- Workflow review-batch
- Agent chief-of-staff
- FAQ
Upgrading
Maintainers