tools-visual-state-machines
Model user journeys, retention loops, or process states with ASCII state machines and storyboards.
Source facts
- Repository
- tjboudreaux/cc-visualization-skills
- Last source activity
- February 17, 2026 at 00:27
- Detected SKILL.md language
- English
- Stars
- 4
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- tools-visual-state-machines
- description
- Model user journeys, retention loops, or process states with ASCII state machines and storyboards.
# 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.
View on GitHub