Analyze design and implementation plans against code and documentation.
npx skills add https://github.com/alexandersumer/config --skill grill-me-alexandersumer
Please help me install this Agent Skill. Skill: grill-me Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/grill-me Command: npx skills add https://github.com/alexandersumer/config --skill grill-me-alexandersumer
This Skill helps identify potential flaws in design, proposal, implementation plans, and architectural choices by applying a structured questioning approach.
CONTEXT.md or ADRs if needed.Use the grill-me skill to grill a design plan on its potential vulnerabilities.
High-intent search queries and answers about installing and using this skill.
Stress testing a design plan involves challenging its code, domain language alignment, and existing documentation to identify critical, architecture-altering decisions and potential vulnerabilities before implementation begins.
You evaluate architectural decisions by applying a structured questioning approach that targets vocabulary discrepancies and checks alignment with existing project documentation like CONTEXT.md and ADRs.
Yes, stress testing explicitly requires alignment with existing project documentation, identifying vocabulary discrepancies between your proposal's terminology and established decisions, and suggesting updates to CONTEXT.md or ADRs if needed.
The best way to uncover vulnerabilities is to grill the plan against code, domain language, and existing decisions to isolate the most critical, architecture-altering choices that require immediate attention.
Existing ADRs are not strictly required to perform a design evaluation, but having them or a CONTEXT.md file allows the stress test to better identify vocabulary discrepancies and suggest accurate documentation updates.
gilesknapStress-test decisions against CONTEXT.md and ADRs to surface terminology conflicts.
rodrigotoledoGenerate Architecture Decision Records in MADR, Nygard, or Y-Statement formats.
ybbms777Challenge technical documents by testing premises and surfacing unstated assumptions.
NodeJSmithCritique code designs using three adversarial reviewer personas.