trellis-brainstorm

To turn fuzzy ideas into clear implementation plans, use a requirements discovery process that asks high-value questions one at a time and inspects your repository to define an evidence-based MVP before development begins.

Scoping ambiguous feature requirements involves checking repository docs, tests, and configs first to gather evidence, then conducting one-question-at-a-time interviewing to converge on a structured PRD and design notes.

Creating PRD and design artifacts for complex multi-step tasks requires evaluating multiple valid approaches, defining an MVP, and updating structured planning documents when the implementation complexity warrants them.

You do not need existing documentation to start brainstorming new features because the process inspects your repository, tests, and task history directly to answer code-level questions before asking you for input.

You should avoid one-question-at-a-time requirements interviewing for simple, single-step tasks that have only one valid implementation approach and do not require evidence-driven scoping or MVP definition.