dynamic-workflow-mode

Topics in the source

• Dynamic Workflow Mode
• When To Activate
• Core Contract
• Preserve Input Boundaries
• Dynamic Harness Decision Tree
• Task-Local Harness Template
• Shared Skill Extraction
• Control Pane Checkpoints

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. 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. 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

This is an excerpt. Refer to the complete source and its current requirements.