conceptual-model-beads
Skill19 starsChanged 6 days agoMITView on GitHub
Build a conceptual model and create Beads issues from the findings. Converts ambiguities, overloaded concepts, and unclear states 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-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-model-beadsSkill
- 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
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 Conceptual Model Review on the current prototype, then create Beads issues from the findings so they become trackable tasks.
- Distinctive: line 14
Create a conceptual model for this scope:
- Distinctive: line 18
Use ultrathink. Work from the repo, prototype, docs, screenshots, routes, components, and visible states.
- Very specific: line 21
Write docs/hci/conceptual-model.md unless the user asked for another path.
- Distinctive: line 22
Create the directory if it does not exist.
- Very specific: line 76
Check if the bd CLI is available:
- Very specific: line 82
If
bdis not found: Stop here. Output the Conceptual Model only, and append: - Distinctive: line 99
Check if the repo is already initialized:
- Very specific: line 105
If that fails (no .beads/ directory, not initialized):
- Very specific: line 111
Use --stealth so Beads metadata is not committed to the main repo.
- Distinctive: line 115
Create one parent issue to group all findings from this review:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Conceptual Model Review on the current prototype, then create Beads issues from the findings so they become trackable tasks.
This is an add-on to conceptual-model. Run the full review first, produce the complete artifact, then pipe findings into Beads.
Phase 1: Run the Conceptual Model Review
Create a conceptual model for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, prototype, docs, screenshots, routes, components, and visible states. If details are missing, infer cautiously and mark assumptions.
Output
Write docs/hci/conceptual-model.md unless the user asked for another path.
Create the directory if it does not exist.
Required sections
- Purpose of the system or feature
- Primary actors
- Primary objects/entities
- Actions available on each object
- States and transitions
- Rules, constraints, permissions, and guardrails
- Ambiguities or overloaded concepts
- Recommendations to simplify the model
Tables to include
Actors
| Actor | Goal | Main tasks | Notes |
Objects
| Object | Definition | Key attributes | Related objects |
Actions
| Action | Target object | Preconditions | Result |
States
| Object | State | Meaning | Entered by | Exited by |
Note: keep this state table high-level (name and one-line meaning only). Full lifecycle definition belongs in the state-model artifact. If a state-model artifact already exists, reference it rather than repeating it.
Diagrams
Add Mermaid diagrams:
- state diagrams for major objects
- entity relationship diagrams for object relationships
Evaluation lens
A strong conceptual model should make these obvious:
- what exists in the system
- what users can do
- what state something is in
- what will happen next
Flag anything that breaks these expectations.
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 Conceptual 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: /conceptual-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 "Conceptual 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 (ambiguities, overloaded concepts, unclear states, missing rules):
MAJOR findings -- always create:
Fundamental model ambiguities that cause user confusion:
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.
Simplification recommendations and minor naming issues:
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: Conceptual Model
- Purpose of the system or feature
- Primary actors
- Primary objects/entities
- Actions available on each object
- States and transitions
- Rules, constraints, permissions, and guardrails
- Ambiguities or overloaded concepts
- Recommendations to simplify the model
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.

