Skip to content
Back to skills

Design Child Contract

ASecurity

Compare 2-3 materially different child-level contract/interface shapes and write the chosen direction into `CONTRACT_DECISION.md` before planning when local contract shape is ambiguous.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
businessapi

Works with

  • api

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add siarhei-belavus/agent-public --skill design-child-contract --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Design Child Contract?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Design Child Contract
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/siarhei-belavus-design-child-contract/badge)](https://www.skillsdirectory.com/skills/siarhei-belavus-design-child-contract)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: design-child-contract
description: Compare 2-3 materially different child-level contract/interface shapes and write the chosen direction into `CONTRACT_DECISION.md` before planning when local contract shape is ambiguous.
---

# design-child-contract

Use only when the child owns an ambiguous API/config/storage/hook/module contract.

## Read first
- `../references/task-packet-contract.md`
- `../references/final-state-authoring-policy.md`
- child `INDEX.md`, `BRIEF.md`, `PLAN.md`, `AMENDMENTS.md`, `ARTIFACT_CANDIDATES.md`
- relevant parent initiative files referenced by the child brief
- `../../references/communication-mode.md`

## Workflow
1. Generate 2-3 materially different contract shapes.
2. Compare them on simplicity, coupling, flexibility, validation fit, and misuse risk.
3. Choose one direction explicitly.
4. Write `CONTRACT_DECISION.md` with the chosen direction, rejected alternatives, and rationale.
5. Update child `INDEX.md` to `Packet phase: contract_decided`.

## Writing rule
Write the chosen contract as the current local design decision.
Do not preserve competing contract vocabularies inside the canonical child packet after the decision is made.

## Do not
- write implementation code
- leave the contract decision implicit in chat only
- create contract churn when the packet already has a clear contract surface

## Communication
Honor active caveman mode for user-facing replies per `../../references/communication-mode.md`. Keep durable artifacts normal unless the human asks otherwise. Drop caveman for safety/clarity when needed, then resume.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in business →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.