grill-with-docs

Update ADRs and CONTEXT.md to align architectural decisions with context documentation.

3|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill grill-with-docs-malinskibeniamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/malinskibeniamin/skills/tree/main/grill-with-docs
Command: npx skills add https://github.com/malinskibeniamin/skills --skill grill-with-docs-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align architectural decisions with the current CONTEXT.md and ADRs, ensuring decisions are recorded, traceable, and reflected in contextual documentation as they evolve.

Core Features & Use Cases

  • Guided decision interviews: Facilitate a structured, question-by-question process to resolve design trade-offs and capture rationale.
  • Live documentation sync: Update CONTEXT.md and ADRs as decisions settle to keep context and decisions in lockstep.
  • Lazy documentation creation: Create necessary docs structures (ADR entries, CONTEXT sections) only when decisions require them.
  • Governance-focused workflow: Emphasize traceability, alignment, and collaboration without altering codebases.

Quick Start

Initiate a guided interview to resolve each design decision and append ADRs to CONTEXT.md as decisions settle.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I keep ADRs aligned with CONTEXT.md after architectural decisions change?

To keep ADRs aligned with CONTEXT.md, this Skill coordinates architectural decisions by updating ADRs to reflect the latest context documentation as decisions settle during design reviews.

What is the best way to document architectural decisions across multi-context repositories?

Documenting architectural decisions across multi-context repositories is handled using a CONTEXT-MAP.md file to guide setup and sync ADRs across distributed contexts.

How does a guided interview process work for resolving design trade-offs?

A guided interview process for design trade-offs works by facilitating a structured, question-by-question session to resolve decisions and capture rationale.

Does this documentation workflow alter my codebase when syncing ADRs?

This documentation workflow does not alter your codebase, making no automated code changes beyond creating or updating ADRs and CONTEXT.md.

When should I use a lazy documentation workflow for architectural decision recording?

Use a lazy documentation workflow for architectural decision recording during design reviews when you need decisions and context documentation to stay in lockstep.