grill-me Skill

Adoption judgment: this is worth using as a pre-coding requirements-alignment step, particularly for ambiguous work, designs with many branches, or tasks where rework is expensive. It should remain a lightweight questioning workflow rather than being treated as a complete engineering methodology or a standalone solution.

Its practical role is to interview the user repeatedly about a plan or design, walk through branches of the design tree, resolve dependencies between decisions, and surface edge cases until both sides have a shared understanding. The direct output is clearer requirements, confirmed choices, and explicit boundaries that another tool or agent can implement. It is not a coding executor, project-management system, product-requirements platform, or decision-maker that replaces the user. A more accurate analogy is a Socratic design reviewer or an interactive requirements checklist.

The entry barrier is fairly low: community write-ups describe the core instruction as only a few short sections, so the main requirement is willingness to answer a sequence of questions rather than complex configuration.