2 systems in this stack
Check the plan before you fund it. Learn what happened after you ship it.
Two operator skills for the two moments teams get wrong: committing to a plan that was never a strategy, and closing a project without learning anything from it. Each works on its own. Together they close a loop, because the post-mortem's findings are exactly what the next audit needs to read.
- Instant access
- Lifetime updates
- Secure purchase
In this stack
Every system you get
OPERATOR SKILL
Strategy Audit Skill
Audit any plan, deck, or brief against the kernel of good strategy, get a verdict with your own words quoted as the evidence, and get the rewritten diagnosis, policy, and actions.
View System
OPERATOR SKILL
Project Post-Mortem Skill
Turn a project's scattered AI conversations, files, and memory into one structured post-mortem with decisions, risks, open items, and what to automate next.
View System
The loop
Most work goes wrong at one of two moments
The first is the moment a plan gets funded. Someone writes a document full of goals and calls it a strategy, nobody can say what problem it solves, and the work starts anyway.
The second is the moment a project ends. The team moves on, the context lives in scattered conversations and files, and the next plan gets written by people who cannot remember what actually happened.
These are the same failure at opposite ends of one cycle. Each skill here handles one end.
Before
The Strategy Audit reads the plan you are about to fund
It extracts the three parts of a real strategy from whatever you give it: the diagnosis, the guiding policy, and the coherent actions.
Then it tells you which ones are missing, quoting your own words back as the evidence, and writes the replacement sentences.
It runs on a plan, a deck, or a brief. You do not have to reformat anything first.
After
The Post-Mortem reads the project you just finished
It works across a project's conversations, files, and memory rather than asking you to reconstruct events from recall.
What comes back is one structured report: the decisions that were made, the risks that showed up, the items still open, and what is worth automating next time.
It is the handover document people mean to write and almost never do.
Why both
The output of one is the input of the other
A good strategy starts with a diagnosis, and the hardest part of writing an honest diagnosis is saying what actually happened last time.
That is the exact artifact the post-mortem produces. Feed it into the audit and the next plan starts from evidence instead of optimism.
Run the loop twice and the second plan is measurably harder to fool yourself with. That is the whole argument for owning both.
FAQ
Questions before you buy
What exactly do I get?
Both skills, as downloadable files, with everything each one ships with.
- The Strategy Audit skill, plus its kernel and hallmarks reference, diagnostic lenses, repair playbook, evidence bank, report template, and a worked example
- The Project Post-Mortem skill, plus its analysis framework, discovery methods reference, and an example report excerpt
There is no separate bundle-only file. This is both products, not a third thing.
Do these actually work together, or is it just two things?
They work together, and the join is specific rather than thematic.
The post-mortem produces a structured account of what happened on a project. The audit needs a diagnosis, which is a clear statement of the problem you are actually facing. That account is the raw material for that diagnosis.
They also work completely independently. Neither one needs the other to be useful.
Which one should I use first?
Use whichever matches where you are standing right now.
If you have a plan in front of you that has not been committed to yet, start with the Strategy Audit. If you have just finished something, start with the Post-Mortem.
The loop does not have a required entry point. It only starts compounding once you have been round it once.
I already own one of these. Is the bundle still worth it?
Only if you want the other one.
This bundle contains the two products and nothing additional, so there is no extra material you would be missing by buying the second skill on its own.
Buying it does not duplicate access to something you already own.
What do I need to run these?
Any AI tool you can give files to. ChatGPT, Claude, and Gemini are all examples; nothing here is built for one of them.
You download the files and use them wherever you already do your thinking. There is no account to create, no extension to install, and no integration to configure.
Is the Strategy Audit connected to Richard Rumelt or his publisher?
No. It is an independent application of the Good Strategy/Bad Strategy framework, with no affiliation, endorsement, or licence.
It is not the book and does not replace it. It is a procedure for applying the framework to your own documents.
Ready in minutes
From download to working in minutes.
No app to learn, no software to install, no setup project. Each system arrives as ready-to-use files that work in any AI tool, so getting started takes minutes.
Download the files
Your download link is ready as soon as checkout completes. No account to create and no password to set.
Add them to the AI tool you already use
ChatGPT, Claude, Gemini, or any other AI tool. Upload a skill, attach a playbook, or open a template, the same way you add any document.
Put it to work
Start on the real job right away. The structure and standards are already built in, so there is nothing to configure first.
Complete stack
The Operator Loop
Two operator skills that close one loop: audit a plan against the kernel of good strategy before you commit, and turn a finished project into a structured post-mortem that feeds the next plan.
- Instant access
- Lifetime updates
- Secure purchase