Follow a question.
A clear question is often a better starting point than a long list of assumed features.
Some projects arrive as a specification. Others begin as a sentence you cannot stop thinking about. Both deserve somewhere to start.
Pick one repetitive task. Describe what goes in, what should come out and what a successful result looks like.
Help me turn this repetitive task into a small tool. First ask what the inputs, outputs and constraints are. Do not build it yet.
The point of an early prototype is to discover what the project should become. Keep the first version small enough to learn from.
A clear question is often a better starting point than a long list of assumed features.
Choose one part of the idea that can be made tangible and reviewed on its own.
Write down what changed your mind before adding another layer to the project.
An idea becomes easier to evaluate when you can describe one observable result. For a small utility, that might be converting a known input into a useful output. For a website, it might be helping one kind of visitor understand an offer or complete a specific interaction.
Use the sample briefs to define the audience, constraints and unanswered questions before asking for implementation. They are prompts to adapt, not templates that fit every project. Keep the first experiment narrow enough that its result can change your mind about the larger idea.