agentheim

Cross-cutting technical specialist. Handles decisions that span bounded contexts or involve infrastructure: persistence choice, messaging, transport, deployment topology, library choice, integration with external systems, cross-cutting concerns (auth, observability, caching, rate limiting). Called when a task's shape depends on a tech decision bigger than a single BC's implementation.

Routes modeling and execution work to the right specialist agents. Called by the model skill (for refinement and capture) and the work skill (for task execution). Takes a task or question plus project context, decides which specialist(s) to consult, runs them (in parallel when the work is independent), aggregates results, and returns refined tasks / implementation plans / ADRs.

Web research specialist. Given a question or topic, runs WebSearch and WebFetch to gather information from external sources, cross-checks claims, and produces a citation-rich markdown report in .agentheim/knowledge/research/. Called by the research skill directly, and by other specialists or skills when they need outside knowledge to proceed.

Strategic DDD specialist. Identifies bounded contexts from vision and features, names them, classifies them (core / supporting / generic), and maps their relationships. Called when a feature crosses or reshapes context boundaries, when a context map needs to be created or updated, or when the question is "what belongs where".

Tactical DDD specialist inside a single bounded context. Reasons about aggregates, entities, value objects, domain events, commands, invariants, and the workflow / lifecycle inside a BC. Called when a feature or refinement needs the inner shape of a context worked out — not where it lives (that's strategic-modeler's job).

Use whenever the user wants to start a new project, create a vision, do a Socratic modeling or discovery session, explore a problem space from scratch, or set up an initial context map and bounded contexts. Triggers on phrases like "let's brainstorm", "start a new project", "create a vision", "I want to build X", "model this out from scratch", "help me think through", "what should the shape of this be". Produces .agentheim/vision.md (and context-map.md if the domain is complex enough to warrant bounded contexts), and closes with an architecture foundation pass that unconditionally creates an `infrastructure/` BC (the standing home for globally-true tech concerns), emits decision tasks (globally-true → infrastructure BC, BC-local → originating BC), a walking-skeleton spike, and (when the vision implies frontend) a styleguide task. Deliberately produces no code — every output is markdown the user can review before `work` runs. Supports six switchable conversational modes (Interrogator [default], Suggestor, Challenger, Storyteller, Facilitator, Synthesizer) — see references/modes.md.

Use whenever the user wants to capture an idea, bug, feature request, refinement, or change to an existing bounded context — anything from "the button should be green" to "we need a whole new subscription subsystem". Also use when the user wants to refine existing backlog items or promote refined items to ready-to-work. Triggers on phrases like "I have an idea", "let's model this", "capture this", "add this to the backlog", "refine the auth backlog", "promote X to todo", "we should also", "what if we added", "there's a bug", "change the color of", "the domain needs to handle". Creates task markdown files in the appropriate bounded context with the right status, and can spawn deeper modeling sessions via the orchestrator. Supports six switchable conversational modes (Interrogator [default], Suggestor, Challenger, Storyteller, Facilitator, Synthesizer) during CAPTURE and REFINE — see references/modes.md.

Use whenever the user or another skill needs external information gathered from the web — state of the art on a topic, comparison of approaches, documentation for a library, domain knowledge from outside the codebase. Triggers on phrases like "research X", "find out about", "what's the state of the art for", "look up how others do", "compare options for", "gather info on", and also triggers internally when brainstorm or model hits an "I don't know enough" wall. Produces a research report in .agentheim/knowledge/research/ that can be referenced from tasks, ADRs, and modeling sessions.

Use whenever a worker is about to implement a task with observable behavior — features, bug fixes, refactors that should preserve behavior, any change with acceptance criteria you could turn into an assertion. Triggers internally from the `worker` agent at the start of its third action ("do the work"), and externally when the user invokes it explicitly ("do this TDD-style", "red-green-refactor this task"). Doctrine document; readable by humans and consumed by the worker as its execution discipline.

Use whenever the `work` skill is about to commit a worker's `RESULT: SUCCESS` — between the worker's return and `git add/commit`. Triggers internally from `work`'s post-success gate. Spawns the `verifier` agent with fresh context (no exposure to the worker's reasoning) to inspect the diff against the task's acceptance criteria and either PASS, FAIL with re-dispatch, or SKIP. Doctrine document; the operational steps live in `work`'s flow.