venhdev/zenforge

freeze-contracts

Partition system boundaries into isolated bounded contexts and freeze explicit cross-module interface contracts before changeset planning or implementation.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/venhdev/zenforge --skill freeze-contracts

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

markdown
# 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

  1. Partition domain boundaries into isolated Bounded Contexts with single data ownership.
  2. Define typed interface specifications, error models, and mock stubs for all cross-boundary traffic.
  3. Output the staged contract specification as STAGED (or report UNRESOLVED on conflicting ownership).
같은 저장소의 Skills

더 많은 Skills

모든 Skills