Spec Sync
Use this skill whenever a change affects public language/compiler behavior.
Required Sync Surfaces
- owning implementation files
- unit/integration/e2e tests
- executable examples in
examples/ - active specs in
spec/ - current-state docs such as
README.mdand the canonical reference when needed
Repository Rules
- Prefer updating the owning active doc over adding new explanation docs.
- Do not treat
spec/design/archive/as current guidance. - If the change invalidates an example, either rewrite it to remain executable or move it
to
examples/illustrative/. - If the change affects a completion claim, update the phase oracle docs and any current phase-status summary in the same change set.
Verification
Run the pre-push gate after the edits, then require applicable CI checks to pass on the pushed candidate before ready-for-review:
python3 scripts/gate.py --fastpython3 scripts/gate.py --validation is optional for troubleshooting or additional local
validation. It is not a per-PR requirement and does not replace a named acceptance
oracle or manual gate.