brainstorm

Requirements discovery before AI coding involves capturing a clear task and aligning on an MVP early. This Skill automates that process by using a task-first approach to reduce back-and-forth and rework during development.

The best way to create a PRD seed for unclear requirements is to outline an MVP based on the user task description. You can then seed the PRD with goals, knowns, and open questions to drive focused, one-question-per-message Q&A.

The one-question-per-message Q&A approach helps with task management by keeping conversations focused and actionable. It prevents requirement overload by deriving answers from code, docs, and research before asking the user a single, targeted question.

Yes, you can use this process for technical choices with multiple viable paths. It applies a research-first mechanism, performing quick market and open-source checks before proposing options to converge on a clear MVP while leaving room for future expansion.

You should not use an automated requirements discovery workflow for development tasks with already well-defined, fixed requirements. It is specifically designed for situations with unclear, evolving requirements where multiple viable implementation paths exist.