Flowchart · Diagram Design

Should you write this as a skill?

A three-decision triage for turning a one-off workflow into something reusable. Shape carries type — ovals bracket the flow, rectangles are steps, diamonds are decisions.

NO YES NO YES New workflow Do it manually once Will you repeat it >3 times? One-off keep manual Reusable across projects? CLAUDE.md note project-scoped Write a skill reusable + assets LEGEND · SHAPE CARRIES TYPE Start / end (oval) Step (rectangle) Decision (diamond) Happy path Branch

WHY THIS FLOWCHART

Most things aren't skills

The happy path is narrow on purpose. Only workflows that clear all three gates earn the overhead of a reusable skill — everything else is better as a project note.

Shape, not color

  • Oval bookends the flow
  • Rectangle is a step
  • Diamond is a decision
  • Color reserved for the happy path

Every branch gets a label

Unlabeled branches turn a flowchart into a maze. Yes/No is fine; conditions in mono when the logic is richer.

flowchart · should I write this as a skill? example · schematic skill