Every distinct, accessible product suggestion Pierre Renard shared in the Pierre x GTOWizard group DM, consolidated and checked against what is implemented, in flight, backlogged, or still untracked.
Use the filters or search by feature, status, date, or issue ID.
Rework “best / strong / medium / trash” thresholds because Hold’em-style percentile or equity bands do not distribute PLO hands usefully.
Avoid filling the hand list with 1% actions/hands; either clean them up or hide negligible weights.
Support > / <-style range filtering—for example, top pair or better, or boards below ace-high.
Resolve cases where category combinations returned unexpected hands or filters appeared broken.
Let a Trainer filter mean “K-high or lower / no ace,” rather than forcing every generated flop to contain a king.
Stop counting overpairs as two pair; add distinct pocket-pair and three-pair classes, including pair-blocker subcategories.
pair/overpair, but the broader PLO4 taxonomy adjustment is Backlog. No verified three-pair or requested blocker split was found.Add PLO-native detail: wraps/OESD/NGS, one- and two-card straight blockers, nut/second-nut kickers, redraws, pair blockers, strong/weak full houses, trips kickers, flush and straight sidecards.
Extend the key-card/blocker view from one-card impact to two-card combinations.
In Trainer, generate turn/river cards that complete straights without necessarily also selecting flush-completing cards.
Go beyond a hand list: show hands played, accuracy/correctness, EV-loss KPIs, filters, and session-level performance.
Use the empty Trainer sidebar for exact-hand strategy, overall range frequencies, session stats, and recent hands.
Upload played hands, review them against the PLO strategy, and jump into the matching Study spot.
Let users clear the sidebar counters on demand so a drill’s hand count and EV-loss stats have a clear starting point.
Allow the exact hand action to stay hidden before a decision while still showing category and range frequencies as learning context.
Change the sizing/tree strategy from inside Trainer instead of opening Study, editing there, and restarting practice in another tab.
Replace manual spreadsheet/Heptabase aggregate analysis with native reports across boards and strategy transitions.
Let users choose non-standard PLO bet sizes and solve the resulting spot quickly rather than relying only on the presolved library.
Add custom preflop setup options instead of limiting custom solve creation to postflop spots.
Configure the full game tree on every street instead of making ad-hoc edits only while browsing Study.
Keep previously created trees available instead of rebuilding them from scratch.
Save prior flop/turn/river sizing configurations and reuse them across spots.
If PLO dynamic sizing uses defaults, offer at least two libraries: 20/33/50/70/100 and 15/25/40/62/100.
Use Matrix as part of the hand/range learning view inside Trainer, not only as a Study surface.
Clicking AQ should include AKQx and other hands containing AQ, not only hands whose two highest cards are exactly AQ. Default to the full range, then narrow down.
Let Matrix stand on its own: filter categories inside it and show previous-street range weights rather than forcing users back to the hand list.
Add an EV/Pot or “pot share” read alongside the action-frequency percentage in Matrix.
Expand PLO500 rake solutions beyond the common mid-stack depths, covering both short stacks and deep play.
At 20–40bb, include limps where justified and consider smaller RFI sizes around 17–27bb rather than blindly pot-opening every depth.
Cover a standard UTG straddle in addition to the WPT SB-ante straddle structure.
Pierre suggested CoinPoker ante sims, then withdrew the ask after Frank pointed out they had already been added.
Model open-limping from every position in the rake-free CGWC-style CoinPoker cEV ranges.
Create solutions for GG’s different Rush & Cash cash-drop structures.
Prefer lower-priced plans per PLO format for specialists, while still offering a bundle for multi-format players.
When defining PLO6 preflop categories, include triple-suited structure and treat ace/king presence as potentially central.
Important product signals Pierre raised, but not feature requests.
What “all” means in this audit.