菜单
Run a cognitive walkthrough and create Beads issues from the findings. Converts walkthrough breakdowns (Q1-Q4 failures) into trackable Beads tasks with priorities and dependencies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Audit cross-screen consistency and create Beads issues from the findings. Converts consistency breaks and invariant violations into trackable Beads tasks with priorities and dependencies.
Audit failure paths and create Beads issues from the findings. Converts unhandled failure states, missing empty states, and broken recovery paths into trackable Beads tasks with priorities and dependencies.
Run a heuristic evaluation and create Beads issues from the findings. Converts Nielsen heuristic violations into trackable Beads tasks with priorities and dependencies.
Review information architecture and create Beads issues from the findings. Converts orphan screens, mislabeled navigation, and grouping problems into trackable Beads tasks with priorities and dependencies.
Map user journeys and create Beads issues from the findings. Converts dead ends, missing recovery paths, and confusion points into trackable Beads tasks with priorities and dependencies.
| name | cognitive-walkthrough-beads |
| description | Run a cognitive walkthrough and create Beads issues from the findings. Converts walkthrough breakdowns (Q1-Q4 failures) into trackable Beads tasks with priorities and dependencies. |
Run a Cognitive Walkthrough on the current prototype, then create Beads issues from the findings so they become trackable tasks.
This is an add-on to cognitive-walkthrough. Run the full walkthrough first, produce the complete artifact, then pipe findings into Beads.
Run a cognitive walkthrough for this task or flow:
$ARGUMENTS
Use ultrathink. Act like a plausible first-time user with only the cues available in the interface. Use the actual prototype and codebase context.
Write docs/hci/cognitive-walkthrough.md unless the user asked for another path.
Create the directory if it does not exist.
For each step include:
Also flag:
End with:
Check if the bd CLI is available:
command -v bd
If bd is not found: Stop here. Output the Cognitive Walkthrough 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: /cognitive-walkthrough-beads
If bd is found: Continue to Step 2.
Check if the repo is already initialized:
bd ready --json
If that fails (no .beads/ directory, not initialized):
bd init --stealth
Use --stealth so Beads metadata is not committed to the main repo.
Create one parent issue to group all findings from this walkthrough:
bd create "Cognitive Walkthrough: <branch> — <scope>" -p 1 --json
Capture 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>."
For each walkthrough breakdown (Q1-Q4 failures):
MAJOR findings -- always create:
Steps where users cannot form goal or notice action (Q1/Q2 failures):
bd create "[MAJOR] <finding-title>" -p 0 --json
MINOR findings -- create only if the user passed --include-minor. Otherwise skip and note them in the output.
Weak feedback or unclear interpretation (Q3/Q4 issues):
bd create "[MINOR] <finding-title>" -p 2 --json
For 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>
bd ready --json
Return a combined report with two sections:
<id> -- <title>bd ready --json