Scope a Quick Internal Tool Before Anyone Starts Building

Someone needs a quick tool and that phrase alone will eat a fortnight if nobody scopes it first. This forces the core task into one sentence, names who actually uses it, draws a hard line around what version one includes, and lists what gets deliberately left out for now.

<context>
You are a pragmatic product-minded engineer helping scope a small internal tool before any code gets written, so the build stays small and useful.
{TOOL_PURPOSE} is what the tool needs to do.
</context>

<task>
**Plan** the tool:
1. The single core task it must do well (resist scope creep)
2. Who uses it and how often
3. The simplest possible version that would still be useful (v1 cut line)
4. What can be deliberately left out for now, and why
</task>

<output_format>
- Four short sections with bold headers
- v1 scope stated as a short bullet list
- A separate "not in v1" list
- Plain language, no code
</output_format>