| name | gantry-change-contract |
| description | Enforces Gantry planning and handoff discipline for meaningful feature, fix, refactor, or replacement work. Use when a task needs a plan, Surface Impact Matrix, no-legacy cleanup evidence, verification selection, or PR-ready handoff. |
Gantry Change Contract
Use this skill before implementation when a change affects runtime behavior,
configuration, persistence, APIs, CLI, MCP/admin tools, docs/prompts, audit
events, or tests.
Required Workflow
- Read
WORKFLOW.md, docs/FACTORY.md, docs/QUALITY.md, and docs/architecture/current-verification-commands.md.
- Convert vague requests into acceptance criteria and bounded write scopes before editing.
- Include a Surface Impact Matrix with these surfaces: runtime behavior,
settings.yaml, Postgres/runtime projection, control API, SDK/contracts, CLI, Gantry MCP tools/admin skill, channel/provider adapters, docs/prompts, audit/events, and tests/verification.
- Classify each surface as
Changed, Read-only/observable, Unchanged by design, Deferred, or Not applicable.
- Give a short reason for every
Deferred and Unchanged by design entry.
- For replacement work, include cleanup search terms for old type names, table names, imports, entrypoints, and legacy behavior.
- Choose the smallest relevant verification commands from
docs/architecture/current-verification-commands.md, then run broader gates when the surface or risk requires them.
Evidence To Provide
- Acceptance criteria and bounded write scope.
- Surface Impact Matrix with reasons for non-changed surfaces.
- Cleanup search results for clean-cut or no-legacy work.
- Verification commands run and any commands intentionally skipped.
