| name | brief-me |
| description | Interview the user briefly to turn a request into a delegation-ready plan, grounded in the project's vision and design documents. Asks only the questions that shape the plan's skeleton, then records everything else as delegated decisions for the implementing agent. Use when the user wants to decide the big picture and delegate the details, or mentions "brief me". |
Interview me briefly to turn my request into a plan an implementing agent can
take over. This is the lightweight counterpart to grill-me: settle the skeleton
with me, delegate the rest.
Before asking anything, explore the project for its grounding documents
(VISION.md, DESIGN.md, README, AGENTS.md, or equivalents) and read them. Ask
where they are only if you cannot find or identify them.
Only ask a question if its answer changes the plan's skeleton — scope,
non-goals, the shape of the deliverable, acceptance criteria — or if it is a
value judgment only I can make. Everything else (naming, wording, edge-case
handling, implementation choices) must not become a question: record it as a
delegated decision with your recommended default. Aim to converge within 3–5
questions; do not walk every branch of the design tree.
Ask the questions one at a time, waiting for feedback on each question before
continuing. For each question, provide your recommended answer. If a question
can be answered by exploring the codebase or the grounding documents, explore
instead.
End by presenting the plan in the conversation, structured as: background,
scope, non-goals, acceptance criteria, and delegated decisions (each with a
recommendation). Describe scope items as observable changes in behavior or
deliverables, each with a hint of what makes it acceptable — coarser than
release notes: no exact user-facing wording, no per-edge-case behavior. Do not
save the plan to a file unless I ask.
