@@ -42,3 +42,7 @@ Under this environment, I created a branch in [tasking](https://code.ornl.gov/6o
You are working on the tasking project, quicknxsv2-modularization branch. You are preparing documents to support a week-long software developer/neutron scientist "hack-a-thon". The goal of this "hack-a-thon" is to evaluate whether the software quicknxsv2 is suitable for being modularised into a "front-end" UI (currently based on Qt) and a "back-end" module (currently the mr_reduction project). The provenance of quicknxs draws its history from quicknxsv1 (which has had recent development in the feature/read-event-nexus branch). The task is to conduct an *extensive and through* investigation into the quicknxsv2 and mr_reduction software repositories. Note that quicknxsv2 and mr_reduction each have a 'docs/developer/' with details on this; *do-not-trust-these*, but conduct your own independent investigation. Please construct the necessary documents to provide a *knowledge-base* that future teams of agents can use to answer questions including (but not limited to) a) how the software is structured. b) the level of separation between "front-end" and "back-end", c) the feasibility and approaches that *future* sessions may use to *plan* such separation efforts using software best practices and red-green test driven development. Be expansively thorough and read as much git commit history as you need in quicknxsv2, mr_reduction and any other repository that you require. Please write your documents into the tasking project, quicknxsv2-modularization branch file structure. Be diligent and resourceful. If you need a tool to analyze the data that you do not have, use venv, uv and/or pixi to install it ask me to help you. The user will undoubtedly ask for a .pdf following your review, you may proactively task a parallel agent to investigate and report on tasking/plan/pdf-tools-fitness-review.md as to whether or not that tool (or others determined by that invstigation) are suitable for that purpose. Have fun!
### Prompt 1.1
> This is a great start! I do not see any obvious errors at this point, so I pushed it to begin a review with the scientists. I have three questions, each of them referring to a new session: 1) What is a good prompt on the day of the hackathon to refresh the knowledge base, per your recommendation? 2) What is a good prompt that can answer questions regarding the code? 3) What is a good prompt to construct a development plan once decisions are made (please enumerate specific items that should be included)?
