Skip to content
New this month 24 fresh C++, C#, F#, JavaScript, TypeScript and Lua courses just landed. Browse new releases Use code WELCOME10 for 10% off your first order · 14-day refund
WisdomCharms — home
Cart 0 items in cart
Prompt Packs & Templates All levels

The Documentation and Release Notes Prompt Vault

Prompts that turn commits, diffs and tickets into documentation people will actually read.

Rated 4.5 out of 5 from 2 reviews 35 students

LM Created by Laura Mbeki

  • Last updated August 2026
  • English
  • 2h 30m of material
  • 19 lessons

What you will learn

7 concrete outcomes

Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.

  • Draft a README, architecture overview and getting-started guide from real source material
  • Generate changelogs grouped by user impact instead of commit order
  • Write release notes in a tone that matches the audience reading them
  • Produce migration guides that state breaking changes plainly
  • Audit existing documentation for statements the code no longer supports
  • Write runbooks that a tired on-call engineer can follow at three in the morning
  • Keep documentation prompts in the repository so the next release is faster

Course curriculum

5 modules · 19 lessons · 2h 30m of material

3 lessons running 22m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.

Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.

4 lessons running 32m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.

Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.

4 lessons running 34m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.

Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.

4 lessons running 32m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.

Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.

4 lessons running 30m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.

Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.

5 modules · 19 lessons

2h 30m total length

Requirements

Short list, and deliberately so. If you meet these you can start today.

  • Access to a repository you are allowed to describe publicly or internally
  • A chat model account such as Claude or ChatGPT

About this course

Documentation is the work everyone agrees is important and nobody schedules. A model will not make you care, but it will remove the blank page, and this vault is built to make that first draft close enough to keep.

Inside are prompt sets for the documents developers are actually asked for: a README that explains what the project is in the first two lines, an architecture overview written from a directory listing and a few key files, API reference entries generated from route definitions, a getting-started guide tested against a genuinely empty machine, runbooks for on-call, changelogs grouped by user impact rather than commit order, release notes in three different tones, migration guides that spell out breaking changes, and the deprecation notice nobody wants to write.

The vault also handles the reverse direction: prompts that read existing documentation and find what is now false, what contradicts the code, and what assumes knowledge the reader does not have. Those are the ones teams end up using every quarter.

Nineteen recorded lessons apply the vault to a real open-source style repository across a full release cycle. The pack ships as Markdown, Notion, plain text and a set of document templates, delivered by an access link emailed after checkout.

Topics covered

Frequently asked questions

Still unsure about something? Write to misteryjj100@gmail.com and a human answers, usually the same working day.

It will if you let it. Several prompts in the vault exist purely to force citations back to files and lines, and the audit set is built to catch inventions before publication.

Yes, and most buyers use it that way. The runbook and architecture sets assume an internal audience with more context and less patience.

Yes. Every prompt set comes with a matching Markdown template so the output lands in a consistent structure across a project.

Checkout is handled on our provider's secure payment page. The moment your payment clears we email your personal access link and access code to the address you used at checkout, and the same link appears in your account library. There is nothing to install and nothing to wait for.

Email misteryjj100@gmail.com within 14 days of your purchase, quote your order number, and we refund the full amount to your original payment method. No form to fill in and no questions about how much of the course you watched.

What students say

Reviews are written by people who bought this course. We publish the critical ones too.

4.5

Rated 4.5 out of 5

Course rating · 2 reviews

Rating distribution

  • 5 stars 50%
  • 4 stars 50%
  • 3 stars 0%
  • 2 stars 0%
  • 1 star 0%
  • HV

    Hendrik Vos

    Developer advocate

    Feb 2026
    Rated 5.0 out of 5

    Release notes by impact, not by commit

    Grouping changes by who is affected and what they have to do about it, rather than listing merged pull requests in order, is such an improvement that our support team commented on it unprompted. The prompts do most of the sorting for you.
  • SN

    Simone Neri

    Technical writer

    Oct 2025
    Rated 4.0 out of 5

    The audit prompts want a huge window

    The drifted-documentation audit expects a README and the code it describes pasted in together, which for anything real means splitting it up and losing exactly the cross-references you were checking. Lovely idea, awkward in practice. The changelog and runbook prompts are strong enough on their own to hold this at four.

Your instructor

LM

Laura Mbeki

Prompt engineer and AI workflow designer

  • 506 students taught
  • 16 courses published
  • 4.3 instructor rating
  • Prompt engineering
  • Prompt libraries
  • AI workflows
  • Prompt evaluation

Laura went independent after seven years of agency work and now designs the prompt libraries that sit behind other people's products. She treats prompting as engineering: versioned prompts, a held-out evaluation set, a regression run before anything ships, and a token budget you have to hit. Her packs are the ones she uses with her own clients — briefing, rewriting, summarising, review — rather than sanitised examples, and each comes with notes on where it fails. She keeps every pack working across ChatGPT, Claude and a small open model, so the technique outlives the model.

See every course by Laura Mbeki
$14 USD

One-time payment · lifetime access

The WisdomCharms dispatch

One useful email a week. No fluff, no spam.

New course releases, discount codes before anyone else, and a short, practical breakdown of one technique — a prompt pattern, a C++ idiom, a TypeScript trick — that you can use the same day.

  • Subscriber-only launch pricing
  • Unsubscribe in one click
  • We never sell your address

By subscribing you agree to our Privacy Policy. Questions? Write to misteryjj100@gmail.com.