coach
Decision support and grounded teaching for the human. Invoke when the user signals a message didn't land ("wait, what?", "I don't understand", "explain it like I'm five", "which is better?", "I'm not sure") about a question or fork they've been asked, or when they hand over a MEMORY.md lesson, an ADR, or a bundle and want to learn the concept behind it.
- License 许可
- MIT
- 最近更新
- 2026-08-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- coach
- description
- Decision support and grounded teaching for the human. Invoke when the user signals a message didn't land ("wait, what?", "I don't understand", "explain it like I'm five", "which is better?", "I'm not sure") about a question or fork they've been asked, or when they hand over a MEMORY.md lesson, an ADR, or a bundle and want to learn the concept behind it.
03 SKILL.md 正文
coach
Help the human decide and learn — never decide for them, never drift into lecture.
Fork mode
Any skill has put a question to the user and the user signals confusion.
- Pause the fork; do not press for an answer. If the user can't answer
because someone else owns the decision, route to
questionnaireinstead. - Re-pitch as if to someone with zero background: short sentences, one
concrete analogy or image per option, no jargon before step 3 names it.
Use the vocabulary of
.waymark/CONTEXT.mdwhen it exists; explain each option with its concrete consequence in this repository — not textbook generalities. - Name the underlying software-engineering concepts by their real names (coupling, migration cost, blast radius, lock-in...) so the user collects the vocabulary to steer with next time.
- Give one recommendation and the reason it fits this repo's constraints.
- Re-ask the original fork. The user still decides; a coach that answers its own question has failed.
Grounded-teach mode
The user hands over a MEMORY.md line, an ADR, or a bundle.
- Read the source: the bundle's SPEC/NOTES, the ADR, or the code the lesson points at.
- Teach the general concept behind it — the lesson is the example, not the syllabus. ("sticky positioning belongs to question rows" → CSS sticky and stacking contexts, demonstrated on this repo's transcript component.)
- Work through the actual repository code, never invented examples.
- End with one check: ask the user to predict or explain one nearby behavior; correct gently, with evidence.
Either mode: when a plain-prose explanation has failed to land twice, escalate the medium, not the volume — build a single-file HTML visual explainer of the concept (big visuals, few words, zero jargon) and walk it with the user. One concept per explainer; it teaches, it never argues for an option.
One concept per session — depth over coverage. Full-topic syllabi are a different engagement, not this skill.
04 同仓库更多 Skills
verify
Execute VERIFY.md scenarios through real consumer paths, review the frozen task-owned diff, deliver the verdict, and close the bundle — distilling durable lessons into the repo's MEMORY.md. Also the route for re-running an open bundle's gates or updating its VERIFY.md/NOTES.md, including after another agent's commits — never by ad-hoc scripts. For an open bundle only; tier-Light changes are verified inline, not through this skill.
spec
Turn the current conversation and codebase understanding into a work bundle with SPEC.md — synthesis of what is already known, interviewing only on material open forks. Use for unresolved ideas, requirements, sources, system maps, or plans.
scout
Settle the pre-spec unknowns that need a decision — interview the user on open forks, prototype feel-right design questions, sharpen the domain model, or chart an effort too big for one session. Use when an idea is still vague, options compete unchosen, the user doesn't know where to start, or asks to be grilled. Evidence questions with no decision attached (external facts, baselines) belong to explore instead.
questionnaire
Turn a decision the user can't fully answer into a Markdown questionnaire for the one person who can — filled in async, or together over a meeting. Adapted from Matt Pocock's to-questionnaire.
implement
Implement authorized Full-tier work from the bundle's SPEC.md, red-first at pre-agreed seams. Requires an explicit user request to implement or fix production code, and a SPEC whose red-test list covers this exact scope — post-ship review findings and follow-ups go through spec first. Never invoke on your own initiative. Do NOT trigger when the target is a throwaway prototype, research spike, or baseline (explore's scope), or when the fix is a tier-Light quickfix (proceed directly, no skill).
handoff
Compact the current conversation so another agent can pick the work up — into the active bundle's NOTES.md when one exists, or a standalone handoff document otherwise. Adapted from Matt Pocock's handoff.