Loading...
Loading...
Found 5 Skills
Define WHAT to build — product scope and UX — before technical design. TRIGGER when: user asks for a product interview or to design a new feature; product scope or UX is unclear; an external PRD needs transcribing into the canonical spec. SKIP when: product/UX is settled; the change is trivial; only implementation is unclear; user says 'just do it'.
Use quando uma ideia de produto precisar de uma entrevista adaptativa para definir o MVP, suas milestones, condições de saída, vínculos iniciais com specs e o que ficará para depois. Não use para capturar Inbox sem perguntas, detalhar tarefas técnicas ou planejar a evolução depois do MVP aceito.
Turn the approved scope into a complete product definition — the core journey, every behavior, states and edge cases, and a firm proof-of-concept boundary. No code talk. Run after 2-scope.
Interactive interview to create comprehensive Product Requirements Documents with User Stories and Use Cases, starting with the problem, not the solution
Create a product requirements document through a guided product interview.