[ivanovm]

Ok I got a first cut of Ruby parser in - the latest commit on Rails was a little sluggish but it works!

Right now the parser intentionally tags modules as classes, we made some assumptions in the generic parser code for other languages that don't quite align with ruby's notion of modules, but that'll be adjusted in the near future.

[ScotterC]

hey this is awesome. I'm using it and I think it's got some wheels. But please add a quick link to submit feedback in app! Here's what I got so far: - specific issue: I updated the triage text before submitting to the planning stage. Although the triage text maintained my edits I'm pretty sure the prompt that went into the first Plan generation did not include my edits. - rough idea: Plans are long and take awhile to regenerate. There's fear of submitting for a regeneration when all you want is it to understand something different about the high level thoughts. Maybe keeping a history of plans or even diffing them could be useful.

Both items above coalesce into a desire to 'rewind' back to the top of the process and try to get the context understood at the beginning, and have that clearly reflected to the user so that as you move through to details it gets easier to handle the nitty gritty without as much editing.

[robmck]

We will definitely add a feedback button, thanks for the suggestion!

We will look into why the Triage edits were not reflected in the plan. And I like your suggestions on being more specific on updates to the Plan.

I have a few suggestions in the meantime that could help to get you part of the way there as we work on these new additions:

- If you select a piece of the plan, you could ask that step to be regenerated based on new edits and then replace that piece either with the "Replace selection with summary" button or copying directly

- You can Ctrl-Z in the document editors to go back. It sounds like this might help a bit with rewinding as you describe

Let me know if that makes sense!

[ScotterC]

Great. I’ll give it a try today