This repository uses Ground Control for requirements management and workflow automation. Run the repo lint and test gate before and after implementation work.
This repo's Ground Control project, workflow commands, SonarCloud settings, and
plan rules live in .ground-control.yaml at repo root (with the full plan
rules set under .gc/plan-rules.md). Agents read it via the
gc_get_repo_ground_control_context MCP tool, which returns the full workflow
config in a single call.
- Pass full requirement UIDs exactly as they exist in Ground Control. Do not synthesize or rewrite requirement prefixes.
- Set
ACES_REQUIREMENT_UIDwhen the branch name does not already contain a UID such asWB-001. - The required lint/test checks and hard rules are enforced by the
/implementskill through the plan rules file referenced in.ground-control.yaml— see.gc/plan-rules.mdfor the authoritative list. - Commit-time hooks are a separate contract from the committed
.pre-commit-config.yamland CI: every fresh clone must runmake hooks(scripts/install-hooks.sh) once to activate them. SeeCONTRIBUTING.md.