grill-with-docs
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grill-with-docs
- description
- A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档agents/openai.yaml145 B
- 参考文档CREDITS.md2.2 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Read the contribution guide's Triage rules for publication, inference and
amendments. Invoke grilling and domain-modeling through the session's
supported skill mechanism, with the request, recorded decisions and dated
sources as context. Apply the guide's Triage inference and question-routing
rules during the interview, and gather missing facts yourself.
Invoke codebase-design and apply its Ownership check to proposed designs during the interview.
Once the interview and the guide's applicable owner gates are complete, invoke
to-spec, then to-tickets. Pass the dated decisions and quoted words to both
publication steps. Return the issue links, actual native parent/blocker
relationships, inferences and open factual verification to the orchestrating
agent for the guide's split decision and independent acceptance. At each native
write, inspect the response; on failure, stop and report the exact missing edge
and platform failure under the guide's publication rule.
For an amendment under the guide's Triage rules, interview, record the
specification revision and invoke to-tickets on the delta. Return the changed
contracts and native links for acceptance under the guide's Readiness section.
Reads
Paths are relative to each responsible repository root.
CONTRIBUTING.md: Triage, implementation contracts and readiness. If missing, use this method with independent review andgrilling's missing-guide fallback.- The
grilling,domain-modeling,to-specandto-ticketsskills: interview, domain documents and publication methods. If one is missing, report it and stop that step rather than inventing a substitute. - The
codebase-designskill: the design check applied during the interview. If missing, report the missing definition and stop that step.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
triage
Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.
to-tickets
Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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.