Agent skill

Dynamic Workflow Mode

by affaan-m in affaan-m/ECC

Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.

MITAuto-check passed

Install Dynamic Workflow Mode

skills CLI
$ npx skills add affaan-m/ECC --skill dynamic-workflow-mode -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC dynamic-workflow-mode --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dynamic-workflow-mode .claude/skills/dynamic-workflow-mode && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dynamic-workflow-mode
GitHub stars
276k
Used in
1 other repo
Token cost
~1.3k tokens
SKILL.md length
656 words
Files
1
Skills in repo
673
Repo updated
First seen
Licence
MIT

At a glance

Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.

  • Works in 5 steps: One-shot task: keep it inline. Do not… → Repeated task with changing inputs:… → Repeated task across teammates or repos:… → …
  • Building a task-local harness
  • SKILL.md covers When To Activate, Core Contract, Dynamic Harness Decision Tree and Task-Local Harness Template, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dynamic Workflow Mode is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Building a task-local harness
  • Adding eval gates
  • Extracting a reusable skill from ad-hoc work

Example prompts

  • “/dynamic-workflow-mode”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. One-shot task: keep it inline. Do not invent a harness.
  2. Repeated task with changing inputs: create a task-local harness and keep it under a temp or project-local working area.
  3. Repeated task across teammates or repos: extract the pattern into a shared skill.
  4. Task with external state, queueing, or approvals: add control pane visibility before adding more automation.
  5. Task with safety risk: add an eval gate and a human merge gate before autonomous execution.

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dynamic Workflow Mode loads about 1.3k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 656 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 656 words, ~1,348 tokens.

