Backlog/issues feature?

[EqualAPriori]

Hi all, really great work!

Wanted to get feedback: oftentimes while working, I think of / encounter issues that I don't quite yet want to flesh out into a spec (usually haven't thought about it enough yet), but still want to track.

Right now I manually log this to a single issues.md file somewhere, but I'm wondering if this is maybe something I should manage with openspec (e.g. just create a new spec, so it's under changes, or if this might even be a new openspec slash command + file organization), or with a gh slash command.

Wanted to see what people recommend / use in their daily workflows.

Thanks!

[TabishB]

@EqualAPriori Sometimes I just create a "change" with just a "proposal.md" file that I then flesh out later. I do agree that something more baked into openspec would be nice, we're trying to make sure the core loop is good before expanding into things like this.

[EqualAPriori]

got it, thanks!