Loaded Markdown

PlanPack Mermaid Diagram Skill

skills/planpack-mermaid-diagram/SKILL.md

Markdown viewer modes
Skill Name
planpack-mermaid-diagram
Skill Description
Create concise, human-reviewable Mermaid diagrams for PlanPack pipelines, lineage, blockers, handoffs, and agent orchestration. Use when asked to visualize a PlanPack, compare pipeline options, show serial vs parallel subagent flow, or produce Mermaid for the PlanPack viewer.

PlanPack Mermaid Diagram

Goal: a diagram a technical human can scan row by row, then inspect in the viewer. Default to flowchart TD unless lineage/dependency mapping is the main ask.

Procedure

  1. Identify the plan source, orchestrator, human gates, agent lanes, and final handoff.
  2. Serial work: one straight top-to-bottom spine, no side quests.
  3. Parallel work: one subgraph with direction LR; each lane a nested subgraph with direction TB. Every lane reaches one join node before the next row starts. No edges between lanes unless one truly depends on another.
  4. Show feedback loops (human review, validation failure, blocks) as a short edge back to the orchestrator only when they matter; a labeled blocker node often reads better.
  5. Short human-readable titles (2-5 words, optional 3-7 word second line). Detail belongs in the plan's human view, not the diagram. Do not use profile IDs as visible titles.
  6. Add class styles at the bottom.

Example shape:

Rendering diagram…

Visual Grammar

  • Humans: gates and review decisions. Agents: concrete worker roles.
  • Blockers/failures: red/pink only. Completion/handoff: green. Process feedback: amber.

Default palette:

classDef source fill:#e8f3ff,stroke:#2563eb,color:#071b3a;
classDef orchestrator fill:#f5f2e8,stroke:#6f5d2a,color:#211a07;
classDef human fill:#fff4cc,stroke:#b88700,color:#2b2100;
classDef agent fill:#ecfdf3,stroke:#16803c,color:#062b15;
classDef validation fill:#eef2ff,stroke:#4f46e5,color:#14143d;
classDef blocker fill:#ffe8e8,stroke:#dc2626,color:#3b0707;
classDef done fill:#dcfce7,stroke:#15803d,color:#052e16;
classDef feedback fill:#fff7ed,stroke:#ea580c,color:#431407;

Shape Rules

  • Prefer 12-22 nodes; one primary diagram before optional detail diagrams.
  • No decorative icons, emojis, paragraph labels, crossing loops, or dependency spaghetti.
  • Quote labels containing spaces or punctuation.
  • Do not include implementation details that are not visible in the plan.
  • The viewer renders Mermaid with securityLevel: "strict": click tooltip directives are disabled, so never rely on hover detail.

Output

  1. Mermaid code block.
  2. Two to five terse notes only if tradeoffs matter.
Markdown Source86 lines
1---2name: planpack-mermaid-diagram3description: Create concise, human-reviewable Mermaid diagrams for PlanPack pipelines, lineage, blockers, handoffs, and agent orchestration. Use when asked to visualize a PlanPack, compare pipeline options, show serial vs parallel subagent flow, or produce Mermaid for the PlanPack viewer.4---5 6# PlanPack Mermaid Diagram7 8Goal: a diagram a technical human can scan row by row, then inspect in the viewer.9Default to `flowchart TD` unless lineage/dependency mapping is the main ask.10 11## Procedure12 131. Identify the plan source, orchestrator, human gates, agent lanes, and final handoff.142. Serial work: one straight top-to-bottom spine, no side quests.153. Parallel work: one `subgraph` with `direction LR`; each lane a nested subgraph with16   `direction TB`. Every lane reaches one join node before the next row starts. No edges17   between lanes unless one truly depends on another.184. Show feedback loops (human review, validation failure, blocks) as a short edge back to19   the orchestrator only when they matter; a labeled blocker node often reads better.205. Short human-readable titles (2-5 words, optional 3-7 word second line). Detail belongs21   in the plan's human view, not the diagram. Do not use profile IDs as visible titles.226. Add class styles at the bottom.23 24Example shape:25 26```mermaid27flowchart TD28  A["Draft plan"] --> P["Start parallel discovery"]29 30  subgraph DISCOVERY["Parallel discovery"]31    direction LR32    subgraph INFO["Info"]33      direction TB34      I1["Collect constraints"] --> I2["Surface blockers"]35    end36    subgraph IDEAS["Ideas"]37      direction TB38      G1["Generate options"] --> G2["Select candidates"]39    end40    subgraph RESEARCH["Research"]41      direction TB42      R1["Find prior art"] --> R2["Extract risks"]43    end44  end45 46  P --> I147  P --> G148  P --> R149  I2 --> J["Join findings"]50  G2 --> J51  R2 --> J52  J --> C["Consolidate plan"]53```54 55## Visual Grammar56 57- Humans: gates and review decisions. Agents: concrete worker roles.58- Blockers/failures: red/pink only. Completion/handoff: green. Process feedback: amber.59 60Default palette:61 62```mermaid63classDef source fill:#e8f3ff,stroke:#2563eb,color:#071b3a;64classDef orchestrator fill:#f5f2e8,stroke:#6f5d2a,color:#211a07;65classDef human fill:#fff4cc,stroke:#b88700,color:#2b2100;66classDef agent fill:#ecfdf3,stroke:#16803c,color:#062b15;67classDef validation fill:#eef2ff,stroke:#4f46e5,color:#14143d;68classDef blocker fill:#ffe8e8,stroke:#dc2626,color:#3b0707;69classDef done fill:#dcfce7,stroke:#15803d,color:#052e16;70classDef feedback fill:#fff7ed,stroke:#ea580c,color:#431407;71```72 73## Shape Rules74 75- Prefer 12-22 nodes; one primary diagram before optional detail diagrams.76- No decorative icons, emojis, paragraph labels, crossing loops, or dependency spaghetti.77- Quote labels containing spaces or punctuation.78- Do not include implementation details that are not visible in the plan.79- The viewer renders Mermaid with `securityLevel: "strict"`: `click` tooltip directives are80  disabled, so never rely on hover detail.81 82## Output83 841. Mermaid code block.852. Two to five terse notes only if tradeoffs matter.86