skills.rest
a35506322
a35506322COMMUNITY
Explore all skills by this author →
GitHub

grill-with-docs

Stress-test project plans against domain documentation, codebase, and ADRs.

1|Updated Jan 25, 2026
Search Tags:#documentation#adr#plan-validation#code-alignment#domain-language#context-glossary#requirement-grilling
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill grill-with-docs-a35506322
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/grill-with-docs
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill grill-with-docs-a35506322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building features that misalign with your project's established domain language, documented architectural decisions, and actual codebase implementation, preventing costly rework and team miscommunication.

Core Features & Use Cases

  • Plan Stress-Testing: Challenges every aspect of your proposed plan against existing CONTEXT.md glossaries, ADRs, and code to catch contradictions and fuzzy terminology early.
  • Domain Language Alignment: Flags conflicting or vague terms, proposes precise canonical language that matches your project's existing glossary, and updates documentation inline as decisions are finalized.
  • Use Case: When designing a new user cancellation feature, the Skill will flag if you use the term "cancel" when your project glossary defines full cancellations as "order void" and partial cancellations as "reversal", ensuring consistent terminology across the team.

Quick Start

Ask the AI to grill your proposed e-commerce order management feature plan against the project's existing domain documentation and codebase to catch all misalignments before you start implementation.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I stress-test a software plan against existing project documentation?▼

Stress-testing a plan against project documentation involves challenging your proposed features against existing domain glossaries, architectural decisions, and codebase implementation to catch terminology contradictions and misalignments before implementation begins.

What is domain language alignment and why does it matter for feature design?▼

Domain language alignment ensures your feature design uses precise canonical terminology matching your project's existing glossary, preventing team miscommunication and costly rework caused by vague or conflicting terms like using "cancel" instead of defined terms such as "order void".

How do I validate code alignment before starting a system refactoring project?▼

Validating code alignment before refactoring requires surfacing contradictions between your planned behavior and actual code implementation by cross-referencing proposed changes against recorded architectural decisions and established domain documentation to ensure structural consistency.

Can I update project glossaries and ADR records inline while reviewing a feature plan?▼

Updating project glossaries and ADR records inline is supported during plan stress-testing, automatically crystallizing architectural decisions and refining domain language definitions directly as contradictions are flagged and terminology conflicts are resolved.

Does this approach work for architectural trade-off scenarios requiring alignment with prior documented choices?▼

Architectural trade-off scenarios requiring alignment with prior documented choices are fully supported, applying stress-testing logic to enforce consistent domain language and verify that new architectural decisions respect existing recorded constraints and codebase realities.

What are the limitations of relying solely on codebase implementation to catch plan misalignments?▼

Relying solely on codebase implementation misses undocumented domain language nuances and architectural context, making it necessary to stress-test plans against both documented decisions and code simultaneously to surface all behavioral and terminology contradictions.

Related Skills

Explore More Software Engineering Skills→
matt-rileymatt-riley
1

grill-with-docs

Elicit and record domain terms and ADR decisions during planning.

Community
Advanced
lucidfrontier45lucidfrontier45

planner

Generate Markdown implementation plans for software features without modifying the codebase.

Community
Advanced
docs-plusdocs-plus
88

grill-with-docs

Validates project plans against CONTEXT.md glossaries and ADRs to catch terminology mismatches.

Official
Intermediate
EmergenceAIEmergenceAI
2

validate-plan

Validate implementation plans against success criteria and architectural standards.

Official
Advanced