skills/writing-research/grilling-designs/SKILL.md
Interview the user one decision at a time to stress-test a plan or design until goals, constraints, assumptions, tradeoffs, risks, and verification are explicit. Use only when the user asks to be grilled or names “grilling designs.”
npx skillsauth add narumiruna/agent-skills grilling-designsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build a live decision tree from the user's goal, constraints, stakeholders, flows, dependencies, risks, and success criteria.
Prioritize goal/success, constraints/non-goals, architecture facts, interfaces/data/state ownership, failure/security/migration/rollout/observability, then test and verification criteria.
Do not draft a plan while major branches remain. When the user requests a plan after the interview, use writing-plans with the agreed decisions.
Stop when no major unresolved branch remains. Return the agreed decisions, remaining risks or unknowns, and the recommended next action.
development
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.