菜单
Pick the right ordered sequence of skills for the job at hand, announce it, and keep reminding the user which skill comes next after each stage completes — so they never have to remember the chain themselves. Only active when explicitly invoked.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/caezium/skills --skill playbook命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Orchestrate Henry's long-running engineering and research work across recall, consultation, specifications, verification, worker fleets, evidence trails, handoffs, and reflection. Use when work spans sessions or machines, needs autonomous agents, crosses risky runtime boundaries, or Henry asks to resume, run a fleet, keep going, or use Henry mode. Skip small self-contained tasks.
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
Implement a piece of work based on a spec or set of tickets.
基于 SOC 职业分类
正在显示 SKILL.md
| name | playbook |
| description | Pick the right ordered sequence of skills for the job at hand, announce it, and keep reminding the user which skill comes next after each stage completes — so they never have to remember the chain themselves. Only active when explicitly invoked. |
| disable-model-invocation | true |
The user knows skills exist but shouldn't have to memorise which ones to run in which order. When this skill is invoked, you become the keeper of that sequence for the rest of the session.
This is not default behavior. Never volunteer skill-sequence guidance unless the user invoked /playbook (or explicitly asks). Once invoked, the guidance persists for the whole session.
Read the argument and conversation context, then match against the workflow table:
| Workflow | When it fits |
|---|---|
| feature | Building a feature or making a nontrivial change: design → spec → tickets → implementation → review (Matt Pocock's spec-driven flow) |
/playbook feature), use that one.Read the chosen workflow file. Present the full sequence up front as a short numbered list: each step's skill, what it produces, and which step the user is currently at.
Don't assume they're at step 1 — if the conversation already contains a sharpened design, they may be at the spec step; if a spec already exists on the tracker, they may be at tickets. Say where you think they are and why.
For the rest of the session:
/skill-name — ." Put this at the END of your final message for the turn so it's the last thing they read.Each workflow is one file in workflows/: a name, when it fits, and an ordered list of steps (skill + what it produces + prerequisites). To add a new arrangement for a different context of work, add a file there and a row to the table above. Keep steps as existing skills — a playbook orders skills, it doesn't define new ones.