[gchamonlive]

Not really, because I do my sessions exclusively in the cli. I've commited sessions once in a repo and GitHub complained about secrets. When I inspected the sessions it were exporting my zsh env which has got lots of secrets in it. So I need to first collect all sessions related to one change, as I also spread a single change in multiple sessions, sanitize it and then share.

What I think I'll do is to formalize my workflow in the form of a meta project and do write-up about it. I think it's going to be more useful to a wider audience than share sessions tied to a specific niche project.

However, in a nutshell, I do a discovery session in which I explore the problem. The output of this discovery session is a work-item document with lots of tasks in it but roughly defined. I then open another refinement session, so I intentionally lose the discovery context. This session improves the work-item doc. Then I open another execution session in which I iterate over each task. Then I do a post session in which the agent is instructed to verify if the work-item is indeed concluded or if we left work out by mistake. The output of this last session is either another follow-up work item or a decision change documentation, either in the work item I'm closing or the next work item if it's already there, so I document decision changes that I needed to make during the execution phase.