grill-with-llm-wiki

Stress-test plans against an LLM-maintained wiki using articles, index, and log.

8|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ccomkhj/skills --skill grill-with-llm-wiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-llm-wiki
Source: https://github.com/ccomkhj/skills/tree/main/grill-with-llm-wiki
Command: npx skills add https://github.com/ccomkhj/skills --skill grill-with-llm-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents you from building on shaky assumptions by stress-testing your plan against what an LLM-maintained wiki already records, surfacing contradictions, stale claims, missing cross-links, and synthesis gaps.

Core Features & Use Cases

  • Read-only wiki interrogation: Probes an existing wiki’s articles, index, and log without writing anything back.
  • Branch-based tension discovery: Organizes questions by failure mode (term clashes, stale claims, orphan concepts, conflict annotations).
  • Source-trace verification: Follows an article’s Raw references to verify what the underlying sources actually say before challenging the plan.
  • Convergence summaries: Records resolved branches, open items, and accepted risks at the end of the grilling session.

Quick Start

Run grill-with-llm-wiki and ask it to pressure-test your current plan against your existing wiki, one focused question at a time.

Frequently Asked Questions about grill-with-llm-wiki

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

FAQPage Schema
How do I stress-test a product plan against an existing knowledge base?

To stress-test a product plan against a knowledge base, you interrogate the wiki's articles, index, and log to surface contradictions, stale claims, and synthesis gaps before finalizing decisions.

What is assumption testing in decision tracking and when do I need it?

Assumption testing in decision tracking validates current plan terminology and logic against recorded wiki history. You need it when existing knowledge conflicts with new product, design, or data planning scenarios.

How do I verify source traces during a plan review?

You verify source traces during a plan review by following an article's Raw references to check underlying sources. This synthesis verification ensures original documents actually support the recorded claims before challenging the plan.

Can I interrogate my wiki for missing cross-links and term clashes without modifying it?

Yes, you can interrogate your wiki for term clashes, orphan concepts, and missing cross-links without modifying it. The process requires read-only wiki discovery, ensuring safe non-writing behavior toward all wiki artifacts.

What is the best way to organize tension discovery questions for requirements planning?

The best way to organize tension discovery questions for requirements planning is through branch-based generation. This categorizes questions by failure modes like term clashes, stale claims, and conflict annotations for focused resolution.

What are the limitations of using an LLM-maintained wiki for plan review?

Limitations of using an LLM-maintained wiki for plan review include relying on the wiki's current index and log completeness. The process cannot write back or fix artifacts, only identify accepted risks and open items in convergence summaries.