Analyze project documentation and codebase context to distinguish facts from open decisions.
npx skills add https://github.com/druejaramillo/skills --skill grill-druejaramillo
Please help me install this Agent Skill. Skill: grill Source: https://github.com/druejaramillo/skills/tree/main/project/grill Command: npx skills add https://github.com/druejaramillo/skills --skill grill-druejaramillo
This skill resolves ambiguity in product, design, and architectural planning by forcing a structured, evidence-based dialogue between the user and the AI, preventing costly assumptions.
Invoke the grill skill by asking the assistant to help you evaluate your current project plan for potential risks and missing decisions.
High-intent search queries and answers about installing and using this skill.
Resolving architectural uncertainties requires distinguishing established facts from open decisions through structured inquiry. This approach analyzes existing project documentation and codebase context to provide evidence-based recommendations, preventing costly assumptions during product planning.
Stress-testing a feature plan involves categorizing project inputs into facts, assumptions, and decisions. Facilitating a structured interview process clarifies project direction and identifies missing decisions, ensuring alignment before development begins.
Tracking confirmed architectural decisions uses standardized documentation records and ADRs. Systematically recording these decisions ensures project alignment and maintains a clear history of evidence-based resolutions for future reference.
Existing project documentation and codebase context can be used to evaluate potential risks. Evidence-based resolution prioritizes these documented facts over speculation to identify missing decisions and architectural trade-offs.
Structured decision mapping is needed when facing complex architectural trade-offs that require stakeholder alignment. It resolves ambiguity in product and design planning by forcing an evidence-based dialogue that categorizes inputs into actionable facts and open decisions.
Resolving product ambiguity requires separating facts from open decisions to prevent costly assumptions. This structured approach ensures that planning recommendations are grounded in codebase evidence and documented facts rather than speculation.
ben-mad-jlpExplore codebases, documentation, and commit history to gather project context.
cdalsoniiiCreate and maintain Markdown Architecture Decision Records with a standardized template.
znc15Interrogate project plans and design architectures through iterative decision-tree questioning.
shekerkammaPair success metrics with guardrail metrics to identify trade-offs in analytical workflows.
