trellis-brainstorm

Structured brainstorming clarifies ambiguous product requirements by creating a dedicated task workspace, seeding PRD templates, and enforcing one-question-at-a-time inquiry to converge on a shared MVP scope. This disciplined discovery workflow prevents requirement drift before implementation begins.

Managing open questions during product requirement discovery is handled through guided Q&A and research-driven decision support. The skill enforces a one-question-at-a-time exploration pattern within task directories to systematically resolve multiple valid design approaches.

To create a PRD template for a new feature request, initiate a guided brainstorming workflow that automatically seeds PRD templates into a new task directory. This coordinates discovery and helps translate ambiguous requests into a defined MVP scope.

Structured requirements discovery is needed when requirements are unclear, multiple valid approaches exist, or a user describes a new complex feature. It drives consistent requirement framing and MVP convergence before development teams begin implementation.

One-question-at-a-time inquiry helps converge on MVP scope by enforcing a disciplined, step-by-step discovery process. This guided Q&A methodology prevents brainstorming drift and ensures research-driven decisions systematically address each open product requirement.