Skill

tools-visual-state-machines

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

Install

npx claudepluginhub tjboudreaux/cc-visualization-skills --plugin visualization-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Explain how users or issues move through states with clear entry/exit rules.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars1

Forks0

Last CommitFeb 17, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

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

State list (e.g., New, Activated, Retained, Churned).

Transition triggers (events, metrics, timers).

Guard conditions / actions per transition.

Workflow

Define legend

[STATE] boxes; arrows -->; dotted ..> for optional transitions.

Draft storyboard

Example:

[New]
  |
  | signup complete
  v
[Activated] --fails SLA--> [Churn Risk]
  | retention event
  v
[Retained]

Add annotations

Edge labels: >=3 sessions, NPS<30.
Actions: /{ send email } appended to arrow.

Link to metrics

Provide query references or analytics dashboards for each transition.

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.

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

State list (e.g., New, Activated, Retained, Churned).
Transition triggers (events, metrics, timers).
Guard conditions / actions per transition.

Workflow

Define legend
- [STATE] boxes; arrows -->; dotted ..> for optional transitions.

Draft storyboard

Example:

[New]
  |
  | signup complete
  v
[Activated] --fails SLA--> [Churn Risk]
  | retention event
  v
[Retained]

Add annotations
- Edge labels: >=3 sessions, NPS<30.
- Actions: /{ send email } appended to arrow.
Link to metrics
- Provide query references or analytics dashboards for each transition.
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.