Step by step to work on Front end feature request

Ever think about your approach of doing a feature request?
I do, and sometimes i don't do it in consistent way,
sometimes i read the requirement and straight to the code, and just missing out some edge cases / scenario and i had to re-work my state, component structure

here are small notes from me, that i think an ideal step-by-step approach to complete a small feature request (consider it like a jira ticket if you use jira)

• Define scenarios that you want to test as a unit test
  Read the Acceptance criteria in the ticket (the requirement).
  write blank test, without assertion first, but write the scenario and step by step to run it by using comment

• if you use TDD approach, start writing the test after that

• if you don’t use TDD approach for some reason, skip and do the unit test after the code is completed.

• Don’t code yet, do little white boarding, or pen/paper to design your state, code, containers, components compositions, etc.
  ensure your design can cover scenario 1 , 2, 3 of the unit test.

• Break your plan into subtasks, make a checklist from it. (todolist, comments, whatever you like, but ensure you keep on track on every small thing you need to do)

⚠️this list will help you to focus.
for example you doing task A, and you just realized you need to add B and C, instead of getting distracted you can add B and C to the list first, and complete A first without switching back and forth doing different things.

• Start code
  develop to cover scenario 1, then cover 2, then 3 then etc…

• If you haven't, Complete the unit test

• Create commit, recommended to follow this approach https://www.conventionalcommits.org/en/v1.0.0/
  then Raise a PR.

you can then continue to test the feature in your staging environment, and once passed, deploy to prod