mirror of
https://github.com/mattpocock/skills.git
synced 2026-09-12 18:38:06 +07:00
Matt Pocock
a3065f1b7b
The old page explained the mechanism and stopped. It answered none of the questions people actually ask: which grilling skill to reach for, how many questions is normal, what to do with a question talking can't settle, whether to clear context before to-spec. Keep the mechanism short and spend the page on judgement instead: three-way sibling routing keyed on what you have in front of you; a section naming passivity as the main failure mode; grillable vs ungrillable as the move for questions that need a prototype; an "It's working if" list; and a "Common questions" section answering the six highest-volume ones. Say plainly to leave plan mode off. Sourced from user questions across X, Discord and YouTube.
1.4 KiB
1.4 KiB
mattpocock-skills
| mattpocock-skills |
|---|
| patch |
Rewrite the grill-me docs page around what people actually get wrong.
The old page explained the mechanism — rounds, the frontier, the decision tree — and stopped there. Every recurring question from the last few months went unanswered on it: which of the three grilling skills to reach for, how many questions is normal, what to do when a question can't be answered by talking, and whether to start a fresh session before writing the spec.
The rewrite keeps the mechanism short and spends the page on the judgement calls instead:
- Sibling routing is now a three-way list keyed on what you have in front of you — no codebase, a codebase, or too big for one session — rather than a paragraph.
- "It's a conversation, not an interview" names passivity as the main failure mode. A session where you answer "agreed" forty times produces a plan you didn't write and can't defend.
- "Grillable and ungrillable" gives readers the move for a question that talking cannot settle: stop, prototype, come back. This is where long sessions come from.
- A "Common questions" section answers the six highest-volume ones directly, including how to restore one-question-at-a-time and why you should not clear context before
to-spec. - "It's working if" added, led by the sharpest signal: if you never disagreed, you didn't need the session.
Also drops the "plan mode" ambiguity by saying plainly to leave it off.