an issue tracker doesn't feel like the right place for app specification

^ an issue tracker (linear or github issues) doesn't feel like the right place for app specification

An issue tracker feels like a reasonable place for quick bugs, but a better place for specification feels like documentation context graph.

In an ideal world, you'd work with an agent to modify your documentation context graph and then the agent would do a reconciliation between before and after and propose some migration-like ephemeral work to get you there. That work would make sense in an issue tracker, but putting it there should be the agent's job, not the human's. Humans should essentially be working at the "epic" level in a way that updates the documentation context graph.