skills.rest
assofohdz
assofohdzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

grill-with-docs

Align software plans with domain models, ADRs, and CONTEXT.md terminology.

25|5|Updated Apr 22, 2017
Search Tags:#codebase exploration#architectural decisions#documentation updates#context.md#terminology management#domain alignment#adr creation
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill grill-with-docs-assofohdz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.agents/skills/grill-with-docs
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill grill-with-docs-assofohdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates misalignment between proposed software plans and existing domain terminology, documented architectural decisions, and project context, preventing costly rework and stakeholder confusion caused by vague language or unrecorded trade-offs.

Core Features & Use Cases

  • Domain alignment grilling: Relentlessly questions plan details to resolve conflicts with existing CONTEXT.md glossary terms and ADR decisions.
  • Terminology sharpening: Identifies vague or overloaded terms and proposes precise canonical language to eliminate ambiguity across engineering and domain teams.
  • Inline documentation updates: Automatically updates CONTEXT.md and creates ADRs as decisions crystallize during the session, ensuring documentation stays in sync with design work. Use case: Ideal for engineering teams designing new features or architectural changes where alignment with existing domain rules and documented decisions is critical to avoid rework.

Quick Start

Use the grill-with-docs skill to walk through your proposed feature plan step by step, resolving terminology conflicts and documenting key decisions as you go.

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 plans with existing domain models and documentation?▼

To align feature plans with domain models, you can stress-test proposed software plans against existing CONTEXT.md glossaries and documented architectural decisions, resolving terminology conflicts and domain misalignment during the design phase.

When do I need to create an ADR for architectural trade-offs?▼

You need to create an ADR when non-obvious architectural trade-offs are identified during plan validation, ensuring that design decisions and their context are documented inline as they crystallize in real-time.

How do I update CONTEXT.md terminology during architectural design discussions?▼

You can update CONTEXT.md terminology automatically by identifying vague or overloaded terms during design discussions and proposing precise canonical language to eliminate ambiguity across engineering and domain teams.

Can I use domain alignment grilling for cross-team terminology conflict detection?▼

Yes, domain alignment grilling supports cross-team terminology conflict detection by relentlessly questioning plan details to resolve conflicts with existing standardized project terminology and documented ADR decisions.

What is the best way to prevent domain misalignment when proposing architectural changes?▼

The best way to prevent domain misalignment is to walk through proposed plans step-by-step, validating them against existing domain rules and documented decisions, while updating inline documentation to stay in sync with design work.

Does this approach work for real-time terminology sharpening during engineering workflows?▼

Yes, this approach applies to engineering workflow scenarios involving feature design and architectural trade-off discussions, satisfying requirements for real-time terminology conflict detection and inline CONTEXT.md updates.

Related Skills

Explore More Software Engineering Skills→
arthur-debertarthur-debert

grill-me-with-docs

Challenge plans against CONTEXT.md, ADRs, and spec documents.

Community
Advanced
nseluganseluga

domain-modeling

Collaboratively define and standardize project domain terminology and record architectural decisions.

Community
Advanced
roerohanroerohan
27

grill-with-docs

Validate implementation plans against project domain models and architectural decisions.

Community
Intermediate
AskTinNguyenAskTinNguyen

documentation-and-adrs

Capture architectural decisions with ADR templates and lifecycle guidance.

Community
Intermediate