菜单
Use when wrapping up a session, after a mistake or correction, or when significant codebase knowledge was gained, to persist learnings into the brain; triggers include "reflect", "remember this".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/alexanderop/afk --skill reflect命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when the user wants to generate behavioral evals, LLM-judge tests, or eval cases for a skill, agent, prompt, or feature, write a failing eval before implementing, or scaffold an eval harness in a repo that has none
Use when a plan or spec splits into many independently-mergeable units — a codebase-wide migration, rename, or repeated pattern change — and the user wants them implemented in parallel as separate PRs rather than one sequential pass. The fan-out alternative to afk:implement.
Use when the user says "grill me", asks to stress-test a plan, wants to be interviewed or asked the questions needed before building, offers a vague feature idea, or wants grounded planning before non-trivial implementation
基于 SOC 职业分类
正在显示 SKILL.md
| name | reflect |
| description | Use when wrapping up a session, after a mistake or correction, or when significant codebase knowledge was gained, to persist learnings into the brain; triggers include "reflect", "remember this". |
Review the conversation and persist learnings — to brain/, to skill files, or
as structural enforcement. This is where most brain content comes from. The
invariant: a learning lands in the destination where it will actually change
future behavior, not just the brain by default.
Do not use this skill for trivia already captured in the brain, or for plan-specific notes that belong in the plan's docs.
brain/index.md to understand what notes already exist. If brain/
does not exist, run afk:init-brain first.brain/index.md itself is rebuilt by the PostToolUse hook.Not everything belongs in the brain. Route each learning to where it has the most impact.
brain/principles/encode-lessons-in-structure.md.brain/). Codebase knowledge, principles, gotchas — anything
that informs future sessions. The default destination. Use the brain skill
for writing conventions: one topic per file, directories with [[wikilink]]
indexes, no inlined content in index files.${CLAUDE_PLUGIN_ROOT}/skills/<skill>/). If a learning
is about how a specific skill works — its process, prompts, or edge cases —
update the skill directly.STOP and ask the user when a candidate learning encodes a preference or decision you are not confident they hold, or when persisting it would contradict an existing brain note. Otherwise apply and report.
Return a summary in this shape:
## Reflect Summary
- Brain: [files created/updated, one line each]
- Skills: [skill files modified, one line each]
- Structural: [rules/scripts/checks added]
- Todos: [follow-up items filed]