Spec-Grounded Design

Don't code an integration from memory or from docs you assume are right. Get the real spec, probe the real behavior, treat reality as truth, then design against a contract. Reverse-engineered and stale specs lag the live API — the live probe is non-negotiable.

Works with any agent that can fetch docs and run a shell. No vendor APIs of its own.

Supporting files (read when needed):

• grounding-checklist.md — what to verify live, probe patterns, reality-wins rule
• design-contract-template.md — the contract output format

Output: {SKILL_OUTPUT_DIR}/spec-grounded-design/ — see ../OUTPUT.md

Step 0 — Scope the integration

Establish (ask only if missing):