grill-with-docs

Stress-tests plans against domain glossaries and records decisions in CONTEXT.md and ADRs.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill grill-with-docs-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/grill-with-docs
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill grill-with-docs-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often embed fuzzy terminology and undocumented trade-offs that later confuse teams or contradict the codebase. This Skill runs a structured interrogation of your plan against your project's existing domain language and documented decisions, updating CONTEXT.md and ADRs inline as decisions crystallize. ## Core Features & Use Cases - Relentless plan interrogation: Asks one question at a time, walking each branch of the design tree and providing a recommended answer for every question. - Terminology sharpening: Challenges terms that conflict with the existing CONTEXT.md glossary and proposes precise canonical vocabulary for vague language. - Inline documentation updates: Updates CONTEXT.md the moment a term is resolved and offers ADRs only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: Before implementing a new order-cancellation feature, run a grilling session to reconcile your plan with the existing glossary, discover that the code only supports full cancellation, and record the partial-cancellation decision as ADR 0003. ## Quick Start Ask the agent to grill you on your implementation plan for a new feature and update the project glossary and ADRs as decisions are made.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a software design plan before implementing it?

Run a grilling session that interviews you about every aspect of the plan, one question at a time, with a recommended answer for each. Questions that can be answered by exploring the codebase are resolved through code exploration instead of asking you.

How do I keep a project glossary consistent with my code?

Maintain a CONTEXT.md glossary at the repo root and challenge any term usage that conflicts with it during planning. When a term is resolved, update CONTEXT.md immediately rather than batching changes, keeping it free of implementation details.

When should I write an Architecture Decision Record?

Write an ADR only when all three conditions hold: the decision is hard to reverse, it is surprising without context, and it resulted from a real trade-off between alternatives. If any condition is missing, skip the ADR to avoid documentation noise.

Does this approach support repositories with multiple bounded contexts?

Yes. If a CONTEXT-MAP.md exists at the repo root, it lists each context, its location, and its relationships. The session infers which context the current topic belongs to and asks when unclear, with context-specific ADRs stored alongside each context.

What are the limitations of interview-based plan review?

The session depends on your answers and the existing documentation, so undocumented decisions and unexplored code paths can be missed. It also creates documentation lazily, so repos with no prior CONTEXT.md or ADRs start from scratch during the first session.