---
name: infographic-process
description: Build a step-flow infographic — 3 to 7 numbered steps connected by arrows. Use for onboarding flows, how-it-works diagrams, decision trees, timelines.
allowed-tools: create_infographic canvas_snapshot search_vault query_knowledge
title: Process Infographic
category: creative
status: active
metadata:
  triggers:
  - process infographic
  - step diagram
  - how it works
  - flow chart
  - onboarding flow
  - process diagram
  - step-by-step graphic
  - timeline graphic
  priority: 6
---
## Instructions

Build a **process-flow** infographic — 3 to 7 numbered steps in a
horizontal sequence with arrows between them. The point is to make
a sequence feel inevitable: each step earns the next.

1. **Clarify scope** — Ask what process is being shown and who it's
   for. Onboarding for a new user? Internal handoff? Customer
   journey? The audience changes the level of detail.

2. **Gather real steps** — Use `search_vault` and `query_knowledge` to
   pull from real artifacts: project workflows, SOP documents, vault
   docs. Don't invent generic steps; map the actual flow.

3. **Pick the right granularity**
   - 3 steps → "the big picture" (most impactful)
   - 4 steps → balanced overview
   - 5 steps → detailed walkthrough
   - 6-7 steps → reference diagram (rare, often a sign to split)
   - 8+ steps → split into two graphics or zoom out

4. **Step shape**
   - Each step has a SHORT title (≤ 4 words) and a SHORT description
     (≤ 12 words). One sentence max.
   - Titles are imperative or noun ("Submit Request", "Review",
     "Approve & Send"), never sentences.
   - Descriptions explain WHAT happens at the step, not WHO does it
     (the audience already knows).

5. **Call `create_infographic`** with `layout="process-flow"`,
   `theme="bright"` (or `"bold"` / `"editorial"`), and
   `show_on_canvas=true`. Pass `data.steps` as a list of
   `{title, description?}` objects. The engine renders a horizontal
   numbered flow with theme-colored connectors.

## Rules

- **Always pass `layout="process-flow"`** when calling
  `create_infographic` from this skill.
- **Pass `show_on_canvas=true`** so the user previews the flow
  immediately. Skip only if they say "svg only".
- **Immediately after `create_infographic` returns with a populated
  `canvas` field, call `canvas_snapshot({name: "<title>"})`** so the
  flow is recoverable.
- **Max 7 steps per graphic.** Past 7 the diagram becomes a wall of
  boxes nobody scans.
- **Titles ≤ 4 words.** Descriptions ≤ 12 words. Discipline IS the
  craft of a process diagram.
- **Imperative titles.** "Submit", "Review", "Approve", not "Submission
  is made by the user".
- **No fabrication.** If you don't know the actual steps in a workflow,
  ask the user to dictate them. Generic placeholders ("Step 1: Plan,
  Step 2: Execute") are useless.

## Examples

- input: "Make a how-it-works graphic for our agent ingest pipeline"
  output: |
    [calls query_knowledge for ingest pipeline architecture]
    [identifies 5 real stages: drop → classify → extract → wiki → graph]
    [calls create_infographic with layout="process-flow", theme="bright", 5 steps]
    Created ingest-flow.svg (theme: Bright) → projects/personal/output/ + canvas preview.

- input: "Process diagram for the new-customer onboarding journey"
  output: |
    [reads onboarding doc from vault]
    [confirms the 4 actual stages with the user before drawing]
    [calls create_infographic with layout="process-flow", theme="editorial", 4 steps]
    Created customer-onboarding.svg + canvas preview.