Awesome Claude Workflows

A community-curated list of real-world Dynamic Workflows in Claude Code — shared by the people who actually run them in production.

Browse workflows · Install one · Contribute yours

New to the feature? See the official docs and the
launch post. This list isn't
a tutorial — it's a directory of battle-tested examples.

Contents

• Use a workflow
• Workflows
  • Research & Synthesis
  • Code Review & Quality
  • Bug Hunts & Audits
  • Migrations & Modernization
  • Design & Planning
• Resources
• Contributing
• License

Use a workflow

Claude Code auto-discovers any workflow file dropped into ~/.claude/workflows/ (user scope, every
project) or ./.claude/workflows/ (project scope). Each one becomes a /<name> slash command — no
plugin, manifest, or registration needed.

Install with one command (installs into ~/.claude/workflows/):

# no clone needed — install a single workflow by name
curl -fsSL https://raw.githubusercontent.com/lxcong/awesome-claude-workflows/main/install.sh | bash -s -- <name>

Or from a clone:

git clone https://github.com/lxcong/awesome-claude-workflows.git
cd awesome-claude-workflows
./install.sh                  # install all workflows (user scope)
./install.sh <name>           # just one
./install.sh --project <name> # into ./.claude/workflows/ instead

Then, in Claude Code:

/<name> ...

or run /workflows to browse. (Manual alternative: copy any
workflows/<name>/<name>.workflow.js to ~/.claude/workflows/<name>.js yourself.)

Prerequisites: Claude Code v2.1.154+, a paid plan, and Dynamic workflows enabled in
/config. The first run asks you to approve the plan — pick "don't ask again" to skip it next
time. Workflows can use many tokens; start scoped.

Workflows

🌱 This list is just getting started. Our first showcase, TradingFlow, grew big enough to
graduate into its own repo. The categories below are the
scenarios we want to fill next. Run a workflow on a real problem? Add it — that's
the whole point of this repo.

Research & Synthesis

• TradingFlow — Multi-agent equity analysis: 4 analysts
  in parallel → bull/bear research debate → trader proposal → aggressive/neutral/conservative risk
  debate → portfolio manager's 5-tier rating. Patterns: parallel fan-out, sequential debate, judge
  panel. Research only — not financial advice. 🎓 Graduated to its
  own repo — see the pointer.

Code Review & Quality

• 🚧 To be contributed — add yours.

Bug Hunts & Audits

• 🚧 To be contributed — codebase-wide bug hunts, security audits, dead-code sweeps. Add yours.

Migrations & Modernization

• 🚧 To be contributed — framework swaps, API deprecations, language ports. Add yours.

Design & Planning

• 🚧 To be contributed — plan stress-tests, design judge panels. Add yours.

Resources

• Introducing dynamic workflows in Claude Code — official launch post (May 28, 2026)
• Dynamic workflows documentation — official docs
• Dynamic Workflows in Claude Code — Hacker News
• r/ClaudeCode: Multi-agent workflows

Contributing

This repo lives on your contributions. If you've built a workflow that solved a real problem,
share it so others can learn from a working example.

See CONTRIBUTING.md. In short — add one entry to the right use-case section:

- [Name](link) — One-line description of the problem it solves. *By [@you](https://github.com/you)*

Prefer workflows you've actually run, and note the rough token cost / plan if you can.

License

MIT © 2026 lxcong and contributors. Curated entries remain under their respective owners'
licenses.