Download SKILL.mdSave it as .claude/skills/dynamic-workflow-mode/SKILL.md (or your agent's skills folder).
name
dynamic-workflow-mode
description
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.
metadata.origin
ECC

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.

Dynamic Harness Decision Tree

  1. One-shot task: keep it inline. Do not invent a harness.
  2. Repeated task with changing inputs: create a task-local harness and keep it under a temp or project-local working area.
  3. Repeated task across teammates or repos: extract the pattern into a shared skill.
  4. Task with external state, queueing, or approvals: add control pane visibility before adding more automation.
  5. Task with safety risk: add an eval gate and a human merge gate before autonomous execution.

Task-Local Harness Template

Use this structure before writing code:

markdown
# Dynamic Workflow Harness

Objective:
- Ship:
- Do not ship:

Inputs:
- Repo or workspace:
- External systems:
- Credentials policy:

Loop:
1. Discover current state.
2. Generate or update the smallest useful artifact.
3. Run eval checks.
4. Record status and handoff.
5. Stop on failed gate, unclear ownership, or unsafe external action.

Eval:
- Command:
- Expected pass signal:
- Failure owner:

Handoff:
- Status:
- Evidence:
- Next action:

Shared Skill Extraction

Promote a task-local harness into a shared skill only when at least two of these are true:

  • The same workflow appears in multiple sessions, repos, teams, or launches.
  • The workflow needs specific language, tool, or safety sequencing.
  • Failures repeat because operators skip a gate or lose context.
  • The workflow has a stable input/output contract.
  • The workflow benefits from a control pane, status board, or team handoff.

When extracting, write the skill first in skills/<name>/SKILL.md. Add command shims only if a legacy slash-entry surface is still required.

Show full SKILL.md (263 more words)Show less

Control Pane Checkpoints

Dynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session:

  • Plan: objective, owner, acceptance criteria, and risky external systems.
  • Queue: work items, assigned agent role, branch/worktree, and dependency edges.
  • Run: active harness, current loop step, recent eval result, and token/cost signal if available.
  • Gate: test results, browser screenshots, security review, and merge readiness.
  • Handoff: what is done, what failed, what needs a human decision.

If the repo has ECC2 state enabled, prefer adding or reading checkpoints through the ECC control pane or state-store-backed scripts instead of scattering untracked notes.

Eval Gates

Every dynamic harness needs a task-specific eval. Pick the cheapest reliable gate:

Work TypeEval Gate
Code featureFocused test, lint, coverage, and one integration path
UI/control paneBrowser smoke with screenshot and overflow/error checks
Agent workflowFixture transcript or seeded work item with expected routing
Research/contentSource-neutral brief, claim checklist, and publish-ready outline
IntegrationDry-run command, config validation, and no-secret scan

Do not claim a dynamic workflow is reusable until the eval can be rerun by another teammate.

Anti-Patterns

  • Generating scripts that hide the real decision logic from the operator.
  • Treating dynamic workflow mode as permission to skip tests.
  • Creating one-off docs when a shared skill or status artifact is the real product.
  • Running multiple agents without ownership, merge gate, or conflict policy.
  • Letting raw private research data leak into public docs.

Output Standard

Finish with:

  • The harness or skill path.
  • The eval commands and results.
  • The control pane or handoff artifact path.
  • The next reusable extraction candidate.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/dynamic-workflow-mode of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Dynamic Workflow Mode next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dynamic Workflow Mode compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dynamic Workflow Mode this skillaffaan-m/ECC276k1 repos~1.3kAutomated safety check: PassMIT
Eval Harness Firstwshobson/agents40k—~2kAutomated safety check: PassMIT
Harness Evaltech-leads-club/agent-skills7k—~3.9kAutomated safety check: PassCC-BY-4.0
Extractalirezarezvani/claude-skills28k—~1.4kAutomated safety check: PassMIT
Eval Harnessxu-xiang/everything-claude-code-zh2k—~974Automated safety check: PassMIT
Eval Harnessxu-xiang/everything-claude-code-zh2k—~904Automated safety check: PassMIT

Similar skills

  • Eval Harness First

    wshobson/agents

    Build the evaluation harness that gates every fine-tuning run — golden sets, per-failure-mode graders, judge calibration, and base-model baselines.

    40k GitHub stars~2k tokensUpdated 4 days ago
    AI & LLM EngineeringAuto-check passed
  • Harness Eval

    tech-leads-club/agent-skills

    Evaluates a repository's agent harness (AGENTS.md, rules, skills) for broken paths, redundant instructions and usefulness, and stops at reports.

    7k GitHub stars~3.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Extract

    alirezarezvani/claude-skills

    Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.

    28k GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Eval Harness

    xu-xiang/everything-claude-code-zh

    适用于 Claude Code 会话的正规评测框架(Evaluation Framework),实现了评测驱动开发(Eval-Driven Development, EDD)原则

    2k GitHub stars~974 tokensUpdated 7 mo ago
    AI & LLM EngineeringAuto-check passed
  • Eval Harness

    xu-xiang/everything-claude-code-zh

    为 Claude Code 会话提供的正式评测框架,实现了评测驱动开发(EDD)原则. An agent skill from xu-xiang/everything-claude-code-zh.

    2k GitHub stars~904 tokensUpdated 7 mo ago
    AI & LLM EngineeringAuto-check passed
  • Eval

    alirezarezvani/claude-skills

    Evaluate and rank agent results by metric or LLM judge for an AgentHub session.

    28k GitHub stars~618 tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed

More from affaan-m/ECC

All 673 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    276k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed
  • Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    276k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    276k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    276k GitHub stars~2.9k tokensUpdated 4 days ago
    Auto-check passed
  • Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    276k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed
  • Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    276k GitHub stars~3.5k tokensUpdated 4 days ago
    Auto-check passed

Questions about Dynamic Workflow Mode

What does Dynamic Workflow Mode do?

Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Dynamic Workflow Mode is an agent skill from affaan-m/ECC. Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.

When should I use Dynamic Workflow Mode?

Dynamic Workflow Mode fits situations like: building a task-local harness; adding eval gates; extracting a reusable skill from ad-hoc work.

How do I install Dynamic Workflow Mode in Claude Code?

Run `npx skills add affaan-m/ECC --skill dynamic-workflow-mode -a claude-code`. Or copy the skill folder (skills/dynamic-workflow-mode in affaan-m/ECC) into .claude/skills/dynamic-workflow-mode in your project. Claude Code loads it when a task matches its description.

How do I install Dynamic Workflow Mode in Codex?

Run `npx skills add affaan-m/ECC --skill dynamic-workflow-mode -a codex`. Or copy the skill folder (skills/dynamic-workflow-mode in affaan-m/ECC) into .agents/skills/dynamic-workflow-mode in your project. Codex loads it when a task matches its description.

Can I use Dynamic Workflow Mode in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill dynamic-workflow-mode -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dynamic-workflow-mode, .gemini/skills/dynamic-workflow-mode, .github/skills/dynamic-workflow-mode and .opencode/skills/dynamic-workflow-mode in your project.

What does Dynamic Workflow Mode need to run?

SKILL.md names no scripts, command-line tools or credentials: Dynamic Workflow Mode is instructions for the agent only.

Does Dynamic Workflow Mode access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dynamic Workflow Mode safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dynamic Workflow Mode use?

Dynamic Workflow Mode is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dynamic Workflow Mode use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dynamic Workflow Mode?

Skills that share tags, products or a category with Dynamic Workflow Mode: Eval Harness First (wshobson/agents, 40k stars), Harness Eval (tech-leads-club/agent-skills, 7k stars), Extract (alirezarezvani/claude-skills, 28k stars) and Eval Harness (xu-xiang/everything-claude-code-zh, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dynamic Workflow Mode?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 275,546 GitHub stars. The repository holds 673 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.