Briefs, meeting notes, project follow-up, reporting

This lesson is still being tested: it improves with learners' feedback. If something is unclear, it is the lesson that needs fixing, not you.

By the end of this lesson, you will be able to

recognize the documents that come back: brief, meeting notes, project follow-up, weekly report;
fix their format once and for all, in a skill;
produce a weekly report from your journal, without inventing anything;
check a report in two minutes.

Why it matters to you

Every week, the same documents come back: where the project stands, what was decided, what is blocked. Writing them by hand takes time; leaving them to the AI without a framework gives a different text each time, sometimes padded with guesses.

A skill with a fixed format, whose instruction is to read only your files, gives you the right document in one word.

It is an instruction, not a barrier: the connectors you connected in lesson 3 remain available in Claude Code.

Before you start


You need	Claude Code (app or terminal), in Manual mode, and your mon-espace-ia folder with a few journal pages and a project sheet
Cost	The agent subscription: Claude Pro at minimum, €18 per month excl. VAT, price shown in France on 24/10/2026
Duration	40 minutes
Reminder	The report only reads: green task (lesson 1)

Understand it in 3 minutes

Four documents that come back:

Document	Based on	For whom
Brief	Your project sheet	A person who is going to help you, or another AI (module 9)
Meeting notes	Your meeting notes	The participants (module 3, lesson 1)
Project follow-up	The project sheets	You, to see where each project stands
Weekly report	The journal pages of the last 7 days	You, or someone you report to

The right framework, in the skill:

What it reads: specific files (the journal of the last 7 days, the sheet of the current project).
The format: always the same parts, in the same order, with a maximum length.
The rules: use only these files, write [to be completed] when information is missing, change nothing.
The trail: end with the list of files read, so that you can check.

Facts and opinions. A report can add an opinion (“little margin”). It may help you, but it is not in your notes: spot it.

Do it together

1Step 1: Create the weekly report skill

In mon-espace-ia, in Manual mode:

Create a project skill named point-semaine, in .claude/skills/point-semaine/SKILL.md.
Description: "Prepares the weekly update from the journal pages of the last 7 days and the project sheets. To be used when I ask for the weekly update, review or report."
Instructions, read-only (do not change any file):
1. Read the pages in the journal folder from the last 7 days (the names are dates YYYY-MM-DD; ignore modele.md), then the sheet of the current project.
2. Write the update in 10 lines at most, with four parts: Done, Decided (with the reason), Pending or at risk, Next action.
3. Use only what is written in these files. If information is missing, write [to be completed].
4. End with the list of journal pages that you read.
Show me the file before you create it.

Read it, then allow it (the .claude folder asks for your approval).

2Step 2: Use it

In a new session, type:

/point-semaine

In our test, on a made-up journal, the update took the facts from the pages, marked “The reason is not written: [to be completed]” for a decision with no reason, and listed the pages read.

3Step 3: Check in two minutes

Is the list of pages read complete?
Can every fact in the report be found in a page?
Are the [to be completed] marks right?
Which sentences are opinions from the AI, and not facts?

4Step 4: The other documents (your choice)

On the same model, create a skill for the document that is most useful to you: a project follow-up (“For each sheet in projets/, one line: goal, current step, next action”) or a brief (“From the sheet of the current project, a one-page brief for a person who is going to help me”).

Your turn

Use /point-semaine at the end of each week, for two weeks.
Check each report with the four questions of step 3.
Adjust the skill if something keeps coming up (a useless part, a length that is too short).
Note on your task sheet (lesson 1): does the skill work well enough to be scheduled (lesson 5)?

Check your work

It worked if:

your point-semaine skill exists, read-only, with its format and its rules;
you got at least one report, and checked every fact in the journal;
you can tell, in a report, facts from opinions;
your task sheet says whether the automation can move on to the next step.

Common mistakes:

a different format every week, for lack of a skill;
letting the skill change files “to save time”;
no longer checking after three weeks because “it works”;
taking an opinion from the AI for a fact.

Keep it and pick it up later

Your document skills are in the .claude/skills/ folder of your workspace: they are part of your copies.
Keep the reports that were useful in your journal: they tell the story of your project week after week.

Going further

optional

A well-made brief also helps you hand work to another AI, or to a person: that is the subject of module 9, lesson 3.

New words

4 words explained

Word	What it means
Brief	A page that gives someone everything they need to help on a project
Reporting	The regular account of progress: every week, every month
Fixed format	The same parts, in the same order, every time
Opinion	A view from the AI, sometimes useful, but not written in your notes