# Tools Visual State Machines

> Model user journeys, retention loops, or process states with ASCII state machines and storyboards.

- Skill: `tjboudreaux/tools-visual-state-machines` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tjboudreaux/tools-visual-state-machines`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tjboudreaux/tools-visual-state-machines/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: tjboudreaux (https://skillmd.com/u/tjboudreaux)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tjboudreaux/tools-visual-state-machines

---


# State Machine Storyboards

## Intent
- Explain how users or issues move through states with clear entry/exit rules.
- Support growth loop, launch, or issue triage skills by making transitions explicit.

## Inputs
1. State list (e.g., `New`, `Activated`, `Retained`, `Churned`).
2. Transition triggers (events, metrics, timers).
3. Guard conditions / actions per transition.

## Workflow
1. **Define legend**
   - `[STATE]` boxes; arrows `-->`; dotted `..>` for optional transitions.
2. **Draft storyboard**
   - Example:
     ```
     [New]
       |
       | signup complete
       v
     [Activated] --fails SLA--> [Churn Risk]
       | retention event
       v
     [Retained]
     ```
3. **Add annotations**
   - Edge labels: `>=3 sessions`, `NPS<30`.
   - Actions: `/{ send email }` appended to arrow.
4. **Link to metrics**
   - Provide query references or analytics dashboards for each transition.
5. **Embed in docs**
   - Include in PRs/issues or `.factory/skills/...` referencing file names (e.g., `state-machines/activation.txt`).

## Verification
- Every state has at least one ingress and egress (unless Start/End).
- Triggers clearly defined; no unlabeled arrows.
- Diagram reviewed with product/growth stakeholders for accuracy.