Agent skill · product strategy · affaan-m
dynamic-workflow-mode
Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work.
Why this skill is useful
Provides a structured approach for creating dynamic workflows and task-local harnesses that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Dynamic Workflow Mode Use this skill when a coding agent can generate or adapt a task-local harness instead of only following a static command flow. The goal is to turn dynamic workflow mode into a disciplined system: temporary harnesses for one-off work, shared skill extraction for repeated work, and observable control pane checkpoints for teams. When To Activate The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode. A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard. Multiple agents need the same repeatable process but the process is not yet captured as a shared skill. A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge. Core Contract Dynamic workflow mode should produce a task-local harness only when the harness is cheaper and safer than manually driving the same steps. The harness must have: Objective: the outcome it owns and the outcome it explicitly does not own. Inputs: files, URLs, prompts, data sources, credentials policy, and user-provided constraints. Outputs: commits, reports, screenshots, status files, or control pane snapshots. Eval: at least one pass/fail check tied to the task, not only "it ran". Handoff: a short artifact that tells the next operator what happened, what is blocked, and how to resume. Preserve Input Boundaries Make two independent parts of Inputs explicit before discovery or execution: Action-to-tool bindings: which tool may read, write, or publish for each operation. A tool being available does not authorize it for another action. Entity scope: selected account, project, workspace, period, and exclusions, separately from search filters such as a shared payee, label, or name. Carry both into executor instructions and the handoff. Apply the entity boundary to discovery, batch preparation, and remaining-work reports, not only to writes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/dynamic-workflow-mode--65c898