菜单
File a substrate-friction observation correctly. Use the moment you notice anything unexpected about the substrate — a missing flag, a confusing error, a workflow surprise. Filing is autonomous; do not gate on the user.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/blakesims/stores --skill observe命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | observe |
| description | File a substrate-friction observation correctly. Use the moment you notice anything unexpected about the substrate — a missing flag, a confusing error, a workflow surprise. Filing is autonomous; do not gate on the user. |
| user_invocable | true |
You are filing an observation about substrate friction. Filing is autonomous (ai_autonomous) — you do not need user assent. Friction goes to a row immediately or it dies.
For dogfood context, see /CLAUDE.md and stores/observations/CLAUDE.md.
You (the agent) invoke this skill any time you notice friction with the substrate during other work. The user can also invoke it directly to file something they noticed. Either way, the protocol is the same.
Bar for filing: you noticed friction. Don't filter at filing time. Triage happens in the observation lifecycle, not before the row exists.
Examples of file-worthy friction:
git mv, set_var, or any other "I'll just bypass" shortcut.You need at minimum:
dev (always, for substrate-friction; other source values are for production-system observations the user files)high | normal | low
high = blocks current work or breaks the dogfood loop itselfnormal = friction worth fixing, doesn't blocklow = nit / cosmetic / wishlistdate -Iseconds)w<isoweek>-d<weekday> (use w$(date +%V)-d$(date +%u))T013 for substrate-T013, or empty if no task is in flight)stores observations add --invoker ai_autonomous \
--summary "<one-line>" \
--source dev \
--priority <high|normal|low> \
--captured-at "$(date -Iseconds)" \
--captured-week "w$(date +%V)-d$(date +%u)" \
--task-id "<surfacing-task-display-id-or-omit>" \
--body-from-file <(cat <<'EOF'
<longer description here. Multi-line OK. State what you tried, what you expected, what happened, and whether it's reproducible. If a workaround exists, describe it. Reference any related observations or tasks by id.>
EOF
)
Returns the new L-id (e.g. L004). Capture it; reference it in commit messages and any related work.
/pickup will surface it. Do NOT stop to investigate the observation now — that's a different turn, with the user, with a triage decision./observe directly: confirm the L-id back to them and exit. Do not auto-investigate.If stores observations add itself fails (substrate uninitialized, schema error, runner crash), do NOT swallow the error. Write a worklog note instead:
# Make a worklog note via the project's note script:
docs/worklog/new-note.sh substrate-down-<short-slug>
Fill the worklog note with the same content the observation would have carried, plus what broke about the substrate itself. When the substrate recovers, file the observation properly and reference the worklog note in the body.
The discipline: never let friction die silently, even when the substrate is the thing that's broken.
--invoker ai_with_human — wrong; filing is autonomous. The user-authority moments are investigate / confirm / wont_fix / promotion, not filing./observe files and exits.stores observations list --json | grep -i <keyword> first; if a recent open observation already covers it, add a comment via stores observations update (with --invoker ai_autonomous if the field allows) instead of duplicating.task_id that doesn't exist — leave it empty if no task surfaced this. The field is optional and a soft-FK; a wrong value is worse than no value.After filing, print one line:
Filed L0XX (priority=<X>, summary="<...>", task_id=<id-or-none>).
Then return to whatever the surrounding work was.
Use when operating as the Pi architecture/design governor for the stores substrate, or when asking Pi for design review, priority coherence, contract ratification advice, or architectural approval over agent-comm.
Use when operating as the Claude Code engine controller for the stores substrate: driving tasks, daemon/worktrees, codex/rebase loops, and multi-agent coordination.
Use for the temporary front-of-engine queue-curation role in stores: triages observations/intake/tasks, deduplicates stale/noisy rows, drafts priority recommendations, and delegates backlog analysis to subagents without implementing code.