grill-with-docs
Interview the user to resolve an unclear plan or design and record agreed domain terms and architectural decisions.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-15
- Stars
- ★ 635
- Forks
- 91
01 前言 Front Matter
- name
- grill-with-docs
- description
- Interview the user to resolve an unclear plan or design and record agreed domain terms and architectural decisions.
- disable-model-invocation
- true
02 资源文件 12
- 参考文档agents/openai.yaml247 B
- 参考文档ARD.md4.9 KB
- 参考文档config/settings.yaml3.2 KB
- 参考文档PRD.md2.7 KB
- 参考文档references/errors.md2.8 KB
- 参考文档references/examples.md7.0 KB
- 参考文档references/implementation.md1.3 KB
- 脚本scripts/cost_estimator.py7.5 KB
- 脚本scripts/formatters.py7.1 KB
- 脚本scripts/gas_fetcher.py10.9 KB
- 脚本scripts/gas_optimizer.py11.4 KB
- 脚本scripts/pattern_analyzer.py11.0 KB
03 SKILL.md 正文
Grill with docs
Turn unresolved design questions into agreed decisions. Read relevant code, existing decisions, and the conversation before asking questions. Use domain-modeling to maintain terms and record decisions.
Ask a small set of questions about the next consequential choice. Explain the tradeoffs and recommend an option when evidence supports one. Investigate facts yourself. Let the user decide preferences and unresolved product behavior.
Record agreed answers as they arrive. Do not reopen settled choices or invent answers on the user's behalf. Continue independent investigation while waiting. Finish when the requested design questions are resolved, with the decisions, document links, and remaining uncertainty. An interview is not a prerequisite for implementation when the user has already supplied a sufficient spec.
04 同仓库更多 Skills
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler.
nodetool
Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.
wan-2-6-prompting
Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba/wan-2.6/text-to-video, alibaba/wan-2.6/image-to-video, wan-video/wan-2.6-t2v, wan-video/wan-2.6-i2v, wan-video/wan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.
video-workflow
Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.
video-clone
Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.
video-audio-continuity
Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.