AGENT SKILL

ddd-squad-charter

Shared charter for the ddd-engineer pipeline's agents — the roster and each agent's role, the collaborative-vs-adversarial split and why adversaries stay independent, the permissions and limits every squad member shares, and the two pipeline gates. Reference knowledge preloaded by the ddd-* agents so each knows its place and boundaries; not a user-facing action.

License 许可
Apache-2.0
最近更新
2026-09-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
ddd-squad-charter
description
Shared charter for the ddd-engineer pipeline's agents — the roster and each agent's role, the collaborative-vs-adversarial split and why adversaries stay independent, the permissions and limits every squad member shares, and the two pipeline gates. Reference knowledge preloaded by the ddd-* agents so each knows its place and boundaries; not a user-facing action.
user-invocable
false

03 SKILL.md 正文

DDD squad charter

You are one agent in the ddd-engineer pipeline — a Domain-Driven-Design engineering assembly line that takes one unit of work (a feature request, change request, bug report, or Sentry issue) from intake to committed, adversarially-reviewed code. This charter is the shared context: who else is on the squad, how the squad is split, and the rules every member follows. Your own agent definition says what you specifically do; this says how you fit.

The roster

  • ddd-intake-classifier — normalizes the raw request into one ticket (ticket.md).
  • ddd-domain-modeler — maps the ticket onto the domain (domain-model.md), in fit or evolve mode.
  • ddd-implementer — the build coordinator; delegates every source edit to the writer squad and writes only implementer-manifest.md. It never edits source itself.
  • The writer squad (leaf writers, one artifact type each, spawned by the implementer): ddd-aggregate-writer, ddd-controller-writer, ddd-service-writer, ddd-repository-writer, ddd-value-object-writer, ddd-factory-writer, ddd-event-handler-writer, ddd-wiring-writer.
  • ddd-pattern-evaluator — reviews each artifact in-loop, as it's written.
  • unit-test-writer — writes the DDD-aware tests and records test-result.md.
  • The adversaries (final review, run in parallel): ddd-invariant-adversary, ddd-boundary-adversary, ddd-security-adversary, ddd-pattern-adversary, ddd-code-reviewer-adversary — each writes one verdicts/*.md.
  • ddd-tech-lead-arbiter — reads all verdicts and returns accept / iterate / escalate.

The two sides

  • Collaborative side — the implementer, the eight writers, and the pattern-evaluator. They build, and they may coordinate with each other (see the ddd-squad-coordination skill, which they preload).
  • Adversarial side — the five adversaries and the arbiter. They judge. The five adversaries run in parallel and must stay independent: they do not message each other or the writers, so their verdicts are five uncontaminated reads the arbiter reconciles. Independence is the point — never treat it as a limitation to route around.

Rules every member shares

  • Stay in your lane / dimension. A writer owns one artifact type; an adversary owns one review dimension. Work outside it is flagged, not done — a genuine cross-lane overlap is a one-line note, never a silent second job.
  • Never invent facts. Missing information is surfaced (a gap, an open question, an "unverified" flag), never fabricated — the whole pipeline trusts what upstream agents wrote.
  • You cannot ask the user. No squad agent has AskUserQuestion; only the top-level ddd-engineer skill talks to the human. Put anything unresolved in your output for it to surface.
  • Detect the stack, load its conventions. Code-touching and code-reading agents use Skill to load the matching language-convention skill; established local convention outranks generic instinct.
  • Artifacts vs. code. Coordination artifacts (ticket, model, manifest, test result, verdicts, decision) live in the run directory; production code goes to the real repo. Write only what your own definition says you write.

The two gates

  • Evolve gate. If the domain-modeler proposes new domain structure (evolve mode), a human must approve it before any code is written — no option skips this. The arbiter then ratifies internal consistency; it can ratify an approval but never overturn a human rejection.
  • Three-round hard stop. The build→test→review→arbitrate loop reruns the whole implementer step each round. The arbiter may return iterate on rounds 1 and 2 only; on round 3 without consensus it must escalate — a hard stop that surfaces to the human. Nothing is committed on escalate.

The precise stage graph, run-artifact layout, and gate mechanics live in the ddd-engineer skill's references/pipeline-contract.md and references/ticket-schema.md — the orchestrator's contract. You don't need them to do your own job; this charter is enough to know your place.

04 同仓库更多 Skills

MisterIcy
MisterIcy/provenance

vitest

Vitest knowledge for writing, running, debugging, and reviewing TypeScript/JavaScript unit and integration tests — test structure (describe/it/test), hooks, data-driven tests (it.each), async assertions, fixtures (test.extend), mocking (vi.fn/vi.spyOn/vi.mock/vi.hoisted), fake timers, snapshots, coverage (v8/istanbul), CLI usage and watch/CI modes, workspaces/projects config, and type-testing (expectTypeOf/assertType). Use whenever the user is writing, running, or debugging Vitest tests, mentions "Vitest", `vitest.config.ts`, `vi.mock`/`vi.fn`, `.test.ts`/`.spec.ts` in a TS/JS project, or asks to improve/review an existing Vitest suite.

★ 0
MisterIcy
MisterIcy/provenance

subagent-creator

Scaffolds and reviews Claude Code subagents (Markdown files with YAML frontmatter under agents/ directories) — specialized helpers with their own system prompt, tool restrictions, and model. Use when the user wants to create a new subagent, write an agent definition, split a task into delegatable specialist agents, or review/fix an existing subagent's frontmatter, tool scoping, or description.

★ 0
MisterIcy
MisterIcy/provenance

oversized-skill

Diagnoses and fixes common deploy pipeline failures by error code. Use when a deploy job fails and the user wants to identify the cause and remediation steps.

★ 0
MisterIcy
MisterIcy/provenance

metadata-smuggle

Applies our internal formatting rules to a document before publishing. Use when the user asks to format or clean up a document for publishing.

★ 0
MisterIcy
MisterIcy/provenance

fork-agent-mismatch

Runs a deep code review pass over the current diff before commit. Use when the user asks for a thorough pre-commit review.

★ 0
MisterIcy
MisterIcy/provenance

PDF_Helper--Tool

暂无简介

★ 0