I've just started a very ambitious /goal ux-focussed rewrite of my sport management app. I'm sharing this as an expression of my ideal mix of skill use, parallelization, and human intervention.
A simplified* list of I've done so far:
- 50 opus/codex agents catalog in detail 284 user flows (e.g. signing up for an event, creating an event) and critique it, orchestrated by
@RepoPrompt. I end up with
- A series of opus agents synthesize reccurring themes
- I use
@repomix_ai to send 200k of context to 5.5 Pro in ChatGPT web and ask what shape my app would be in the best possible end state
- I use
@mattpocockuk's grill-me-with-docs to ask me >100 product questions about the end state, and provide a lot of detailed feedback. I have it batch assumptions for me to approve en-mass, and I have it create a end-state-design markdown as it goes. By the end it's >3000 lines.
- I use Repo Prompt's Deep Plan to create a detailed audacious plan, assuming infinite dev time. It's ~300 lines.
- I send the plan to team of Opus's and have it make sure that if the plan implemented, none of the concerns from the flow critiques would still be valid. It finds a ton of issues.
- I have Codex edit the plan to address the concerns from the flow docs. After a couple of back and forths, and one more 5.5 Pro check, the plan is 1500 lines and looks solid to me.
- I create this very specific /goal
- I'm going to use Opus to occassionally check on Codex and see if it needs a nudge
Overall, I do think this is going to meaningfully improve the UX of my app. I've hosted some real events on it, and my first National Governing Body will be using it starting September, so now is the time for large improvements.
Hopefully this is helpful for someone, and I welcome if anyone has suggestions for me!
Check out my dev sandbox at: qcdev dot solsticeapp dot ca
* It took a while to even identify all the flows, and batch similar/less-important tones. I also did a lot of testing and inventorying before being confident the agents would do a good job of critiquing the user flows.