Promptwith a check section
Finding the risks nobody has named yet
When the risk register holds only the obvious entries and you want to know what is missing.
Back
Resources
Tools for everyday project work
Prompts for recurring tasks, instructions for building your own agents and working templates as PDFs. All free.
In the order a project runs
What are you working on right now?
- 01Setting up a project and making decisionsBefore you start: pin down the mandate and the approach, find the risks and people you have missed, and test the business case.3 prompts · 2 templates
- 02Preparing and running workshopsBefore and during a workshop: set the guardrails and the agenda, sort what the room produced, and keep a record of what was decided.2 prompts · 1 agent · 2 templates
- 03Reporting and escalatingWhile the project runs: a status report the steering committee actually reads, and an escalation that gets a decision.2 prompts · 1 agent
- 04Handing over to operationsAround go-live: check whether operations can take over, keep a log through hypercare, and agree how you will know it is over.2 prompts · 1 agent · 1 templateNew
- 05Learning from what happenedAfter a sprint, a workshop or at project close: retrospectives and lessons learned that end in actions with an owner and a date.3 prompts
How to get the tools
Templates
Open or save the PDF. No account, no email address.
Prompts and agents: with a free account
There is no plan to choose and no payment details to enter. The account is where the collection lives: it grows over time, and your results from the calculators are kept, so you can compare them three months from now.
Already working in Claude? Flow efficiency and business case are also available as a plugin in the Claude Directory: two skills that calculate with your numbers and show the formula. The plugin is free; you need access to Claude. View the plugin in Claude →
01Setting up a project and making decisions
Back to overviewBefore you start: pin down the mandate and the approach, find the risks and people you have missed, and test the business case.
Promptwith a check section
Stakeholder matrix, cross-examined
When the matrix is done and you want to know who you have misjudged.
Promptwith a check section
Testing a business case against itself
Before the numbers reach a committee — and someone else finds the gap.
TemplatePDF · 1 page
3-Level Alignment Canvas
The kick-off template: mandate, outcome and way of working on a single page — settled before the first task is handed out.
Open PDF →no account
TemplatePDF · 1 page
Cynefin quick reference
What kind of problem is this, and which approach fits it? The four domains, each with the mistake people typically make in it.
Open PDF →no account
02Preparing and running workshops
Back to overviewBefore and during a workshop: set the guardrails and the agenda, sort what the room produced, and keep a record of what was decided.
Promptwith a check section
From mess to structure: clustering a collection and deriving consent questions
The pile of cards from a brainstorm becomes named clusters, one decision question per cluster in objection form, and a list of what nobody has said yet.
Promptwith a check section
Turning a vague brief into an agenda
"Just run a workshop" becomes a goal in one sentence, the questions to settle with the sponsor beforehand, and a run of timed blocks for the duration you actually have.
Agent5 steps · set up once
Workshop memory: setting up an agent that keeps the record
Photos of the walls and transcripts after every block become four running lists: decisions with objection and resolution, parking lot, open questions, and actions with a name and a date — plus a block-end summary somebody can check. This is the one for keeping the record as the session runs; if you would rather work through everything afterwards in a single pass, take the prompt "From the wall to a list of actions".
TemplatePDF · 1 page
Consent record (decision, objection, change)
A discussion going in circles becomes one line: proposal, objection, what would have to change, decision, date. One sheet per proposal, with a field for who did not speak.
Open PDF →no account
TemplatePDF · 1 page
Setting the guardrails before the workshop starts
A brief of “just run a workshop” becomes one page: what is off limits, who decides what (delegation level per topic), what the session is for, what it explicitly is not, and who is missing from the room.
Open PDF →no account
03Reporting and escalating
Back to overviewWhile the project runs: a status report the steering committee actually reads, and an escalation that gets a decision.
Promptwith a check section
Status report for the steering committee
When dates, risks and open items need to become a report a committee reads in five minutes.
Promptwith a check section
Preparing an escalation
When a decision has to go up a level and the question is how to ask without looking out of your depth.
Agent5 steps · set up once
Setting up an agent for the weekly status report
When the status report has the same shape every week and still starts from scratch every time.
04Handing over to operations
Back to overviewAround go-live: check whether operations can take over, keep a log through hypercare, and agree how you will know it is over.
PromptNewwith a check section
Checking operational readiness: what the project documents leave unanswered
When go-live is getting close and nobody can say for sure whether operations can take over the result — before operational acceptance shows that it cannot.
PromptNewwith a check section
Exit criteria for the hypercare period
When hypercare is in the project plan and nobody has yet said how you will know it is over.
AgentNew5 steps · set up once
Hypercare log: setting up an agent to keep a record of the hypercare period
For the hypercare period between go-live and project closure: turns incident tickets, minutes and notes into four running lists — incidents and who resolved them, questions that went back to the project team, known errors with their workarounds, and the status of the exit criteria. Plus a weekly overview that operations can check against the ticket system.
TemplateNewPDF · 1 page
Operational readiness on one page
Before operational acceptance or at the end of the hypercare period: the four signs as a checklist — incident route, change route, operational metrics, knowledge — with exit criteria, the fallback plan and the decision on whether the project can close.
Open PDF →no account
05Learning from what happened
Back to overviewAfter a sprint, a workshop or at project close: retrospectives and lessons learned that end in actions with an owner and a date.
Promptwith a check section
A retrospective that doesn't stop at collecting notes
When recent retros produced a lot of notes and little change.
Promptwith a check section
Lessons learned somebody else can use
At project close — when the report would otherwise vanish into a folder.
Promptwith a check section
From the wall to a list of actions
Photos and transcripts taken after the session become actions with an owner and a date, kept apart from what was merely parked, plus a third list for everything that is neither. This is the one for working through it afterwards in a single pass — if you want the record kept as the session runs, take the guide "Workshop memory".
