[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EZZ24KB0VFZ4M7AV5R5FVB":3,"skill-same:01M7EZZ24KB0VFZ4M7AV5R5FVB":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7EZZ24KB0VFZ4M7AV5R5FVB","dynamic-workflow-mode",null,"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.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fdynamic-workflow-mode\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dynamic-workflow-mode\ndescription: \"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.\"\nmetadata:\n  origin: ECC\n---\n\n# Dynamic Workflow Mode\n\nUse 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.\n\n## When To Activate\n\n- The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode.\n- A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard.\n- Multiple agents need the same repeatable process but the process is not yet captured as a shared skill.\n- A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge.\n\n## Core Contract\n\nDynamic 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:\n\n- **Objective**: the outcome it owns and the outcome it explicitly does not own.\n- **Inputs**: files, URLs, prompts, data sources, credentials policy, and user-provided constraints.\n- **Outputs**: commits, reports, screenshots, status files, or control pane snapshots.\n- **Eval**: at least one pass\u002Ffail check tied to the task, not only \"it ran\".\n- **Handoff**: a short artifact that tells the next operator what happened, what is blocked, and how to resume.\n\n## Dynamic Harness Decision Tree\n\n1. **One-shot task**: keep it inline. Do not invent a harness.\n2. **Repeated task with changing inputs**: create a task-local harness and keep it under a temp or project-local working area.\n3. **Repeated task across teammates or repos**: extract the pattern into a shared skill.\n4. **Task with external state, queueing, or approvals**: add control pane visibility before adding more automation.\n5. **Task with safety risk**: add an eval gate and a human merge gate before autonomous execution.\n\n## Task-Local Harness Template\n\nUse this structure before writing code:\n\n```markdown\n# Dynamic Workflow Harness\n\nObjective:\n- Ship:\n- Do not ship:\n\nInputs:\n- Repo or workspace:\n- External systems:\n- Credentials policy:\n\nLoop:\n1. Discover current state.\n2. Generate or update the smallest useful artifact.\n3. Run eval checks.\n4. Record status and handoff.\n5. Stop on failed gate, unclear ownership, or unsafe external action.\n\nEval:\n- Command:\n- Expected pass signal:\n- Failure owner:\n\nHandoff:\n- Status:\n- Evidence:\n- Next action:\n```\n\n## Shared Skill Extraction\n\nPromote a task-local harness into a shared skill only when at least two of these are true:\n\n- The same workflow appears in multiple sessions, repos, teams, or launches.\n- The workflow needs specific language, tool, or safety sequencing.\n- Failures repeat because operators skip a gate or lose context.\n- The workflow has a stable input\u002Foutput contract.\n- The workflow benefits from a control pane, status board, or team handoff.\n\nWhen extracting, write the skill first in `skills\u002F\u003Cname>\u002FSKILL.md`. Add command shims only if a legacy slash-entry surface is still required.\n\n## Control Pane Checkpoints\n\nDynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session:\n\n- **Plan**: objective, owner, acceptance criteria, and risky external systems.\n- **Queue**: work items, assigned agent role, branch\u002Fworktree, and dependency edges.\n- **Run**: active harness, current loop step, recent eval result, and token\u002Fcost signal if available.\n- **Gate**: test results, browser screenshots, security review, and merge readiness.\n- **Handoff**: what is done, what failed, what needs a human decision.\n\nIf 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.\n\n## Eval Gates\n\nEvery dynamic harness needs a task-specific eval. Pick the cheapest reliable gate:\n\n| Work Type | Eval Gate |\n| --- | --- |\n| Code feature | Focused test, lint, coverage, and one integration path |\n| UI\u002Fcontrol pane | Browser smoke with screenshot and overflow\u002Ferror checks |\n| Agent workflow | Fixture transcript or seeded work item with expected routing |\n| Research\u002Fcontent | Source-neutral brief, claim checklist, and publish-ready outline |\n| Integration | Dry-run command, config validation, and no-secret scan |\n\nDo not claim a dynamic workflow is reusable until the eval can be rerun by another teammate.\n\n## Anti-Patterns\n\n- Generating scripts that hide the real decision logic from the operator.\n- Treating dynamic workflow mode as permission to skip tests.\n- Creating one-off docs when a shared skill or status artifact is the real product.\n- Running multiple agents without ownership, merge gate, or conflict policy.\n- Letting raw private research data leak into public docs.\n\n## Output Standard\n\nFinish with:\n\n- The harness or skill path.\n- The eval commands and results.\n- The control pane or handoff artifact path.\n- The next reusable extraction candidate.\n","# Dynamic Workflow Mode\n\nUse 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.\n\n## When To Activate\n\n- The user mentions dynamic workflows, custom harnesses, harness-per-task, adaptive workflows, or Claude Code dynamic workflow mode.\n- A task needs a custom loop, evaluator, crawler, fixture generator, watcher, or local dashboard.\n- Multiple agents need the same repeatable process but the process is not yet captured as a shared skill.\n- A workflow needs durable handoff artifacts, eval evidence, or operator approval before merge.\n\n## Core Contract\n\nDynamic 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:\n\n- **Objective**: the outcome it owns and the outcome it explicitly does not own.\n- **Inputs**: files, URLs, prompts, data sources, credentials policy, and user-provided constraints.\n- **Outputs**: commits, reports, screenshots, status files, or control pane snapshots.\n- **Eval**: at least one pass\u002Ffail check tied to the task, not only \"it ran\".\n- **Handoff**: a short artifact that tells the next operator what happened, what is blocked, and how to resume.\n\n## Dynamic Harness Decision Tree\n\n1. **One-shot task**: keep it inline. Do not invent a harness.\n2. **Repeated task with changing inputs**: create a task-local harness and keep it under a temp or project-local working area.\n3. **Repeated task across teammates or repos**: extract the pattern into a shared skill.\n4. **Task with external state, queueing, or approvals**: add control pane visibility before adding more automation.\n5. **Task with safety risk**: add an eval gate and a human merge gate before autonomous execution.\n\n## Task-Local Harness Template\n\nUse this structure before writing code:\n\n```markdown\n# Dynamic Workflow Harness\n\nObjective:\n- Ship:\n- Do not ship:\n\nInputs:\n- Repo or workspace:\n- External systems:\n- Credentials policy:\n\nLoop:\n1. Discover current state.\n2. Generate or update the smallest useful artifact.\n3. Run eval checks.\n4. Record status and handoff.\n5. Stop on failed gate, unclear ownership, or unsafe external action.\n\nEval:\n- Command:\n- Expected pass signal:\n- Failure owner:\n\nHandoff:\n- Status:\n- Evidence:\n- Next action:\n```\n\n## Shared Skill Extraction\n\nPromote a task-local harness into a shared skill only when at least two of these are true:\n\n- The same workflow appears in multiple sessions, repos, teams, or launches.\n- The workflow needs specific language, tool, or safety sequencing.\n- Failures repeat because operators skip a gate or lose context.\n- The workflow has a stable input\u002Foutput contract.\n- The workflow benefits from a control pane, status board, or team handoff.\n\nWhen extracting, write the skill first in `skills\u002F\u003Cname>\u002FSKILL.md`. Add command shims only if a legacy slash-entry surface is still required.\n\n## Control Pane Checkpoints\n\nDynamic workflow mode becomes team-usable when it exposes state. Record these checkpoints whenever the task spans more than one session:\n\n- **Plan**: objective, owner, acceptance criteria, and risky external systems.\n- **Queue**: work items, assigned agent role, branch\u002Fworktree, and dependency edges.\n- **Run**: active harness, current loop step, recent eval result, and token\u002Fcost signal if available.\n- **Gate**: test results, browser screenshots, security review, and merge readiness.\n- **Handoff**: what is done, what failed, what needs a human decision.\n\nIf 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.\n\n## Eval Gates\n\nEvery dynamic harness needs a task-specific eval. Pick the cheapest reliable gate:\n\n| Work Type | Eval Gate |\n| --- | --- |\n| Code feature | Focused test, lint, coverage, and one integration path |\n| UI\u002Fcontrol pane | Browser smoke with screenshot and overflow\u002Ferror checks |\n| Agent workflow | Fixture transcript or seeded work item with expected routing |\n| Research\u002Fcontent | Source-neutral brief, claim checklist, and publish-ready outline |\n| Integration | Dry-run command, config validation, and no-secret scan |\n\nDo not claim a dynamic workflow is reusable until the eval can be rerun by another teammate.\n\n## Anti-Patterns\n\n- Generating scripts that hide the real decision logic from the operator.\n- Treating dynamic workflow mode as permission to skip tests.\n- Creating one-off docs when a shared skill or status artifact is the real product.\n- Running multiple agents without ownership, merge gate, or conflict policy.\n- Letting raw private research data leak into public docs.\n\n## Output Standard\n\nFinish with:\n\n- The harness or skill path.\n- The eval commands and results.\n- The control pane or handoff artifact path.\n- The next reusable extraction candidate.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fecc\u002Fdynamic-workflow-mode","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dynamic-workflow-mode",{"tool":38,"command":39},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dynamic-workflow-mode",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill dynamic-workflow-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fdynamic-workflow-mode\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]