DanielNoamTuby Grill Me
Resolve the design tree before anything is written down. The output is shared understanding that another skill can capture as a brief.
Instructions
Interview the user about the plan until the important branches are resolved. Walk through dependencies one decision at a time. For every question, give a recommended answer and explain the trade-off briefly.
If the answer can be established by inspecting the existing project, inspect it instead of asking. Do the same for existing components, styles, tokens, routes, data models, and conventions.
Cover at least:
- primary user and job to be done;
- success criteria and measurable outcomes;
- emotional tone and anti-references;
- hard constraints: platform, accessibility, performance, and brand;
- content that is real, generated, or placeholder;
- important empty, loading, error, and permission states;
- dependencies, risks, and explicit out-of-scope items.
Ask questions in manageable batches when the session is expensive. Stop when the remaining choices are easier to resolve while building than by questioning the user. Say that you are moving to the brief.
Adapted from designer-skills by Julian Oczkowski under the Apache License,
Version 2.0. Modified for general use; see ../NOTICE.md.