feature-contract-definition SKILL.md skillA
feature-contract-definition from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/feature-contract-definition@git:20261016.c769bd8Pins git:20261016.c769bd8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/feature-contract-definition/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c769bd8, committed Oct 16, 2026
- First version recorded
- Sep 6, 2026
- Size
- 9,235 bytes
- Repository stars
- 3
- License
- Apache-2.0
Defining a versioned API, event, data, integration, security, or operational contract for a feature after its behavior is agreed and before implementation is planned. Use when callers, consumers, stored data, or operators will depend on a changed boundary and its success, failure, ownership, compatibility, and verification must be explicit. Does not choose the architecture or transport (feature-solution-analysis), record the decision (feature-decision-analysis), or implement the contract…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Feature Contract Definition ## Purpose Turn an agreed boundary change into an authoritative contract that independent producers and consumers can implement and verify without guessing. A contract describes externally observable semantics; a DTO, schema, or endpoint list without failures, ownership, and compatibility is only a shape. ## Workflow 1. **Start from accepted intent.** Trace the contract to `OBJ-*`, `BR-*`, `BAC-*`, affected `SC-*` items, and the boundary crossing in the impact map. If behavior is still disputed, return to the responsible Product or Engineering stage for that decision. Reuse existing repository/session references and accepted revisions; do not invent IDs or require a new dossier merely to draft a contract. Record missing mappings explicitly and continue unaffected surfaces. Inspect existing decisions, specifications and consumer evidence before asking. If a material gap remains, state the competing observable outcomes and ask the accountable role which is required; keep the dependent clause provisional instead of silently choosing a guarantee. …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/feature-contract-definition@sha256:04bcb3a8c0266b81The line at the top of this page pins the label git:20261016.c769bd8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gn32oary6vfl4oy7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c769bd8 latest | 2026-10-16 | c769bd8 | 9,235 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 7,357 B | A | view · diff |
| git:20260923.832673e | 2026-09-23 | 832673e | 7,020 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 6,647 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 6,464 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9235 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gn32oary6vfl4oy7 GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/feature-contract-definition GET https://markdownregistry.com/api/v1/blob/04bcb3a8c0266b8119eacb6334885c725903fc5c898474a29d14204879ee8ddd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.