One-click install
npx skills add https://github.com/infantesromeroadrian/arca-agent --skill grill-with-docs-infantesromeroadrian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/infantesromeroadrian/arca-agent/tree/main/template/skills/grill-with-docs
Command: npx skills add https://github.com/infantesromeroadrian/arca-agent --skill grill-with-docs-infantesromeroadrian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables domain experts to challenge their plans against an existing domain model, ensuring clarity, adherence to conventions, and precision in documentation.

Core Features & Use Cases

  • Stress-Testing Plans: Analyze plans for consistency with domain conventions and potential pitfalls.
  • Documentation Enhancement: Update terminology and inline documentation as decisions evolve.
  • Use Case: Use the Skill during C1 Discovery to validate ML Problem Statements or in C4 Design to cross-check ADR drafts for potential drift.

Quick Start

Activate the grill-with-docs skill to engage in a thorough planning review.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I validate a domain model against new design proposals?

Stress-test domain-specific proposals by challenging them against a documented domain model, identifying terminology discrepancies, and validating design decisions to promote consistency and reduce ambiguity.

What is the best way to check for terminology discrepancies during code review?

Perform domain model scrutiny to compare domain-specific terms and relationships against evolving inline documentation, ensuring plan validation catches terminology discrepancies before design drift occurs.

Can I use domain model scrutiny to cross-check ADR drafts for potential drift?

Yes, you can cross-check ADR drafts for potential drift by challenging domain-specific proposals against a documented domain model during C4 Design to validate design decisions and ensure consistency.

Does plan validation require existing domain context documentation?

Yes, plan validation requires existing domain context documentation because the process relies on knowledge of domain-specific terms and relationships to challenge proposals and refine terminology.

Why does domain modeling fail to prevent ambiguity in inline documentation?

Domain modeling fails to prevent ambiguity when inline documentation is not updated as decisions evolve, requiring term clarification and domain model scrutiny to enhance consistency across proposals.

When should I stress-test plans against domain conventions during discovery?

You should stress-test plans against domain conventions during C1 Discovery to validate ML Problem Statements and identify potential pitfalls before proceeding with detailed design.