Conduct a requirements review based on the requirements analysis document provided by the current user, and point out unclear, incomplete, problematic interaction, and ambiguous parts in the requirements.
If no specific requirements analysis document is provided, read the requirements-analysis.md file in the output/doc folder under the root directory for the requirements review.
If there is no requirements analysis document, ask the user to provide one.
Based on the requirements review in the first step, guide the user to answer and confirm for unclear content; provide suggestions for multiple solution approaches and ask the user to confirm.
Send the revised requirement points to the user for confirmation.
Refer to the requirements analysis document provided by the user, rewrite the requirements analysis document, save it in the output/doc folder under the root directory of this output, named requirements-analysis-review.md. It must include the main adjustment content of this review.