Consider [?] items...

[NiloCK]

Sometimes I write down something that I might need to do in the future, pending outcomes outside of my influence.

This is essentially a pre-flag for [ ] items which are more likely than average to become [~] items.

[jotaen]

Thanks for sharing your idea. I think [?] could be a useful status, and it should also be obvious what it means.

The only caveat is that I’d like to keep the overall number of statuses contained to like a handful, to keep things simple. So I first wanted to see whether or what other ideas come up over time, before adding a new one. I think, [?] could be a high-up candidate, though.

[shah]

Agreed, @NiloCK [?] could be a great additional status for individuals but IMHO it's more important in case a TODO list is stored in Git for use by multiple collaborators. Some collaborators would find it easier to add a [?] as a suggested item and it would be history-tracked as such.

It could have a very simple workflow - a [?] is a potential start state equal to [ ] when the submitter (collaborator) is not sure whether it's a real task or a potential task.

Linters for xit could then differentiate their lint output for a suggested or potential task vs. a decided task?

[clach04]

Cross ref #44