Run any Skill in Manus with one click

contract-impact

Stars4

Forks2

UpdatedJuly 20, 2026 at 02:31

Classify a bigname request or diff before coding. Use whenever work may affect public API semantics, coverage or exhaustiveness, shared IDs or enums, manifests, migrations, work ownership, `crates/domain`, replay behavior, upstream citations, or consumer replacement/parity.

Installation

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.

Run Skill in Manus

Source

ensdomains

ensdomains/bigname

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	contract-impact
description	Classify a bigname request or diff before coding. Use whenever work may affect public API semantics, coverage or exhaustiveness, shared IDs or enums, manifests, migrations, work ownership, `crates/domain`, replay behavior, upstream citations, or consumer replacement/parity.
metadata	{"kind":"playbook"}

Contract Impact

Decide whether the work is implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, or upstream-citation work.

Read only what is needed

API or coverage: docs/api-v1.md, docs/api-v1-routes.md, docs/consumer-capabilities.md
Identity or shared IDs: docs/adrs/0002-surface-resource-identity.md
Storage, migrations, replay: docs/storage.md, docs/projections.md, docs/execution.md
Manifests or authority: docs/manifests.md
Upstream claims: AGENTS.md § Upstream anchors, .refs/MANIFEST.toml, docs/upstream.md
Ownership: docs/internal/workstreams.md

Output

Produce a short note:

class: one of implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, upstream-citation
docs_or_artifacts: exact docs, OpenAPI, fixtures, manifests, or migrations that must move with the change
owner: owning boundary or directory
blockers: unresolved semantic questions or required upstream citations
communication: confirm changed docs, comments, and writeups introduce no undefined project-specific term — link docs/glossary.md on first use instead of re-defining, add necessary new coinages there in the same change, and qualify bare "promotion"/"profile" in prose; wire field names and enum values are contract, not prose (AGENTS.md § Communication)

Rules

Public behavior, coverage meaning, shared IDs/enums, manifest schema, source authority, replay semantics, or replacement meaning require docs in the same change.
ENSv1, ENSv2, and Basenames behavior claims require pinned .refs/ citations; unsupported claims must not be written.
Hard-stop if the change would make adapters write projections, API read raw facts for normal reads, execution depend on adapter internals, or unsupported behavior become implicit.

More from this repository

same repository

verify-loop

ensdomains/bigname

User-invoked only bigname verification loop. Use only when the user explicitly invokes `$verify-loop` or asks to run the verify loop after Codex has implemented work; it spawns `verification_reviewer`, triages findings, confirms real issues with failing tests or checks, fixes them, and repeats until the reviewer is clean or all findings are rejected.

2026-07-204

consumer-slice

ensdomains/bigname

Scope or implement one end-to-end bigname consumer capability. Use when work maps a first-party or public capability to routes, projections, execution behavior, manifests, tests, rollout criteria, or any parity/replacement claim.

2026-05-184

manifest-authority

ensdomains/bigname

Plan or review bigname manifest authority, source-family admission, discovery edges, capability flags, proxy tracking, start-block provenance, watch-plan effects, or manifest-driven invalidation behavior.

2026-05-184

replay-safety

ensdomains/bigname

Review bigname raw facts, normalized events, canonicality, projection rebuilds, reorg repair, invalidation, execution artifacts, migrations, and storage-family write ownership.

2026-05-184

upstream-evidence

ensdomains/bigname

Gather pinned `.refs/` evidence for ENSv1, ENSv2, Basenames, admitted app metadata, reference-indexer comparisons, or reference execution-client comparisons. Use when docs, manifests, tests, comments, or task output make upstream behavior claims or when a change may introduce a divergence.

2026-05-184

name	contract-impact
description	Classify a bigname request or diff before coding. Use whenever work may affect public API semantics, coverage or exhaustiveness, shared IDs or enums, manifests, migrations, work ownership, `crates/domain`, replay behavior, upstream citations, or consumer replacement/parity.
metadata	{"kind":"playbook"}

Contract Impact

Decide whether the work is implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, or upstream-citation work.

Read only what is needed

API or coverage: docs/api-v1.md, docs/api-v1-routes.md, docs/consumer-capabilities.md
Identity or shared IDs: docs/adrs/0002-surface-resource-identity.md
Storage, migrations, replay: docs/storage.md, docs/projections.md, docs/execution.md
Manifests or authority: docs/manifests.md
Upstream claims: AGENTS.md § Upstream anchors, .refs/MANIFEST.toml, docs/upstream.md
Ownership: docs/internal/workstreams.md

Output

Produce a short note:

class: one of implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, upstream-citation
docs_or_artifacts: exact docs, OpenAPI, fixtures, manifests, or migrations that must move with the change
owner: owning boundary or directory
blockers: unresolved semantic questions or required upstream citations
communication: confirm changed docs, comments, and writeups introduce no undefined project-specific term — link docs/glossary.md on first use instead of re-defining, add necessary new coinages there in the same change, and qualify bare "promotion"/"profile" in prose; wire field names and enum values are contract, not prose (AGENTS.md § Communication)

Rules

Public behavior, coverage meaning, shared IDs/enums, manifest schema, source authority, replay semantics, or replacement meaning require docs in the same change.
ENSv1, ENSv2, and Basenames behavior claims require pinned .refs/ citations; unsupported claims must not be written.
Hard-stop if the change would make adapters write projections, API read raw facts for normal reads, execution depend on adapter internals, or unsupported behavior become implicit.