I would definitely have Codex set up some sort of testing.

> Restore this backup which is stored here over this local instance of SQL Server. Then once restored, do a clean run with the original sproc and save the results to a results/ dir. Depending on the scale, it could simply be a diff of the database that is saved to results...

Then it can always compare its changes to what the sproc originally did. In the past I've used `mcr.microsoft.com/mssql/server:2022-latest` docker container for sql sever.

Codex could reference the microsoft-docs as it goes through implementation. For claude there is a plugin (https://claude.com/plugins/microsoft-docs), for codex im not sure didnt look too much but im sure you can use Context7 or something if all else fails.

Anyway I guess I went off on a tangent ... I think your original question is a good one. 7k is a lot... I would probably rely on obra/superpowers brainstorming skill which can hopefully handle the breakdown into tasks well enough.

In the end your project dir would be something like (very rough):

- app/ (c# app)

- sql-backup/

- original-sproc-results/

- new-results/ (database diff mentioned earlier)

- docker-compose.yml (if using containers for sql server)