grilling
Clarify an ambiguous plan or stress-test a proposed decision before implementation.
- License 许可
- MIT
- 最近更新
- 2026-09-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grilling
- description
- Clarify an ambiguous plan or stress-test a proposed decision before implementation.
02 资源文件 1
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
Clarify the decision
Establish the intended outcome, meaningful constraints, and evidence of success. Read relevant code and existing decisions before asking questions whose answers are available there. Gather a small fact directly; delegate a bounded independent investigation only when it usefully overlaps other work.
Choose routine implementation details yourself and explain consequential choices through observable behavior. Ask the user about unresolved goals, behavior, material tradeoffs, or authority that the repository cannot establish. Offer a recommended answer with a reason. Reuse answers and authorization already given.
Ask the smallest useful batch of questions. Continue independent work while a blocking answer is pending. If the user explicitly requests an exhaustive interview, explore more branches; otherwise stop when remaining uncertainty no longer changes the next step. Do not require the user to choose classes, patterns, or test seams that you can responsibly select from the code.
Record the chosen direction, assumptions, acceptance criteria, and unresolved material decisions. Call the Skill tool with "domain-modeling" only when terminology or durable design records need changing. If implementation is authorized, continue into it once blocking decisions are settled. If the request is planning-only, deliver the plan without adding an extra confirmation round.
04 同仓库更多 Skills
wayfinder
Map unresolved decisions for a large initiative and work through their dependencies until a plan is actionable.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn an agreed feature or plan into a proportionate, testable specification at the requested destination.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-matt-pocock-skills
Configure missing tracker and domain-document conventions for the Matt Pocock workflows in a repository.
research
Investigate a specific technical question using primary sources and save a cited research note.