grill-with-docs
Use when stress-testing a plan against the workspace's accumulated domain knowledge and prior decisions — challenge terminology, sharpen fuzzy language, check the plan against what was already decided, and write resolved decisions back. Use when the user says "grill against our docs/decisions", "does this match our domain model", or wants a glossary-aware, decision-store-aware design grill.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grill-with-docs
- description
- Use when stress-testing a plan against the workspace's accumulated domain knowledge and prior decisions — challenge terminology, sharpen fuzzy language, check the plan against what was already decided, and write resolved decisions back. Use when the user says "grill against our docs/decisions", "does this match our domain model", or wants a glossary-aware, decision-store-aware design grill.
03 SKILL.md 正文
Grill With Docs
Overview
Grill a plan, but grounded in the workspace's actual accumulated knowledge instead of a per-repo glossary file. Pull the domain glossary and prior decisions from basic-memory (the semantic D: vault) and the event-ledger, challenge the plan against them, and write every resolved decision back into those same stores.
This beats grilling against a repo-local CONTEXT.md / docs/adr/ set: the stores are cross-project, semantic, always current, and the SessionStart hook replays the ledger after compaction — so the grounding and the decisions both survive context loss.
This is a layer, not a new grill
Do not re-implement the questioning loop. Run the existing grill for the cadence, then add the store-awareness on top:
- Single plan ->
grill-me(interview relentlessly, one question at a time, recommend each answer, explore the codebase instead of asking when a question is answerable). - Wide / under-specified program ->
grill-me-extensive(the 7-step method: scout, diverge, structure, foundation-first, one-at-a-time, capture, converge — plus its grill modes).
grill-with-docs = those, plus the four domain moves and the load/capture wiring below.
Before the grill — load the grounding
Recall is the part everyone skips. Do it first so your challenges are grounded, not generic:
mcp__basic-memory__search_notes/mcp__basic-memory__build_contextfor the domain glossary and prior decisions in this area;mcp__basic-memory__recent_activityfor what changed lately.
During the grill — the four domain moves
Capture decisions back — close the loop
Why this beats CONTEXT.md / ADR files
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files