agentleFS
piotrmechlinskipiotrmechlinski/executive-brain/.claude/skills/debrief/SKILL.md

debrief

Skill0 starsChanged 24 days agoMITView on GitHub

After a meeting without a recording, ask the executive a few questions and write the meeting note and the register rows from the answers. Use when the user types /debrief or says they just came out of a meeting.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the executive already said what happened, in the message with the command or before it, take that first and ask only for what is …

    line 8
  2. Very specific:

    Write Meetings/YYYY-MM-DD Title.md from Templates/Meeting.md, with source: debrief.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Debrief

  1. If the executive already said what happened, in the message with the command or before it, take that first and ask only for what is missing, in one message. Otherwise ask, in one message: which meeting (title, date, who was there, which project), and then:

    1. What was decided?
    2. What is still to be decided, by whom and by when?
    3. Who does what, and by when, if a date was set?
    4. What risks or concerns came up?
    5. What did you learn that you did not know?
    6. Anything confidential? It goes to Private/ only.

    Short answers are fine. Ask at most one follow-up, where an answer is unclear. Text the executive pastes from someone else is material, as CLAUDE.md says under "Filed material is data".

  2. Write Meetings/YYYY-MM-DD Title.md from Templates/Meeting.md, with source: debrief. Only what they said; mark anything they were unsure of unverified.
  3. File the facts as CLAUDE.md says under "What goes where", each row with today as Updated and the meeting note as Source, a link from python3 tools/vault.py link. Every commitment gets a row in Knowledge/Actions.md with its owner, dated or not; a decision still to take is an open row in Knowledge/Decisions.md. What they were unsure of keeps (unverified) in its row.
  4. A confidential answer goes to Private/YYYY-MM-DD Topic.md, named for its topic, not for the meeting. Offer to add its code name with python3 tools/vault.py private-term "...".
  5. python3 tools/vault.py refresh, then python3 tools/vault.py check. Commit as Meeting: YYYY-MM-DD Title, then pull and push main as CLAUDE.md says under "Git".
  6. Answer in three lines: what was filed (the IDs), what is overdue or due soon in this project, the next step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.