Implement SGD
RepoSentry turns the SGD methodology into concrete artefacts and automated checks inside your existing repositories. You adopt incrementally — none of this requires a rewrite.
Capability model
RepoSentry infers a capability model from your repositories — grouping repos and code into capabilities and features, so you have a living map of what you actually have. You curate it (accept, rename, merge), and it becomes the backbone of traceability: every feature spec, PR check, and metric hangs off it.
Feature specs
Capabilities are decomposed into features, each with acceptance criteria expressed as executable scenarios (Gherkin). This is the heart of "govern the spec, not just the code" — the spec exists first, and code is measured against it. RepoSentry tracks which acceptance criteria are covered by tests and merged code, and which are still spec-only.
Golden-path templates & policies
Define the golden path for your org — the standards a repository or change is expected to follow — and attach compliance policies. RepoSentry uses these as the yardstick for PR checks and remediation, so "our standards" stop being tribal knowledge and become enforced configuration.
PR checks
On every pull request, RepoSentry scores the change against your standards and the relevant specs, and reports back as a status check — before review, not after. Tiered gates mean routine changes pass automatically while high-impact ones get flagged for a human.
Remediation
Where a repository drifts from the golden path, RepoSentry can open a remediation pull request with the fix, so closing the gap is one click rather than a backlog ticket. Nothing is changed without a PR you approve.
How adoption grows
- Connect a repo and accept the inferred capability model.
- Turn on PR checks for the standards that matter most.
- Add feature specs for new work so the spec leads the code.
- Expand to more repos as the team sees the value.
Once it's running, switch to Observe adoption to measure how well it's landing.