state-model-beads
Skill19 starsChanged 6 days agoMITView on GitHub
Define state machines and lifecycles, then create Beads issues from the findings. Converts ambiguous states, silent transitions, and undefined exits into trackable Beads tasks with priorities and dependencies.
- Installs packages
In this repository67 other files it gives its agents.
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- state-modelSkill
- task-analysis-writerSkill
- usability-test-plannerSkill
- vocabulary-audit-beadsSkill
- vocabulary-auditSkill
- wireframe-criticSkill
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Run a State Model Review on the current prototype, then create Beads issues from the findings so they become trackable tasks.
- Distinctive: line 18
Use ultrathink. Work from the repo, routes, components, database schemas, API endpoints, and visible UI states.
- Very specific: line 21
Write docs/hci/state-model.md unless the user asked for another path.
- Distinctive: line 22
Create the directory if it does not exist.
- Distinctive: line 48
Create Mermaid state diagrams for each entity.
- Distinctive: line 49
all states as nodes
- Distinctive: line 68
Create a coverage table:
- Very specific: line 97
Check if the bd CLI is available:
- Very specific: line 103
If
bdis not found: Stop here. Output the State Model only, and append: - Distinctive: line 120
Check if the repo is already initialized:
- Very specific: line 126
If that fails (no .beads/ directory, not initialized):
- Very specific: line 132
Use --stealth so Beads metadata is not committed to the main repo.
- Distinctive: line 136
Create one parent issue to group all findings from this review:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run a State Model Review on the current prototype, then create Beads issues from the findings so they become trackable tasks.
This is an add-on to state-model. Run the full review first, produce the complete artifact, then pipe findings into Beads.
Phase 1: Run the State Model Review
Define the state machines and lifecycles for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, routes, components, database schemas, API endpoints, and visible UI states. If details are missing, infer conservatively and mark assumptions.
Output
Write docs/hci/state-model.md unless the user asked for another path.
Create the directory if it does not exist.
Required process
1) Identify stateful entities
Find every object in the system that has a lifecycle -- anything that changes state over time. Common examples: requests, tasks, users, sessions, approvals, documents, payments, invitations.
2) For each entity, define:
States
| State | Meaning | User-visible cue | Entry condition | Exit condition |
Allowed transitions
| From | To | Trigger | Who can trigger | Side effects |
Invalid transitions
| From | To | Why invalid | What happens if attempted |
Ambiguous or undefined states
Flag any state that is:
- implied but never named
- named differently in different places
- missing a user-visible cue
- reachable but with no defined exit
3) Diagrams
Create Mermaid state diagrams for each entity. Include:
- all states as nodes
- transitions as labeled edges
- guard conditions where applicable
- terminal states clearly marked
4) Cross-entity dependencies
Identify where one entity's state depends on another's. Document:
- which entities are coupled
- what happens when a parent entity changes state
- cascading transitions
- orphaned states (child entity stuck when parent moves)
5) UI state coverage
For each state, check:
- Is there a distinct visual treatment?
- Can the user tell what state they are in?
- Can the user tell what actions are available in this state?
- Is the transition feedback clear?
Create a coverage table: | Entity | State | Has visual cue | Has available actions | Has transition feedback | Gap |
Synthesis
End with:
- entities with the most ambiguous state models
- states that users cannot distinguish visually
- transitions that happen silently without feedback
- invalid transitions that the UI does not prevent
- recommendations for simplifying overly complex lifecycles
Quality bar
- Be specific. Reference actual database fields, API statuses, component props, or CSS classes where possible.
- Distinguish between backend state and user-perceived state. Both matter.
- A well-defined state model should make it impossible to ask "what state is this in?" while looking at the screen.
Deliverable style
- Clear headings
- Markdown tables
- Mermaid diagrams where useful
- Direct language
- No filler
Phase 2: Beads Integration
Step 1 -- Detect Beads
Check if the bd CLI is available:
command -v bdIf bd is not found: Stop here. Output the State Model only, and append:
## Beads Integration: Skipped
`bd` CLI not found. To install Beads and create trackable issues from this review:
pip install beads-cli
# or see https://github.com/steveyegge/beads
Then re-run: /state-model-beadsIf bd is found: Continue to Step 2.
Step 2 -- Initialize Beads (if needed)
Check if the repo is already initialized:
bd ready --jsonIf that fails (no .beads/ directory, not initialized):
bd init --stealthUse --stealth so Beads metadata is not committed to the main repo.
Step 3 -- Create parent issue
Create one parent issue to group all findings from this review:
bd create "State Model Review: <branch> — <scope>" -p 1 --jsonCapture the parent issue ID from the JSON output. Store scope and summary:
bd update <parent-id> --description "<1-2 sentence scope summary>" --acceptance "<quality bar from the review>" --notes "Review date: <today>. Scope: <arguments>."Step 4 -- Create child issues per finding
For each finding (ambiguous states, silent transitions, undefined exits, missing visual cues):
MAJOR findings -- always create:
Undefined states, silent transitions, and dead-end states:
bd create "[MAJOR] <finding-title>" -p 0 --jsonMINOR findings -- create only if the user passed --include-minor. Otherwise skip and note them in the output.
Missing transition feedback and weak visual cues:
bd create "[MINOR] <finding-title>" -p 2 --jsonFor each created issue, update with structured fields (do NOT use bd edit):
bd update <child-id> --description "<what/why + evidence>" --notes "<location and context>" --acceptance "<fix recommendation or verification>"Then link child to parent:
bd dep add <child-id> <parent-id>Step 5 -- Show next actions
bd ready --jsonOutput
Return a combined report with two sections:
Section A: State Model
- Stateful entities identified
- States, transitions, and invalid transitions per entity
- Mermaid state diagrams
- Cross-entity dependencies
- UI state coverage table
- Synthesis and recommendations
Section B: Beads Integration Summary
- Status: initialized | already-initialized | skipped (with reason)
- Parent bead:
<id>--<title> - Created beads: table of Bead ID | Severity | Finding Title | Priority
- Skipped findings: list with reasons (e.g., "MINOR, --include-minor not set")
- Next actions: output of
bd ready --json
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

