
WorkBuddy jumbles entries when organizing a planning doc's settings table—did I miss a setting?
Three AM, I'm staring at a settings document with over a hundred entries, feeling like I'm doing a repetitive material-farming daily quest. No loot drops, and it strains the eyes.
A couple days ago I came across an in-depth analysis of AI's impact on the game market. One judgment in it I agreed with: what AI is best at is work with a correct answer; what it's worst at is creation requiring taste and worldview-building. I figured, perfect — categorization and filing always has a standard answer, right? So I thought I'd have WorkBuddy do it.
I'd been using it to batch-edit spreadsheets smoothly, so I assumed this would be similar. Made a folder, dumped all three versions of the design doc in, and told it to organize into one table with three columns: systems, characters, levels.
The first table looked pretty legit — I even felt good about it for a moment. But looking closely, entry 12 and 13 got merged into one, and a few character settings ended up in the levels column.
So I changed strategy — feed it one document at a time. Better, but still misses things. One doc had about seven or eight side-quest descriptions; it only grabbed four, the rest it seemed not to see. I also tried writing more detailed instructions, putting all three column names in quotes — results weren't great.
What I'm not sure about now is whether the problem is giving it too many documents at once, or my wording not being rigid enough. I've seen people on the forum mention "output contract" — I only vaguely understand it. Does it mean I have to write out exactly what each column looks like, what to fill in when empty, all fixed in advance? From my testing, just saying "organize into three columns" seems to let it improvise.
Anyone hit this pit before, or did I set something wrong?
Physix Frontier