The basic idea is, for various PRs, there are certain things that need to be done after they are merged. For example, when a new feature (pkg) is added, we need to consider whether that package should be added to the parent namespace. Or we may need to do various follow-up actions, like address a bug in an upstream dep, etc.

The intent of this RFC is to allow maintainers to do something like

/stdlib todo

```text {stdlib=public labels="foo,bar"}
[TODO]: This is the todo subject

This is the body of the todo
```

The stdlib bot would then create a new issue on the main repository having the specified subject and the specified body, along with the corresponding labels.

Yes, we can do this manually, but it can be tedious to click through UI buttons and is enough of a barrier that maintainers don't currently do it. Given that we are merging PRs primarily through the GitHub UI, being able to add a comment for the bot to open a new issue could reduce the barrier.

Note the attributes (which is an extension to Markdown that we'd explicitly parse):

• stdlib: attribute indicating where to open the issue. Values: public (on main repo), private (on internal todo repo)
• labels: labels to add on the opened issue. Comma separated-list (assumes that we never add a label with a comma, which we shouldn't).