Menu
Define interface/persistence contracts (APIs, schemas, deeplinks, storage formats) + compatibility rules. Use when public surfaces or stable formats are involved.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | contract-design |
| description | Define interface/persistence contracts (APIs, schemas, deeplinks, storage formats) + compatibility rules. Use when public surfaces or stable formats are involved. |
Make interface boundaries explicit and testable. This skill can target:
Default: ${WORK_PATH}/contracts.md
If the project already uses OpenAPI/proto/schema files, ask user which format to use and where to write.
Ask:
Minimum sections (even in markdown):
Return control to Fabricator.
Use after git-tooling push to create or manage a PR on Bitbucket Server. Composes PR description, creates PR via API, handles review comments. Terminal delivery step. (5 supporting files)
Use at session start to pull Jira issue details into context, or post-delivery to create/update issues. Integrates with task-authoring (issue → task.md) and git-tooling (commit links). (2 supporting files)
Select the minimal sufficient artifact set (task/requirements/tech-spec/contracts/models/verify/evidence) for the current change, and recommend the next skills. Use after task intake or when scope/risk changes.
Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE.
Implement changes guided by existing artifacts and repo conventions (AGENTS/README/DEVELOPMENT + WORK_PATH). Make small diffs, follow coherence gate, and optionally trigger verification-run.
Model states/flows/invariants for complex behavior (async, retries, caching, offline). Use when correctness depends on state machines or non-trivial flows.
