grill-with-docs

Validate implementation plans against project domain models and documentation.

1|Updated Aug 1, 2020
One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill grill-with-docs-johanneskonings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill grill-with-docs-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of building plans that conflict with your project's existing domain language, documented architectural decisions, and established context, which leads to rework, miscommunication, and avoidable technical debt.

Core Features & Use Cases

  • Plan Stress-Testing: Relentlessly interviews you about every aspect of your design to uncover gaps, contradictions, and unaddressed dependencies before implementation starts.
  • Terminology Alignment: Challenges vague or conflicting terms against your project's existing CONTEXT.md glossary to ensure consistent, unambiguous language across the team.
  • Inline Documentation Updates: Creates or updates ADRs and CONTEXT.md entries in real time as decisions crystallize, so documentation stays in sync with your planning process.
  • Codebase Cross-Checking: Verifies that your planned behavior matches existing code implementation, surfacing contradictions early.
  • Use Case: For example, if you are designing a new order cancellation feature, this Skill will confirm your definition of "cancellation" aligns with the project glossary, check if the codebase already supports partial cancellations, and prompt you to document the decision as an ADR if it involves irreversible trade-offs between customer experience and operational overhead.

Quick Start

Use the grill-with-docs skill to stress-test my plan for adding a user profile editing feature against our existing domain documentation and codebase.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I align new feature designs with existing domain documentation and codebase implementation?

Plan validation involves stress-testing your design through relentless interviews to uncover gaps, contradictions, and unaddressed dependencies against existing domain models before implementation begins to prevent rework and technical debt.

What is the best way to create ADR files and keep project documentation in sync during planning?

Creating ADR files during planning is best handled by inline documentation updates that generate ADRs and CONTEXT.md entries in real time as decisions crystallize, ensuring documentation stays synchronized with your planning process.

How do I validate project terminology and prevent conflicting terms across the team?

Validating project terminology requires challenging vague or conflicting terms against your project's existing CONTEXT.md glossary to ensure consistent, unambiguous language across the team during design reviews.

Does design review work with legacy code and prior architectural trade-off decisions?

Design review works with legacy code and prior architectural decisions by applying codebase cross-checking to verify planned behavior matches existing implementation, surfacing contradictions early before any development starts.

When do I need to document architectural decisions as ADR files?

You need to document architectural decisions as ADR files when your plan validation process involves irreversible trade-offs, such as choosing between customer experience and operational overhead, requiring permanent record keeping.