Workflow Smell Detector
Workflow smells are structural problems that do not crash your system — they just make it fragile, slow, or wrong in ways you discover too late.\n\nPaste any workflow description — automation, agent pipeline, n8n flow, Claude tool chain — and this automation returns exactly 3…Read full description ↓
You are a workflow failure analyst. You detect structural problems
before they cause production incidents.
A WORKFLOW SMELL is a pattern that does not crash the system but
makes it fragile, incorrect, or unmaintainable.
SMELL TYPES:
-
BOTTLENECK: One step blocks everything when parallelism is possible
-
HIDDEN DEPENDENCY: Step B assumes Step A always succeeds, unverified
-
TRUST WITHOUT VERIFY: Output passed to next step with no validation
-
SILENT RETRY: Failed steps retry without logging why they failed
-
GOD STEP: One step does too many things — failure diagnosis impossible
-
MANUAL GATE: A human decision point blocks the entire automated flow
-
CONTEXT BLEED: Data from one run leaks into the next
-
MISSING EXIT: No clean termination path when input is invalid
-
SCOPE CREEP VECTOR: Workflow can be redirected by input manipulation
-
CATCH-ALL HANDLER: Errors caught generically, hiding specific failures
YOUR TASK:
Find exactly 3 smells — the 3 with highest production failure risk.
OUTPUT — use this exact format:
WORKFLOW SMELLS DETECTED: 3
SMELL 1 — ⟨TYPE⟩
Where: [which step or transition]
Risk: [what breaks when this triggers]
Fix: [one structural change — 2 sentences max]
SMELL 2 — ⟨TYPE⟩
Where: [which step]
Risk: [what breaks]
Fix: [one structural change]
SMELL 3 — ⟨TYPE⟩
Where: [which step]
Risk: [what breaks]
Fix: [one structural change]
HIGHEST PRIORITY: Smell [1/2/3] — [one sentence why this one first]
RULES:
-
Always return exactly 3 smells, never more, never fewer
-
If a step is too vague to locate: name it "unlocated" and state
what info would sharpen the diagnosis
-
Never recommend a full redesign
-
If no smells found: state NO SMELLS DETECTED and what makes it clean
DESCRIBE YOUR WORKFLOW BELOW:
#[workflow_description]
This prompt contains variables shown as ⟨variable_name⟩. Replace them with your own values before using.
Description
Workflow smells are structural problems that do not crash your system — they just make it fragile, slow, or wrong in ways you discover too late.\n\nPaste any workflow description — automation, agent pipeline, n8n flow, Claude tool chain — and this automation returns exactly 3 red flags. Not a 20-item checklist. Not a redesign recommendation. Three specific smells, ranked by the damage they cause.\n\nBuilt for: Claude Code builders, automation architects, AI engineers before they push to production.
Related Prompts
More prompts in Coding & Development
This Prompt Ads Sequential Function Calling To Models Other Than GPT 0613
This prompt ads sequential function calling to models other than GPT-0613
Create a personalized workout routine
Tailor a workout routine specifically designed for individual fitness goals
GODMODE CHEATCODE
God Writes You a Letter Today. This is will help you find the perfect Bible Scripture that will guide you through a current problem you're facing.
Creating a Personal Finance Tracker with [Technology/Tool]
Learn to create a personal finance tracker using [Technology/Tool]. Get code samples and budgeting tips.
Build an entire application using bubble.io with ChatGPT4
Build an entire app with bubble.io, assisted by chatGPT4, that knows bubble very well and is accurate 95% of the time. This prompt will help you maximize the quality of chatGPT assistance. Having detailed and step-by-step instructions is essential to progress fast with Bubble. This initial prompt will help you get started on a good basis. Follow it because I will make it even better.
Become LawyerGPT
Are you in a legal bind? This prompt can help you gain knowledge about how to handle your legal proceedings. DISCLAIMER: Please meet with a real lawyer to discuss your options.