Workflow Design

SkillMedia

'Designs multi-step AI workflows with chained prompts for Clay, AirOps, n8n, or other automation tools. Produces

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Workflow Design skill

What this skill tells your AI

The instructions your AI receives, as published by matteotitta/genesys-skills in skills/meta/orchestration/workflow-design/SKILL.md and read by ahel’s review.

Design multi-step AI workflows with chained prompts for B2B SaaS marketing deliverables.


Claude Code Triggers

Invoke this skill when user says:

  • "Design a workflow"
  • "Create a process for [task]"
  • "Build a prompt chain"
  • "Sequence prompts for [goal]"
  • "Create an AI workflow"
  • "Multi-step process for [task]"
  • "Chain prompts together"

Do NOT invoke when:

  • User wants a single prompt → Use prompt-design skill
  • User wants to execute a prompt → Just run it directly
  • User wants code/app built → Use vibe-coding skill

Input Requirements

Required Inputs

InputDescriptionSource
Task descriptionWhat the workflow should accomplishUser specifies
Desired outcomeWhat the final output should beUser specifies

Optional Inputs (improve quality)

InputHow It Helps
Existing promptsBuilds on proven patterns
Integration needsDetermines variable chaining
Tool contextAdapts for specific AI (Claude, GPT, etc.)
Quality criteriaDefines success metrics per stage

Input Validation Checklist

Before proceeding, verify:

  • Task description is clear
  • Desired outcome is defined
  • Stages can be identified

If inputs are missing: Ask for task description and desired outcome.


Core Frameworks (voice-locked invariants)

Workflow Patterns

PatternStructureUse When
LinearStage 1 → 2 → 3 → 4Research → Strategy → Execution
Parallel + Merge[A + B + C] → Merge → DIndependent research streams
Iterative LoopStage → Check → Refine → CheckQuality-critical outputs
ForkStage 1 → [A or B] based on conditionDifferent paths for different inputs

Variable Chaining Rules

RuleDescription
Explicit naming{{stage1_output}} not just {{output}}
Format matchingOutput format of N must match input format of N+1
ValidationCheck variables exist before using
FallbackDefine behavior if variable is empty

Process pointer

Step-by-step phases, flowchart, and pre-built workflow chains live in the premium reference.

Summary: validate inputs → map workflow → generate stage prompts (each using 7-section architecture) → create variable registry → write execution guide → compile single markdown document.


Anti-Hallucination Guardrails

  1. Use exact 7-section structure for each stage. Don't invent new sections.
  2. Mark all variables. Every user input and stage output must be {{marked}}.
  3. Include quality gates. Every stage needs verification criteria.
  4. Test variable chains. Ensure outputs match expected inputs.
  5. Reference existing patterns. Check reference files before creating new workflow stages.

Quality

Pre-delivery checklist, worked example (Transcript-to-LinkedIn workflow), and anti-examples live in the premium reference.

Minimum bar: diagram complete, variable registry covers every variable, all stages carry a 7-section prompt, quality gates defined between stages, execution guide present.


Skill Auto-Update Protocol

Feedback signal detection, pattern triggers, and self-update format live in the premium reference.


Integration with Other Skills

Each stage uses the 7-section prompt architecture from the prompt-design skill. For individual prompt creation, use prompt-design.

SkillRelationshipUsage
prompt-designFoundationEach workflow stage uses 7-section prompt architecture
All content skillsUses outputWorkflows feed into skill execution
vibe-codingRelatedFor building tools that use workflows
transcript-analysisProvides inputInterview workflows

Signals

GitHub stars
36
Forks
14
Last commit
Jul 2026
Advanced
Catalog kind
skill
Gateway key
workflow-design
Source
github.com/matteotitta/genesys-skills