signalproof-grill-with-docs

Stress-test plans and designs while capturing resolved terminology and durable architectural decisions.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-grill-with-docs-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-grill-with-docs
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-grill-with-docs
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-grill-with-docs-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design and planning discussions often mix unresolved questions with premature documentation, producing glossaries and ADRs that record speculation as fact. This Skill separates rigorous decision interrogation from durable documentation so only genuinely resolved terminology and tradeoff decisions become permanent records. ## Core Features & Use Cases - Decision-Tree Interrogation: Runs structured grilling against unresolved decision frontiers before anything is documented. - Selective Glossary Capture: Proposes exact terminology deltas only when terms are actually resolved, keeping glossaries free of specs and scratchpad noise. - ADR Threshold Gating: Creates or proposes Architecture Decision Records only for decisions that are costly to reverse, surprising without context, or the result of genuine tradeoffs. - Use Case: During a product architecture review, use this Skill to grill the team on open design questions, then record only the settled canonical terms and the one irreversible database decision as an ADR, leaving unresolved items explicitly marked. ## Quick Start Ask the AI to grill your current design plan and capture only the resolved terminology and durable architectural decisions as glossary and ADR proposals.

Frequently Asked Questions about signalproof-grill-with-docs

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

FAQPage Schema
How do I stress-test a design plan before implementation?▼

Run a structured grilling pass that walks the unresolved decision tree, surfaces contradictions between stated intent and existing artifacts, and labels open questions. Only after decisions stabilize should anything be recorded as durable documentation.

When should I create an Architecture Decision Record?▼

Create an ADR only when a decision is costly or difficult to reverse, surprising without its context, or the result of a genuine tradeoff among alternatives. Ordinary implementation details should not generate ADR noise.

How do I keep a project glossary from becoming a specification?▼

Record only canonical terms with concise definitions, key distinctions, and scope once terminology is actually resolved. Exclude implementation guidance, scratchpad notes, and changelogs, which belong in other documents.

Can this Skill edit repository documentation directly?▼

No. The composition does not grant file-write authority by itself. It proposes exact glossary and ADR deltas, and repository writes require separate explicit human authorization followed by verification.

What happens when documentation, code, and human intent disagree?▼

The conflict is surfaced explicitly rather than silently resolved. The disagreement is routed to the appropriate evidence source or owner decision before any durable state is updated.