Re: [Orgmode] properties in agenda prefix

[Skip Collins]

> What property would you find useful to have and why?

CUSTOM_ID could be handy right away. If arbitrary properties were
accessible in agenda prefix, it would enable very flexible agenda
constructs. Consider a setup in which headlines are given a tracking
number that can be used as a reference number outside of org. The
reference number would naturally be a property, not a tag. To get a
nice list that includes the reference number, it must be assigned to
CATEGORY.

Consider also a group agenda in which items are flagged in the prefix
with the names of their owners. Again, the names must now be assigned
to CATEGORY.

As a design goal, I think would it make sense for agenda and column
modes to have some overlapping features and syntax, including the
ability to access properties.