Doc Summary
Learn what multi-recipe workflows are, how they connect recipes into larger processes, and how to use them effectively.
Reading time: About 4 minutes Skill level: Beginner
WHAT YOU WILL LEARN
After reading this article, you will understand what multi-recipe workflows are, how recipes pass information to each other, and how to execute a workflow from start to finish.
WHAT IS A MULTI-RECIPE WORKFLOW
A multi-recipe workflow is a group of CRAFT recipes designed to be run sequentially, where information from each recipe is shared to the next.
Think of preparing a multi-course meal. You do not cook everything simultaneously without a plan. The appetizer preparation informs the main course timing. The main course flavors guide your sauce decisions. Each dish builds on what came before, and the final result is a cohesive dining experience.
Multi-recipe workflows operate the same way. Each recipe produces output that feeds into subsequent recipes. The first recipe gathers foundational information. The second recipe uses that foundation to go deeper. By the final recipe, you have built something comprehensive that no single recipe could produce alone.
WHY WORKFLOWS MATTER
Individual recipes solve individual problems. That is their strength and their limitation. Some goals require multiple coordinated steps that build on each other.
Consider developing a complete brand identity. You need to understand your business context before you can define your audience. You need to understand your audience before you can identify their pain points. You need to understand pain points before you can craft your value proposition. Each step requires the previous step’s output.
A multi-recipe workflow coordinates this progression. It defines which recipes to run, in what order, and how information flows between them. The result is a systematic process that produces comprehensive outcomes.
HOW WORKFLOWS WORK
Currently, multi-recipe workflows are manual processes. You run each recipe in sequence, carrying the output from one recipe into the next.
Here is the basic pattern.
First, you run Recipe 1 and collect its output. Most workflow recipes produce a summary block at the end, formatted for easy reference.
Next, you run Recipe 2, providing the Recipe 1 output as input. Recipe 2 builds on that foundation and produces its own summary block.
You continue this pattern through each recipe in the workflow. Each recipe receives relevant output from previous recipes and adds its own contribution.
Finally, the last recipe in the workflow synthesizes everything into a comprehensive deliverable.
The key is that information flows forward. Early recipes establish context. Middle recipes develop specific components. Final recipes bring everything together.
THE BRAND IDENTITY WORKFLOW EXAMPLE
The Brand Identity Cookbook provides the most fully developed multi-recipe workflow currently available in CRAFT. It demonstrates how seven recipes work together to produce a complete brand profile.
Recipe 1 gathers business context. It establishes who you are, what you offer, and what constraints you face. This context flows into every subsequent recipe.
Recipe 2 analyzes your target audience. Using the business context, it develops detailed personas describing who you serve.
Recipe 3 identifies pain points. Using audience understanding, it maps the specific problems your audience faces.
Recipe 4 crafts your value proposition. Using audience and pain point knowledge, it articulates why your solution matters.
Recipe 5 defines your competitive edge. Using everything gathered so far, it positions you against alternatives.
Recipe 6 builds elevator pitches. Using audience, value proposition, and competitive positioning, it creates concise ways to communicate your brand.
Recipe 7 synthesizes everything. It pulls all previous outputs together into a comprehensive brand profile document.
Each recipe builds on the previous ones. By Recipe 7, you have a complete brand identity that reflects systematic analysis rather than guesswork.
EXECUTING A WORKFLOW
Running a multi-recipe workflow requires discipline but follows a straightforward process.
Start with the first recipe. Provide any required parameters and complete the recipe fully. When it finishes, you receive a summary block containing the key outputs.
Save the summary block. Copy it somewhere accessible. You will need to reference it in subsequent recipes.
Move to the next recipe. When prompted for inputs from previous recipes, provide the summary blocks you have collected. The recipe uses that context to inform its work.
Continue through the workflow. Each recipe adds to your collection of summary blocks. Later recipes may request multiple previous outputs.
Complete the final recipe. It synthesizes all your accumulated work into the workflow’s ultimate deliverable.
Throughout this process, you maintain the thread. The AI does not automatically remember previous recipes, so you provide that continuity through the summary blocks you carry forward.
TIPS FOR WORKFLOW SUCCESS
Complete recipes fully before moving on. Partial outputs create weak foundations for subsequent recipes. Take time to get quality results from each step.
Keep summary blocks organized. As you accumulate outputs, label them clearly. Knowing which block came from which recipe prevents confusion later.
Do not skip recipes. Workflows are designed as complete sequences. Skipping a recipe means missing context that later recipes expect.
Allow adequate time. Workflows involve multiple recipes, each requiring focused attention. Plan for the full sequence rather than rushing through.
Review the final synthesis. The last recipe in a workflow pulls everything together. Review it to ensure the synthesis accurately reflects your accumulated work.
WHAT IS COMING
Multi-recipe workflows currently require manual execution. You run each recipe and manage the information flow yourself.
Future versions of CRAFT plan to introduce more formal workflow support. This may include workflow definition files, automated information passing, and streamlined execution. These features are planned for development as the framework matures.
The Beta community will help shape how workflow features evolve. Your experience with manual workflows informs what automation would be most valuable.
For now, focus on mastering manual workflow execution. The discipline of carrying context forward and building systematically delivers powerful results even without automation.
COMMON QUESTIONS
Q: Can I run workflow recipes individually? A: Yes. Each recipe can function independently. However, recipes designed for workflows produce their best results when they receive context from earlier recipes in the sequence.
Q: What if I want to change something from an early recipe? A: You can re-run earlier recipes and carry the new output forward. Later recipes will reflect the updated foundation when you re-run them with the revised inputs.
Q: How long does a complete workflow take? A: It depends on the workflow and your depth preferences. The Brand Identity Workflow with standard depth settings takes several hours spread across multiple sessions. Quick modes are available for faster execution.
Q: Can I create my own workflows? A: Yes. If you identify a sequence of recipes that work well together, you can document that as a custom workflow. The pattern of sequential recipes with shared context applies to any domain.