chore: problem statement and development plan adjustment

[aarnphm]

The following feedback from Hunter highlights areas for improvement in the Problem Statement, Goals, and Development Plan. The suggested changes aim to enhance clarity, readability, structure, and completeness:

1. Problem Statement:

   • Condense the problem statement into a concise paragraph that motivates the problem.
   • Avoid including optional stretch goals in the inputs/outputs section.
   • Revise the environment section to focus on "what is being implemented" rather than "how it is being implemented."
   • Reframe the beginning motivation to avoid first-person phrasing (e.g., replace "we" instead of "me").

2. Goals:

   • Add more goals related to user interactions with the software (e.g., user-friendliness, intuitiveness).
   • Expand on the goals to include information about their purpose and how to measure them.
   • Ensure goals are properly motivated and distinguish them from listed requirements.

3. References and Links:

   • Properly implement links and references for readability.
   • Fix any spelling and grammar errors throughout the document.

4. Team Roles:

   • Revisit the roles section to make roles more flexible and better defined.
   • Remove the "BDFL" role and replace it with a more adaptable structure.

5. Git Workflow Plan:

   • Add more details about issue templates, tags, and other organizational aspects for the Git workflow.

6. POC Demo Plan:

   • Rewrite the POC Demo Plan risks section using clear language that a layperson can understand.

7. Reflections:

   • Add more detail to the reflections section, particularly in terms of requirements and addressing specific questions.
   • Ensure the reflections align with the goals and motivation of the document.

8. Formatting and Style:

   • Fix formatting issues to improve readability.
   • Ensure the document is free of spelling and grammar errors.