Feat: How to Capture All Requirements for our App?

[nelsonic]

Story

As a person who is researching and evaluating adopting a new tool
that will enhance my personal effectiveness [sometimes referred to as "productivity"...]
I want to have a comprehensive list of the features
So that I know immediately what is already available in the App

List

The list of features that our App already has should be easily extractable from the Release Notes dwyl/product-ux-research#45

Initially the list can be written manually e.g:

1. Capture anything on your mind and save it in a "second brain"
2. Categorise the items you capture so you can organise and prioritise them
3. Start a timer on an item to track how long it takes you to perform
4. etc.

But longer term we need a more systematic approach that automates some or all of this process using the data in our system to automatically generate the list of features for the /features page of dwyl.com

Note: Not suggesting we are going to capture all the requirements up-front, heavens no! That's waterfall! 🤮
Rather, we need a way of capturing the ongoing requirements as the App evolves and organising them systematically. 📝

If you have any ideas for how to go about this, please comment below. 💬 🙏

[LuchoTurtle]

Apparently, there are a few resources/frameworks that allow requirement tracking and management.
OpenFastTrace is one of them.
Doorstop is another (seems to be the most starred when it comes to requirements management), which seems to have a few side-projects that focus on improving its GUI, like doorstop-edit.

However, I feel like this is a bit overkill from an MVP standpoint. I think having a dedicated Github Project and using a Kanban is perfectly fine to capture the progress status of each requirement. It only starts making sense using a dedicated program like Doorstop when the requirements list becomes too big to manage.

Just my two cents 👍