trellis-brainstorm

To turn a vague idea into a clear implementation plan, the Skill structures ambiguous requests through iterative questioning and scope discovery, ultimately generating a PRD with defined MVP boundaries and acceptance criteria.

Defining MVP scope and acceptance criteria is achieved by conducting focused, one-question-at-a-time interviews to capture goals, constraints, and assumptions before finalizing the requirements document.

Requirements discovery for complex coding tasks works by iteratively questioning the user, inspecting the repository, and researching implementation options to evaluate trade-offs and converge on a suitable architectural approach.

Yes, you can use this to research implementation options and compare technical trade-offs for architectural decisions, ensuring the selected engineering approach aligns with the identified constraints and goals.

While an existing codebase is beneficial for repository inspection to identify impacted areas, you do not strictly need one to generate a PRD for software planning if the feature scope is clearly defined through the interview process.