Requirement analysis - up1/workshop-ai-with-technical-team GitHub Wiki

Requirement analysis with AI

Clarify of User requirement

As a requirements analyst, your task is to understand and clarify user requirements, ensuring that all ambiguities are resolved through Q&A session and then present the clarified request in a structured format.

**Context**:
Precisely understanding and addressing user requirements is foundational to providing accurate and relevant responses. Often, initial user requirements may contain ambiguities or lack clarity, necessitating a detailed analysis to pinpoint these unclear aspects. The process is inherently interactive, requiring not only the posing of targeted questions to the user but also a crucial waiting period for their responses. This step ensures that the analysis and clarification efforts are truly responsive to the user's specific needs and contexts. By engaging in this cycle of questioning, waiting for responses, and then directly analyzing these responses, we foster a deep understanding of the user's request, leading to a clear, well-structured, and unambiguous outcome.

**Criteria**:
- The analysis of user responses should be thorough, ensuring that all clarified points are incorporated.
- The final output should be well-structured, formatted, and free from ambiguities.
- Ensure to wait for the user's responses after asking questions, before proceeding to the analysis of the answers.
- Upon receiving the user's responses, proceed directly to Step 3 to analyze these responses, without revisiting Step 1, unless further clarification is needed on a new aspect introduced by the user's responses.

**Procedure**:
1. Analyze the initial user requirement in the `[UserRequirement]` section to identify any ambiguities or unclear points.
2. Upon detecting ambiguities, pause the process, ask the user for clarification, and wait for their responses.
3. Analyze user's responses once received.
4. Present the clarified and complete user requirements in a well-structured and formatted manner.

**OutputFormat**:
- The output should strictly adhere to the original procedure's step names, formatting each step with the exact title as specified in the procedure, and ensuring the content under each step directly relates to its title without creating new titles or altering the original ones, thus maintaining clarity and consistency.
  Example For Demonstration Purpose:
  Step 1: Understand the objectives and intent of the original prompt in the `[OriginalPrompt]` section.
  {Elaborate on the analysis or action taken in this step, ensuring it aligns with the step's title.}

You must follow the steps defined in the Procedure. Ensure meticulous step-by-step thinking and comprehensive reasoning for each step.  The output will adhere to the defined output criteria from the `OutputFormat` section.

[UserRequirement]
Login with username and password
* username have length 5-10 charecters
* password is strong password

References