Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/venhdev/zenforge --skill freeze-contractsAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
freeze-contracts — Boundary Partitioning & Interface Contract Locking
Domain Rubric
1. Bounded Context Isolation
Isolate domain boundaries so each context exclusively owns its datastore and internal state. Forbid direct cross-database queries or foreign entity mutations; require all cross-boundary interactions to traverse explicit Public Interfaces, Domain Events, or Anti-Corruption Layers (ACL).
2. Contract Specifications & Consumer Fixtures
Define cross-module contracts using strict typed declarations (TypeScript types, Protocol Buffers, JSONSchema, OpenAPI, or Go interfaces). Every contract must declare protocol, direction, typed command/event payloads, error models, and mock provider fixtures so downstream consumers can build independently without upstream readiness.
3. State
STAGED: Bounded contexts mapped, public interfaces frozen, and mock fixtures reviewable.UNRESOLVED: Domain boundary ambiguity or conflicting data ownership prevents clean separation.
Canonical Output Contract
# Contract Freeze: <System / Domain Slug> · <STAGED | UNRESOLVED>
Basis: <Architectural direction or domain specifications reference>
## 1. Bounded Context Topology
- Context: `<ContextName>` | Data Ownership: `<Tables / Entities>` | Public Port: `<InterfaceName>`
- Boundary Rules: <Encapsulation constraints and ACL mapping>
## 2. Frozen Interface Specifications[CONTRACT: <UpstreamContext> -> <DownstreamContext>] Protocol: <In-process Interface | REST | gRPC | Domain Event> Direction: <Sync Call | Async Event> Payload:
- Input / Command: <Typed structure or schema reference>
- Output / Event: <Typed structure or schema reference>
Invariants:
- Idempotency: <Required / Optional / N/A>
- Error Model: <Deterministic error codes and retry semantics>
## 3. Harness Stubs & Consumer Fixtures
- Mock Provider: <Repo-relative path for mock stubs or contract fixtures>
- Verification Target: <Consumer test criteria validating against this contract>
Summary: <N> contexts defined, <M> cross-boundary contracts frozen.
*(omit if clean)* Gap: <Conflicting domain ownership or ambiguous contract boundary.>Routing
- Multi-phase initiative contracts ready for living plan packaging → (via /plan-dossier).
- Greenfield plumbing verification across frozen contracts → (via /spike-skeleton).
- Large-scale refactor with frozen contracts → (via /plan-seam).
- Single-module feature with frozen contracts ready for file impact planning → (via /changeset).
- Domain boundary or schema ambiguities unresolved → (via /clarify).
Execution Protocol
- Partition domain boundaries into isolated Bounded Contexts with single data ownership.
- Define typed interface specifications, error models, and mock stubs for all cross-boundary traffic.
- Output the staged contract specification as
STAGED(or reportUNRESOLVEDon conflicting ownership).