Core Concept
Phase Discipline
Every feature progresses through enforced phases. No shortcuts.
SPEC
RFC must be normative locked
IMPL
Code must match spec locked
TEST
Tests must pass gates locked
STABLE
Bug fixes only locked
No shortcuts. No going back.
Capabilities
What govctl Does
RFC Management
Create, track, and enforce Request for Comments documents as the source of truth for all features.
ADR Tracking
Architectural Decision Records with explicit consequences and traceability.
Work Items
Tasks linked back to governance artifacts. Every change is authorized by a spec.
Phase Gates
Enforce spec → impl → test → stable progression. No shortcuts.
Validation
Continuous checks ensure code matches specifications. Drift is detected instantly.
AI Integration
Works with any shell-capable AI agent. Claude, Cursor, Codex—all supported.
Reference
CLI Commands
Validation
check
govctl check
✓ All 12 RFCs valid
✓ All 8 ADRs valid
✓ All 5 work items valid
Listing
list
govctl rfc list
govctl adr list
govctl work list
Creating Artifacts
new
govctl rfc new "Feature Title"
govctl adr new "Decision Title"
govctl work new "Task Title"
Lifecycle
lifecycle
govctl rfc finalize RFC-0001 normative
govctl rfc advance RFC-0001 impl
govctl rfc advance RFC-0001 stable
Fit
Who This Is For
Good Fit
- Teams frustrated by AI "code now, think later" patterns
- Projects where specifications drift from implementations
- Organizations needing audit trails for AI-generated code
- Developers who believe discipline enables velocity
Not For
- "Move fast and break things" workflows
- Projects without review processes