A skill your agent uses when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits…

MITAuto-check passed

Install Workflow

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill workflow -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace workflow --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/hyperflow/skills/workflow .claude/skills/workflow && 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
workflow
GitHub stars
2.8k
Token cost
~2.7k tokens
SKILL.md length
1,148 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits…

  • Works in 5 steps: Research and planning → Parallel implementation or investigation → Adversarial verification → …
  • A task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes
  • SKILL.md covers Routing Rules, Provider Contracts, Claude Code Prompt Skeleton and Save For Reuse
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use the portable workflow adapter. Trigger with /hyperflow:workflow, "run a workflow", "dynamic workflow", "big task", "large migration", "repo-wide audit".

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Claude Code native workflows; Codex/OpenCode/Grok portable adapter

The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • A task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes
  • Large migrations
  • Repo-wide audits
  • High-confidence verification

Example prompts

  • “run a workflow”
  • “dynamic workflow”
  • “big task”
  • “/workflow”

Requirements

  • Compatibility (from SKILL.md): Claude Code native workflows; Codex/OpenCode/Grok portable adapter
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, AskUserQuestion, Skill

Workflow steps

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

  1. Research and planning
  2. Parallel implementation or investigation
  3. Adversarial verification
  4. Quality gates and repair loop
  5. Final synthesis

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • AskUserQuestion
    • Skill

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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.

  • Compatibility

    Claude Code native workflows; Codex/OpenCode/Grok portable adapter

    From compatibility in the SKILL.md frontmatter.

Context cost

Workflow loads about 2.7k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 1,148 words of instructions outside code blocks.

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

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,148 words, ~2,691 tokens.

