OpenSkillIndex← back to search
claude-code

Learn-skills.dev workflows-orchestration

Workflow orchestration patterns for src/app/workflows, focusing on application-layer use cases, long-running flows, event-driven coordination, and deterministic state transitions; use when implementing multi-step user journeys or cross-capability processes.

install
source · Clone the upstream repo
git clone https://github.com/NeverSight/learn-skills.dev
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/7spade/black-tortoise/workflows-orchestration" ~/.claude/skills/neversight-learn-skills-dev-workflows-orchestration && rm -rf "$T"
manifest: data/skills-md/7spade/black-tortoise/workflows-orchestration/SKILL.md
source content

Workflows Orchestration

Intent

Implement multi-step processes as explicit application workflows that coordinate capabilities via events, not via direct imports.

Workflow Model

  • A workflow is a state machine: explicit states, transitions, and terminal states.
  • Keep transitions deterministic and driven by events/commands.

Where Logic Lives

  • Workflow coordination lives in the Application layer (stores/use cases).
  • Domain invariants stay in Domain; do not encode rules in UI components.

Event-Driven Coordination

  • Workflows subscribe to events to advance state.
  • Publish events only after persistence (append-before-publish).

Concurrency

  • Choose explicit concurrency semantics for async operations (cancel, queue, ignore).
  • Avoid parallel append/publish operations that break causal ordering.

Observability

  • Include correlation IDs so a whole workflow run can be traced end-to-end.