Grill With Docs
Runs a docs-anchored grilling session: challenges a plan against a project's CONTEXT.md language and recorded ADR decisions.
Before & after
Same prompt, same agent — the only difference is the skill.
Splitting a monolith is a significant decision with tradeoffs. There are good reasons to do it, like independent scaling and team autonomy, but it introduces complexity in distributed systems, operational overhead, and testing challenges. It really depends on your team size, current pain points, and long-term vision. Do you have specific constraints driving this question? What parts feel like they need to be separate?
DECISION ANALYSIS vs. EXISTING DOCS CONFLICT WITH ADR-003 (Monolith-First Policy) Doc states: Stay monolith until services exceed 200k lines or 8+ teams Current state: 156k lines, 4 teams Conclusion: Violates established threshold policy Action Required: Update ADR-003 or defer split ALIGNMENT CHECK vs. CONTEXT.md Documented values: "Operational simplicity over microservices cleverness" Current proposal: Splits payment + user services Risk: Creates 3 database schemas, 2 new async queues Missing from proposal: Operational runbook for split deployments CRITICAL GAPS 1. ADR-003 suggests deferral; new pain points not yet in docs 2. CONTEXT.md emphasizes observability first; no tracing plan shown 3. Team structure doc (outdated) assumes monolith ownership model UPDATES TO WRITE • ADR-004: Justify split against original threshold criteria • CONTEXT.md: Add "Distributed systems" as new value if proceeding • Team Structure: Define on-call model for split services RECOMMENDATION: Refactor payment service to separate package first; defer full split until ADR reviewed
About this skill
name: grill-with-docs description: Use when Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisio...
Grill With Docs
Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions "grill with docs".
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the grill-with-docs skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Grill With Docs; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: grill-with-docs
description: Use this skill when a user wants to stress-test a plan against a project's existing documented language and decisions, or explicitly asks to grill a plan with docs.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Grill With Docs
Runs a docs-anchored grilling session: challenges a plan against a project's CONTEXT.md language and recorded ADR decisions, updating those files inline as things get sharpened.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.