Download SKILL.mdSave it as .claude/skills/workflow/SKILL.md (or your agent's skills folder).
name
workflow
description
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use the portable workflow adapter. Trigger with /hyperflow:workflow, "run a workflow", "dynamic workflow", "big task", "large migration", "repo-wide audit".
allowed-tools
Read, Glob, Grep, AskUserQuestion, Skill
compatibility
Claude Code native workflows; Codex/OpenCode/Grok portable adapter
argument-hint
<big task description>
version
1.0.0
license
MIT
tags
workflow, claude-code, codex, opencode, grok, large-task, orchestration, verification

Workflow

Big-task path for work that is too large for normal turn-by-turn orchestration: system-wide changes, large migrations, repo-wide audits, high-confidence verification, and task prompts that explicitly ask for a workflow.

  • In Claude Code, use the host dynamic workflow runtime.
  • In Codex, run the portable workflow adapter with Codex subagents when exposed; otherwise run the same phases inline in the current thread.
  • In OpenCode, run the portable workflow adapter with Task/subagent dispatch when exposed; otherwise run the same phases inline in the current session.
  • In Grok, run the portable workflow adapter with spawn_subagent when enabled; otherwise run the same phases inline in the current session.
  • In Antigravity, Desktop/web bridge mode, or any host that cannot preserve the adapter phases, say so in one line and route to /hyperflow:plan with chain-mode=auto.

Claude Code dynamic workflows require Claude Code v2.1.154 or later and can be disabled by /config, managed settings, ~/.claude/settings.json, or CLAUDE_CODE_DISABLE_WORKFLOWS=1. When disabled, use the portable adapter if the host is Codex, OpenCode, or Grok; otherwise route to /hyperflow:plan with chain-mode=auto.

Routing Rules

  • Run this skill in Claude Code, Codex, OpenCode, and Grok.
  • Auto-route here when triage returns flow=deep or flow=scientific, scope=system-wide, or the user says big task, large migration, repo-wide audit, run a workflow, or dynamic workflow.
  • Do not route here for moderate multi-file work, routine bug fixes, or a task that needs user sign-off between implementation stages. Big-task workflow runs should not depend on arbitrary mid-run user input; split sign-off-heavy work into separate workflows or use spec -> scope -> dispatch.
  • Do not set /effort ultracode or xhigh automatically. The user can enable /effort ultracode manually for session-wide workflow selection.

Provider Contracts

Claude Code Native Workflow

When this skill runs, ask the Claude Code workflow runtime to create a dynamic workflow for $ARGUMENTS. The generated workflow must preserve Hyperflow's doctrine inside the worker prompts and must include these phases:

  1. Research and planning

    • Map affected files, dependency edges, tests, docs, and risk boundaries.
    • Read .hyperflow/profile.md, .hyperflow/architecture.md, .hyperflow/conventions.md, .hyperflow/testing.md, and .hyperflow/memory/index.md when present.
    • Produce a concise execution graph with parallelizable units and dependencies.
  2. Parallel implementation or investigation

    • Fan out independent agents by subsystem or file family.
    • Keep each agent brief specific: objective, files in scope, constraints, acceptance criteria, and test expectations.
    • Use the lightest model/stage that can safely do the work when the runtime supports model routing.
  3. Adversarial verification

    • Run independent verification agents against each implementation or finding.
    • For audits, verify each finding before reporting it.
    • For implementation, check cross-file integration, regression risk, security-sensitive paths, and missed tests.
  4. Quality gates and repair loop

    • Run the project lint, typecheck, build, and relevant tests from .hyperflow/testing.md or detected package scripts.
    • Retry focused fixes only for verified failures.
    • Never use --no-verify; never force-push to main or master.
  5. Final synthesis

    • Return one coordinated result with completed work, verification evidence, unresolved risks, changed files, and next actions.
    • For durable project learnings, identify what should be appended to .hyperflow/memory/, but do not invent memory entries unrelated to the run.
Codex Portable Workflow Adapter

Codex does not provide Claude Code's dynamic workflow runtime. Treat /hyperflow:workflow as a custom Hyperflow workflow envelope around Codex subagents and inline fallback:

  1. Research and planning

    • Read the same .hyperflow/ cache files listed above when present.
    • Write or update .hyperflow/tasks/<slug>.md for implementation or audit work that needs durable progress tracking.
    • Build an execution graph with parallelizable units, dependencies, expected commits, and verification commands.
  2. Parallel implementation or investigation

    • If Codex subagent tools are exposed, dispatch independent searcher/worker/writer units together and collect their results before review.
    • Map implementation and writing tasks to worker subagents; map codebase research to explorer/search subagents.
    • If subagents are unavailable, run each unit inline with explicit worker and reviewer labels.
  3. Adversarial verification

    • Run a separate verification pass for each completed unit before reporting it.
    • Use Codex thinking defaults for verification and final integration review.
  4. Quality gates and commits

    • Run the detected lint, typecheck, build, and relevant tests.
    • Commit each accepted unit separately using conventional commits.
    • Never use --no-verify; never request xhigh.
  5. Final synthesis

    • Return changed files, verification evidence, unresolved risks, and next actions.
Show full SKILL.md (469 more words)Show less
OpenCode Portable Workflow Adapter

OpenCode does not provide Claude Code's dynamic workflow runtime. Treat /hyperflow:workflow as a custom Hyperflow workflow envelope around OpenCode's task/subagent facilities and inline fallback:

  1. Research and planning

    • Read the same .hyperflow/ cache files listed above when present.
    • Write or update .hyperflow/tasks/<slug>.md for implementation or audit work that needs durable progress tracking.
    • Build an execution graph with parallelizable units, dependencies, expected commits, and verification commands.
  2. Parallel implementation or investigation

    • If OpenCode exposes Task/subagent dispatch, send independent implementation or investigation units through that path.
    • Keep each subtask bounded by objective, files in scope, constraints, acceptance criteria, and tests.
    • If task dispatch is unavailable, run each unit inline with explicit worker and reviewer labels.
  3. Adversarial verification

    • Run a separate verification pass for each completed unit before reporting it.
    • Run verification and the final integration review as decision-agent passes on the current session model.
  4. Quality gates and commits

    • Run the detected lint, typecheck, build, and relevant tests.
    • Commit each accepted unit separately using conventional commits.
    • Never use --no-verify.
  5. Final synthesis

    • Return changed files, verification evidence, unresolved risks, and next actions.
Grok Portable Workflow Adapter

Grok does not provide Claude Code's dynamic workflow runtime. Treat /hyperflow:workflow as a custom Hyperflow workflow envelope around Grok spawn_subagent and inline fallback:

  1. Research and planning

    • Read the same .hyperflow/ cache files listed above when present.
    • Write or update .hyperflow/tasks/<slug>.md for implementation or audit work that needs durable progress tracking.
    • Build an execution graph with parallelizable units, dependencies, expected commits, and verification commands.
  2. Parallel implementation or investigation

    • If spawn_subagent is available and subagents are not disabled (GROK_SUBAGENTS / config), dispatch independent units together:
      • implementer/writer → subagent_type: general-purpose
      • searcher/research → subagent_type: explore
    • Collect results before review; spawn independent siblings in parallel when the runtime allows.
    • If subagents are unavailable, run each unit inline with explicit worker and reviewer labels.
  3. Adversarial verification

    • Run a separate verification pass for each completed unit before reporting it.
    • Run verification and the final integration review as decision-agent passes on the current session model.
  4. Quality gates and commits

    • Run the detected lint, typecheck, build, and relevant tests.
    • Commit each accepted unit separately using conventional commits.
    • Never use --no-verify.
  5. Final synthesis

    • Return changed files, verification evidence, unresolved risks, and next actions.

Claude Code Prompt Skeleton

Use this shape when handing the task to the workflow runtime:

text
Create a dynamic workflow for this Hyperflow big-task run.

Task:
<user task>

Doctrine:
- Preserve Hyperflow autonomy: execute reversible work without invented confirmations.
- Ask only for genuine ambiguity after codebase research.
- Keep plans, task decompositions, audits, and memory under .hyperflow/ when files are needed.
- Use conventional commits, one distinct task per commit.
- Never use --no-verify and never force-push to main/master.
- Respect the Hyperflow security blocklist in skills/hyperflow/security.md.

Required phases:
1. Research and planning.
2. Parallel implementation or investigation.
3. Adversarial verification.
4. Quality gates and focused repair loop.
5. Final synthesis.

Acceptance:
- Every substantive result is independently checked before being reported.
- Quality gates run or are explicitly marked unavailable with the command attempted.
- The final answer includes evidence, changed files, unresolved risks, and next actions.

Save For Reuse

When a run succeeds and the user will repeat it, mention that Claude Code can save the generated workflow from /workflows with s. Project workflows save under .claude/workflows/; personal workflows save under ~/.claude/workflows/. Do not create those files directly from this skill because plugin packaging does not currently ship .claude/workflows/ as a first-class component.

Codex, OpenCode, and Grok adapters are not saved through /workflows; repeatable behavior comes from this skill, .hyperflow/tasks/, project memory, and provider-specific subagent/task configuration.

© jeremylongshore, 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 plugins/ai-agency/hyperflow/skills/workflow of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

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

Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.7kAutomated safety check: PassMIT
Large Class Stylesgl-project/sglang37k2 repos~1.9kAutomated safety check: PassApache-2.0
Frontend Large Feature Architecturelangfuse/langfuse36k—~1.4kAutomated safety check: PassCustom licence
Recipe Find Large Filesgoogleworkspace/cli31k—~175Automated safety check: PassApache-2.0
Zcode Large Task Fixturezai-org/ZCode7.7k—~698Automated safety check: PassApache-2.0
Matlab Process Large Imagesmatlab/matlab-agentic-toolkit1.1k—~3kAutomated safety check: PassCustom licence

Similar skills

  • Large Class Style

    sgl-project/sglang

    Code style for SGLang large classes Scheduler, TokenizerManager, and ModelRunner: frozen-code conventions and init orchestration style.

    37k GitHub starsUsed in 2 repos~1.9k tokens
    AI & LLM EngineeringAuto-check passed
  • Architect large or state-heavy Langfuse frontend features. An agent skill from langfuse/langfuse.

    36k GitHub stars~1.4k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Recipe Find Large Files

    googleworkspace/cli

    Identify large Google Drive files consuming storage quota. An agent skill from googleworkspace/cli.

    31k GitHub stars~175 tokensUpdated 4 days ago
    Auto-check passed
  • Generate, verify, or remove large synthetic ZCode task fixtures in local ~/.zcode persistence for UI/session performance testing.

    7.7k GitHub stars~698 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Matlab Process Large Images

    matlab/matlab-agentic-toolkit

    Patterns for using blockedImage to process large images, harness parallel compute for image processing, and write custom adapters.

    1.1k GitHub stars~3k tokensUpdated 2 days ago
    Data & AnalyticsAuto-check passed
  • Azure Large Instances

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure Large Instances development including troubleshooting, limits & quotas, and integrations & coding patterns.

    776 GitHub stars~821 tokensUpdated 5 days ago
    Research & ScienceAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Workflow

What does Workflow do?

A skill your agent uses when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits…. Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow.

When should I use Workflow?

Workflow fits situations like: A task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes; large migrations; repo-wide audits; high-confidence verification.

How do I install Workflow in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill workflow -a claude-code`. Or copy the skill folder (plugins/ai-agency/hyperflow/skills/workflow in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/workflow in your project. Claude Code loads it when a task matches its description.

How do I install Workflow in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill workflow -a codex`. Or copy the skill folder (plugins/ai-agency/hyperflow/skills/workflow in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/workflow in your project. Codex loads it when a task matches its description.

Can I use Workflow 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 jeremylongshore/tons-of-skills-marketplace --skill workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow, .gemini/skills/workflow, .github/skills/workflow and .opencode/skills/workflow in your project.

What does Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, AskUserQuestion, Skill. Compatibility (from SKILL.md): Claude Code native workflows; Codex/OpenCode/Grok portable adapter.

Does Workflow 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 Workflow 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 Workflow use?

Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow use?

About 2.7k tokens (SKILL.md is roughly 11k 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 Workflow?

Skills that share tags, products or a category with Workflow: Large Class Style (sgl-project/sglang, 37k stars), Frontend Large Feature Architecture (langfuse/langfuse, 36k stars), Recipe Find Large Files (googleworkspace/cli, 31k stars) and Zcode Large Task Fixture (zai-org/ZCode, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.