agentsclimarketplace

Contract first

Skill kreek/consult/plugin/skills/contract-first

Engineering quality focused skills for AI coding agents that keep humans in the loop.

Install
npx -y skills add kreek/consult --skill contract-first

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when caller-facing interfaces or shared structure need approval before implementation.

SKILL.md

3.9 KB, as published. Nobody here has run it

Contract First

Iron Law

CALLER-FACING INTERFACES AND SHARED STRUCTURE MUST BE APPROVED BEFORE IMPLEMENTATION.

When to Use

  • A task defines or materially changes a caller-facing interface or shared structure: exported function, public type, HTTP endpoint, CLI/env/config surface, event payload, file format, database schema, migration step, package/module boundary, the public surface of a significant new module or component, project layout, or cross-component contract.
  • A manual or installed Interface Design Gate asks for current interface, proposed interface, boundary reason, and user decision.
  • Reviewing whether implementation started before contract approval.

When NOT to Use

  • Purely internal helper changes with no caller-facing or shared boundary outside the helper.
  • Local file moves, private implementation organization, or refactors that do not create a package/module boundary future work will depend on.
  • Typos, formatting, comment-only edits, or docs-only changes with no contract effect.
  • Broad routing and skill selection; use workflow.
  • The broader approach or solution direction is still unsettled; settle it in specify first.

Core Ideas

  1. A contract is any shape concrete enough that another caller, process, service, user, migration step, package, or future module will depend on it.
  2. Contract-first designs that concrete contract and gets it approved before implementation. Working out the actual signatures, types, and shapes is this skill's job.
  3. Approval covers the named shape only. Compatibility, rollout, renames, removals, and shims need their own explicit decision.

Workflow

  1. Stop before implementation lands. Do not write source, migrations, or config that commit the boundary until approval is recorded.
  2. Name the current shape. Cite file/line evidence, or state "new interface" or "new structure" for greenfield work.
  3. Propose the new shape. Show the concrete signature, type, endpoint, CLI/env/config surface, event payload, schema, migration step, file format, package/module boundary, or project layout future work will bind to.
  4. Explain the boundary. State why it belongs here, what owns each side, and the key tradeoff in the recommended option.
  5. Separate compatibility. For public renames or removals, ask for a breaking change, alias/shim, deprecation path, or old surface retained.
  6. Record the decision. List each proposed surface (signature, flags, schema, event payload, file format, or output shape) with its evidence, state the compatibility impact, and get one approve/revise/reject. An approving design or RFC is not this approval; this list is. Silence is not approval.
  7. Implement only the approved shape. If implementation discovers a materially different contract, reopen the gate.

Verification

  • The current interface or structure is named with evidence, or marked as new.
  • The proposed shape is concrete enough for callers or future modules to bind to.
  • Boundary ownership and compatibility decisions are explicit.
  • The proposed interfaces were listed for the user, who approved, revised, or rejected them before implementation landed.
  • Implementation matches the approved shape, or the gate was reopened.

Optional Runtime Backstop

Some Consult installations include the manual Interface Design Gate runtime. Use /consult:contract [intent] to start it when available.

Handoffs

  • workflow: broad routing.
  • specify: unsettled approach or solution direction.
  • api, database, async-systems, security: domain boundary risks.
  • architecture: shared package/module/project structure.
  • proof: prove the approved interface at the handoff where callers cross it; an approved contract without seam proof is unproven.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.