Tag focus-area-proposal issues with web-features' IDs

Would you consider adding a mechanism to associate focus area proposal issues to their corresponding web-features?

Context

• Focus area proposal issues are filed each year, as new issues on the repository, by members of the web community, in an attempt to get their ideas accepted.
• web-features is a W3C WebDX Community Group project which aims at cataloging the developer features of the web platform, in order to provide hierarchical and summarized feature support data, in a developer-friendly way. One of the outcomes of web-features is the Baseline idea, which you can see at the top of MDN reference pages and on caniuse.com.

Proposal

When new focus area proposal issues get created on the repo, somehow link them to the corresponding web-features entry.
For example, the CSS Module Scripts proposal corresponds to the css-modules feature on the web-features repo (you can also see the feature in a simple way here).
If I had to propose a mechanism for doing this, it would probably be by adding a label to the issue on GitHub that looks like web-features:<the-feature-id>. So, in this example, it would be web-features:css-modules.

Why

The web-features project's main goal is to create a catalog in which, all features that developers can make use of to achieve particular end-user scenarios, have unique IDs, and where these unique IDs can then be referenced by other sources of open web data in the community.
The goal of the project is NOT to make a copy of the other data, and maintain it in our GitHub repo. For example, browser-compat-data points to web-features by using a web-features:<id-of-feature> tag. MDN will soon point to web-features too. The features listed in State of CSS/HTML/JS surveys are also being mapping web-features IDs. And so on.
Interop focus area proposals constitute another source of valuable data about features of the web platform. In particular, they provide valuable insights into what developers need, and how much they need it.

Start by reviewing focus area proposal issue 597 and its linked css-modules feature in the web-features repository. Compare the proposed web-features: label convention with the repository's existing issue-label workflow. Done means corresponding focus-area-proposal issues can be associated with discoverable web-features IDs.