Prompt Flows
Multi-framework sequences for real-world outcomes. Each flow chains 3 prompt techniques in a deliberate order — the sequence that produces results no single framework can deliver alone.
- 15
- Algorithms
- 50+
- Frameworks Referenced
- 3
- Steps Per Flow
The Refiner
Produce publication-ready long-form content by layering expert persona, audience structure, and multi-path quality validation.
The Code Architect
Design architecture before writing code, constrain each component with RISEN, then self-audit with Reflexion before shipping.
The Market Maker
Build emotionally resonant marketing copy from a product description — emotion first, conversion structure second, channel targeting third.
The Research Synthesizer
Transform a complex question into a rigorous, multi-perspective synthesis — scope first, explore all branches, then structure into a formal document.
The Debate Judge
Pressure-test contested decisions with adversarial debate, validate the verdict independently, and audit the assumptions it depends on.
The UX Strategist
Map constraints before ideating, break first-instinct design thinking with SCAMPER, then specify the winning concept as an implementable deliverable.
The Onboarding Writer
Set the documentation standard, structure every section for how people actually learn, then lock in quality with examples that prevent drift.
The Sprint Planner
Validate the goal before planning it, reason through every task and dependency, then formalize for stakeholders in a scoped, assumption-documented brief.
The Brand Voice Engineer
Extract voice identity from existing content, encode it as a reusable system prompt, then anchor production to exemplars so quality never drifts.
The Error Detective
Exhaust all possible causes before fixing any, stress-test each hypothesis against evidence, then audit the fix to confirm root-cause resolution.
The Story Architect
Turn a feature idea into a Jira-ready user story with complete, testable acceptance criteria — scenario context and restriction clarity included.
The PoC Builder
Scope the feasibility hypothesis, build iteratively with a ReAct think-act-observe loop, then refine the roughest edges — so your PoC proves the right thing and survives the demo.
The Legacy Integrator
Understand legacy constraints before writing a line, evaluate every integration path against what must not break, then implement within hard scope boundaries — for adding features to codebases you didn't write.
The Test Strategist
Reason about the full risk surface first, converge on coverage priorities through multi-path consistency checking, then anchor test output to your codebase's real style — for test suites that catch bugs, not just tick coverage metrics.
The API Designer
Specify the full API contract upfront, pressure-test it through adversarial stakeholder debate, then decompose into an implementation pipeline where each step feeds the next — for APIs designed to survive consumer needs, security review, and future changes.
Frequently Asked Questions
What is a prompt flow?
A prompt flow is a deliberate sequence of prompt frameworks applied in order, where the output of each step feeds into the next. Unlike a single prompt, a flow breaks complex tasks into stages — each handled by the technique best suited for that stage — producing results that no single framework could achieve alone.
How is a prompt flow different from prompt chaining?
Prompt chaining is the general technique of feeding one prompt's output into the next. A prompt flow is a specific, curated algorithm — a named sequence of distinct frameworks (like Role Prompting → COSTAR → Self-Consistency) designed for a particular type of task. Every prompt flow uses chaining, but not every prompt chain is a flow.
Do I need to run all steps manually?
Yes — each step is a separate prompt you run in sequence, copying the output of one into the input of the next. The flows are designed to be run in any chat interface (Claude, ChatGPT, Gemini). For repeated use, Prompt Edit lets you save each step as a reusable template with variables, making the sequence faster to run.
Which flow should I start with?
Start with The Market Maker (Beginner) if you write marketing copy, The Sprint Planner (Beginner) if you work in project management, or The Onboarding Writer (Beginner) if you create documentation. All three are rated Beginner and produce immediately useful outputs with familiar frameworks.
Can I adapt a flow to my specific use case?
Yes — each flow is a template, not a rigid prescription. You can swap one framework for another in the same position (e.g., replace AIDA with PAS in a marketing flow), adjust the number of steps, or combine flows. The key is preserving the logical sequence: establish context before generating, generate before evaluating, evaluate before finalizing.