grill-with-docs

Investigate and validate plans, designs, and documentation by exploring assumptions and decisions.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/jchildree/The-QUESTION --skill grill-with-docs-jchildree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/jchildree/The-QUESTION/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/jchildree/The-QUESTION --skill grill-with-docs-jchildree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify issues in plans, designs, and documentation by rigorously investigating them, ensuring better decision-making and clearer communication.

Core Features & Use Cases

  • Investigative Workflows: Utilizes a structured problem-solving approach for debugging and architectural decision-making.
  • Shared Memory Layer: Offers an Obsidian vault-based shared memory with SPIFFE-inspired attestation for collaboration.
  • Investigation Board: Enables tracking of decisions and findings with provenance.
  • Provenance Tracking: Ensures every claim is attributed with source, method, and confidence metadata.
  • Zero Hard Dependencies: Operates independently of other systems.
  • Use Case: When a team is reviewing a new architectural design, use this Skill to systematically examine and validate the design's assumptions and decisions.

Quick Start

Use the /grill-with-docs skill to start a grilling session for your new architectural design.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I systematically validate architectural design assumptions before implementation?

Validating architectural design assumptions requires rigorously investigating plans and documentation to systematically explore decisions, implications, and underlying premises for better decision-making and clearer communication.

What is the best way to track provenance for decisions made during a code review?

Tracking decision provenance during code review involves attributing every claim with source, method, and confidence metadata, ensuring findings are systematically documented and traceable throughout the investigation workflow.

How do I stress-test project documentation to find hidden design flaws?

Stress-testing project documentation to find design flaws involves applying structured problem-solving to rigorously examine assumptions and decisions, ensuring issues are identified before implementation begins.

Do I need external dependencies to run an architectural review investigation?

No external dependencies are required to run an architectural review investigation, as the system operates independently with zero hard dependencies while utilizing a shared memory layer for collaboration.

Can I use an Obsidian vault for collaborative design validation and investigation tracking?

Yes, collaborative design validation uses an Obsidian vault-based shared memory layer with SPIFFE-inspired attestation, enabling teams to track decisions, findings, and provenance during architectural reviews.

When should I not use a structured investigation approach for design validation?

Structured design validation investigation is not suitable when you lack sufficient domain knowledge, as the process requires structured problem-solving skills to rigorously examine and validate complex architectural assumptions.