Managers Strike Lets the Model Think While Tools Handle the Formatting

Yesterday a project management toolkit for ChatGPT and Claude showed up on r/PromptEngineering. It’s called Managers Strike, and the twist is the part worth stealing.

What’s new

The builder works with meeting notes, project plans and reports all day. They got tired of ChatGPT handing back generic tables, giant action lists and over-complicated documents for simple jobs. Anyone who has asked for “a short summary of this meeting” and received a twelve-column table with color-coded priorities knows the feeling. So the builder packaged the fix as reusable skills. There are two so far:

  • Doc Writer: builds business proposals with customizable structure and formatting, so you stop burning high-end model tokens on layout tweaks. Think of the usual loop: “make the headings smaller,” “move pricing to the end,” “shorten the intro.” Each of those is a paid round trip. With a reusable structure, you set the layout once and every new proposal inherits it.
  • Task Tracker: reads long meeting documents (20 to 30 pages), pulls out the decisions and action items, and organizes them into task boards, sprint plans and weekly reports. That’s the kind of document where the one decision that matters is buried on page 17, between a budget tangent and a scheduling argument.

The twist

The unexpected part is that the model isn’t asked to produce better text. The author’s lesson is that the model should do the reasoning, and reusable tools should do the structure, formatting and file operations.

Most of us keep re-prompting for a nicer table. This flips that. The model decides what matters in the meeting. A tool decides how it looks. Task Tracker also aims to update your existing Excel file directly, so you don’t get a fresh spreadsheet every time and then paste it over the old one. If you’ve ever lost a column of manual notes because you pasted the wrong version over the right one, you can see why that matters. The old file stays the source of truth, and only the changed rows get touched.

There’s a cost angle too. Reasoning is the expensive, valuable part of what a model does. Spending it on font sizes and column widths is like hiring a senior analyst to align text boxes. Split the jobs and you pay premium rates only for the thinking.

It’s early. The author says they’re still testing and still working on cutting token use without losing quality. Treat it as a promising build, not a finished product.

The mini-workflow to copy

  1. 📄 Hand the long meeting document to the model and ask for decisions and action items only. No formatting requests. Resist the urge to say “and make it pretty.” Pretty is the tool’s job.
  2. 🧠 Have the model output a clean structured list: task, owner, due date, source line. If an owner or date isn’t stated in the notes, tell the model to write “unassigned” or “no date” instead of guessing. A blank you can see beats a confident guess you can’t.
  3. 🛠️ Let a script or tool write that list into your existing spreadsheet instead of regenerating the whole file. Match on a stable key, like the task name plus owner, so a re-run updates a row instead of duplicating it.
  4. 📊 Run a second reusable template to turn the same data into a sprint plan or weekly report. Same data, different view. You never go back to the 30 pages.

Pro tips

  • Keep the structure in the tool, not in the prompt. Every layout instruction you put in a prompt is tokens you pay for again next time.
  • For 20 to 30 page documents, ask for a source reference with each task. It makes the output easy to spot-check, and a fast spot-check beats trusting a long extraction blindly. Ten minutes checking five random tasks against their source lines will tell you whether to trust the rest.
  • Update the file in place when you can. Regenerating a whole spreadsheet to change three rows is where most of the waste hides.
  • Start small. Run the workflow on one past meeting where you already know the right answers, and compare. If it misses a decision you remember, tighten the extraction prompt before you point it at live work.

Call to action

If you live in meeting docs and status reports, go poke at the GitHub repo (github.com/sakib4535/managers-strike) and see how the skills are split. The author is asking how others handle large meeting documents, structured task extraction and direct spreadsheet updates with LLMs, so drop your setup in the thread. 🚀

I built Managers Strike — project management skills for ChatGPT and Claude
by u/Exact-Substance2084 in PromptEngineering

Scroll to Top