brief
Skill0 starsChanged 34 days agoMITView on GitHub
Write the periodic brief, covering what to do this week, what is coming in the next two to three weeks, and things captured and forgotten. Use when the user says "brief", "weekly review", "what changed", or on the schedule.
80 other projects use a version of this.
Adopted by
Most recently taken up by
- MiguelARojas3103/rtovar-aiostheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- sufficiently-advanced-ai/imitheir own version, first seen Nov 12, 2026
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- fjwood69/moritheir own version, first seen Nov 10, 2026
- serhiileniv/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use strategy, decision and 6 more.
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.
EpistatesSkillstrategy
Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.
Also in 4 projects that use this
aleksander-dytkoSkilldecision
Make a product decision with full context from the vault and available sources
Also in 3 projects that use this
dirienSkilldecide
Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.
Also in 5 projects that use this
howellsSkillreconcile
Audit a project against current plugin conventions and offer to update structure.
Also in 3 projects that use this
codihausSkilldebrief
Analyze customer requirements and deliver market research, tiered proposals, and recommendations
Also in 3 projects that use this
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 3 projects that use this
Other versions80 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 80
- anthropics/knowledge-work-plugins★ 36ksame name
- suboss87/FDEOps★ 940same name
- with-pebbly/aseprite-ai-artist★ 697same name
- educlopez/ui-craft★ 441same name
- github/lever★ 279same name
- dylanroscover/Embody★ 219same name
- yofine/skills★ 154same name
- grainulation/grainulator★ 86same name
- g2i-ai/agents★ 52same name
- gregmos/memoforge★ 38same name
70 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
9
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
- Very specific: line 15
Check mem/rules.md for a ## Brief section first.
- Distinctive: line 21
No metaphor, simile or figure of speech you are used to seeing in print.
- Distinctive: line 22
No long word where a short one will do.
- Distinctive: line 37
No closing remark. No commentary on the system's own reasoning, counters, or file paths.
- Distinctive: line 40
Write long lines: Do not hard-wrap sentences mid-clause.
- Distinctive: line 82
Do not write a sentence whose subject is the report: no "this brief covers", "here is what is coming up", "as of today".
- Distinctive: line 86
If nothing is due, say so in one sentence and omit the empty sections.
- Distinctive: line 146
Use the real name of the thing, in title case.
- Distinctive: line 308
Em dashes inside a detail line: Use a comma, a colon or a full stop.
- Distinctive: line 355
Never write a calendar entry: Do not mention that one is missing either.
“Common” is measured: kept by at least 6 in 10 of the 73 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.
Files
brief
The brief tells the user what to do this week and resurfaces what they would otherwise lose.
It does not explain their work back to them. They know how to update a CV, prepare for an interview, or plan a launch. Telling them how is noise, and it is the fastest way to make the brief unreadable.
Check mem/rules.md for a ## Brief section first. Anything there overrides this file.
How to write
Neutral and factual, like a reference entry. State the fact and stop. Follow Orwell's rules:
- No metaphor, simile or figure of speech you are used to seeing in print.
- No long word where a short one will do.
- Cut every word that can be cut.
- Active, not passive.
- Everyday English, not jargon.
- Break any of these before writing something barbarous.
| Do not write | Write |
| "This has been sitting unresolved for some time" | "Open since 12 August." |
| "It might be worth considering whether to..." | "Decide whether to..." |
| "The deadline is fast approaching" | "Due Sunday." |
| "The vault has no record of X" | (nothing, say only what is there) |
| "No calendar event exists" | (nothing, it is not an action) |
| "a number of items" | "four items" |
No closing remark. No commentary on the system's own reasoning, counters, or file paths. The first line of a section is the first fact.
Write long lines. Do not hard-wrap sentences mid-clause; the email renders them as written.
Title
# Morning Brief — Monday, 31 August 2026Morning Brief on a weekday, Weekend Brief on Saturday or Sunday. Full day name, full
month, four-digit year. Nothing else on the line.
Opening
Two sentences. Never three.
Lead with what finishes this week, not with what is late. A paragraph that opens on four overdue items reads as a charge sheet, and the reader has not reached the list yet.
The first sentence names the work that completes, and what completing it opens up. The second names what is still outstanding, briefly, and stops.
The CV and the personal website both finish this weekend, which clears the run at the
scholarship submission on Friday 18 September. RAG and the masters check are still open from
last week.What that replaced was four sentences, eleven dates and no order of importance:
RAG passed its date yesterday, Friday 11 September, and the two days to Sunday 13 September
already hold the CV, the personal website, the brief redesign and agents and subagents.
Every part of the scholarship preparation is due Thursday 17 September and submission opens
Friday 18 September. The masters check is three days past its third date, and route B has no dates
of its own until it is done.Energy comes from brevity and from leading with what is in reach. It never comes from adjectives. No "you've got this", no "a strong week ahead", no exclamation marks, and nothing rating the work as big, important or exciting.
Do not write a sentence whose subject is the report: no "this brief covers", "here is what is coming up", "as of today". Do not do arithmetic for the reader: "six working days, three of them away" is a calculation nobody asked for.
If nothing is due, say so in one sentence and omit the empty sections.
Staleness, and what is being held
Anything still in raw/inbox/ when the brief is written was held on purpose, not
forgotten. The daily pass compiles every source whose plan touches only wiki/, and holds
anything that would write a dated loop, change a date already recorded, touch mem/,
contradict an existing claim, or that reads more than one way. What remains is what needs a
person.
So report it as a decision waiting, not as a backlog:
*2 sources held: the 8 September transaction touches mem/, and "edbert briefing" reads two
ways. Run /ingest-all to settle them.*Say what each one is and why it waited, up to three. Above three, give the count and the two most consequential. A held source with a date in it goes first, because that is the one where waiting costs something.
Separately, check when the daily pass last ran: the last ingest: ok line in autopilot.log,
in the repository root beside vault/. Not log.md. A pass that finds an empty inbox
compiles nothing and writes nothing there, so a quiet week reads exactly like a broken one. If
the last clean run is seven or more days old, the pass has stopped, which is a different
fault:
*The daily pass last ran 9 days ago. It may have stopped: check autopilot.log.*The scheduled run reads autopilot.log for you and states the result in the prompt. Use what
it states, including when it says the pass is running, and do not work it out again.
Both lines go directly under the opening paragraph, before the first section. A warning about whether the contents can be trusted is useless after the contents have been read.
Neither condition met means no line at all. Do not write a reassurance that the vault is up to date; silence is the signal.
Structure
Three sections. One or two are usually empty, and an empty section is omitted
entirely, and Don't forget is often empty.
Three heading levels, and they are not interchangeable:
## Now the section
### Monday 14 September the date group
#### Thrive Application the entry
A CV and a written introduction. The posting names no closing date.Entries are ####, date groups are ###, sections are ##. Headings rather than bold
text, because the email stylesheet uses the level to space them: without it, title, detail
and the next title sit the same distance apart and the section reads as one block.
Titles
Use the real name of the thing, in title case. Standard abbreviations are fine.
| Wrong | Right |
| RAG | RAG Project |
| Foundation go-to-market planning | Foundation GTM Planning |
| Masters | Masters Applications |
| Trip | Jakarta Trip |
| Haircut | Haircut Booking |
| CV and portfolio | CV and Portfolio |
A single generic word is not a title. If the entry is called Sheet or Website or
Interview, name which one. Where the vault does not know which one, do not paper over it
with a vague description. Quote the user's own words verbatim so at least he recognises
what he meant, and offer to drop it.
Link anything that has a URL. An article, a page, a tool, a repository: the title is the link.
#### [How Complex Systems Fail](https://how.complexsystems.fail/) — 20 minutesA reminder to read something that does not include the thing to read is a reminder to go looking for it.
Timing after the title
No dates after a title. Ever. The date group above the entry carries the date, and
repeating it is noise. That includes ranges: #### Scholarship Prep — Monday 14 to
Sunday 27 says nothing the heading above it has not already said.
| Wrong | Right |
#### Scholarship Prep — Monday 14 to Sunday 27 | #### Scholarship Prep |
#### Scholarship Submission — Saturday 19 to Sunday 20 | #### Scholarship Submission |
#### CV Update — Sunday 13 September | #### CV Update |
Where a range genuinely matters, the detail line is the place for it, and only when the span changes what the reader would do:
#### Scholarship Submission
An essay and two references. The window closes Sunday.Two exceptions, and nothing else:
| Allowed | Because |
#### How Complex Systems Fail — 20 minutes | a duration, not a date |
#### Masters Check — due 9 September, 5 days ago | overdue, where the lateness is the point |
Dates in the detail line are absolute. A relative word means something different on Thursday from what it meant on Monday, and the brief is read across the week.
| Wrong | Right |
| today | Monday 31 August |
| due tomorrow | due Tuesday 1 September |
| this weekend | Saturday 5 September |
Day name and date together. The year only when the item falls in a different one.
Numbers
Digits and standard symbols: 75%, 20 minutes, £40, 3 September. Never 75 per cent.
Spell out only where a digit starts a sentence.
Grouping inside a section
Now and Soon are grouped by date, not listed flat. A date that carries work becomes a
subheading; everything without a fixed day sits in one group at the end.
## Now
### Monday 14 September
#### Thrive Application
A CV and a written introduction. The posting names no closing date.
#### Masters Check
Find the closing date and which documents are needed.
### Across the week
#### CV and Portfolio
Stage one of the scholarship preparation.
#### Personal Website
The last of the three portfolio projects.Date subheadings carry the day and the date, earliest first. The trailing group is titled
Across the week in Now and No fixed date in Soon. Omit it when everything has a
day.
A date subheading with one item under it is still a date subheading. Do not fold it into the trailing group to save a line.
The three sections
# Morning Brief — Monday, 14 September 2026
<Opening. Two sentences.>
<Then the held line, only if something is held.>
## Now
<This week, grouped by date. Anything due or worked on between today and Sunday.>
## Soon
<The next two to three weeks, grouped the same way.>
## Don't forget
<Only things to read and things to buy. See below.>Don't forget
Two kinds of thing, and nothing else:
- Something to read. An article, a paper, a page saved and never opened.
- Something to buy. An item the user said they wanted.
That is the whole scope. It is the gentle end of the brief, and it exists so a saved article does not vanish.
It is not a place for work. A decision, an evaluation, something to write, a list to
confirm: those are tasks. They belong in Now or Soon under a date, or nowhere.
| Belongs | Does not belong |
| An unread article, with its reading time | "Antigravity", because evaluating a tool is a task |
| A monitor the user said they wanted | "The Five Books List", because confirming a list is a task |
| A saved paper, unopened | "Coding and Writing Rules Prompt", because that is work |
#### [How Complex Systems Fail](https://how.complexsystems.fail/)
Richard Cook, 18 principles. About 20 minutes.What never appears
Removed because they carried no information:
- Still open, a list of everything outstanding, most of it not actionable today.
- Worth knowing, vault housekeeping.
- Compiled this week, page and source counts.
- Anything of the form "the vault has no record", "no calendar event exists", "nothing has been added since". Absence is not an action.
- Instructions for work the user already knows how to do.
- File paths. Anywhere. The user opens the vault to find things, not the brief.
- "no note on why", "nothing recorded", "untouched since" as a description of what the user did or did not do when saving something.
- Which loop or source an item came from.
- Counts of pages, sources or compiled items.
- A closing sentence arguing why the item matters. "A verdict closes it." "The reading goal cannot be tracked without it." "Thrive is waiting behind it." The reader knows why their own work matters, and saying it back is the brief padding itself. State what the thing is and when it is due, then stop.
- Em dashes inside a detail line. Use a comma, a colon or a full stop. The dash after a title is a separator, not punctuation, and is the only one in the brief.
- Counters,
surfacedvalues, or any description of how the brief was assembled.
Overdue
An item more than 14 days past its date goes at the top of Now, under an ### Overdue
group that sits above the date groups, with three options and nothing else:
## Now
### Overdue
#### Foundation GTM Planning — due Monday 31 August, 23 days ago
Drop it, set a new date, or do it now.
### Monday 14 September
#### Thrive Application
...Overdue takes the place of a date group, so the entry stays a #### like every other one.
The daily due check stops reminding at 14 days so this can take over. Do not soften it and do not carry it silently. An item nobody has acted on for three weeks is dead or mis-dated; both are answers, leaving it open is not.
Length
The whole brief fits on a phone screen. If it does not, Now is holding things that belong
in Soon, or Soon is holding things that belong nowhere.
Then
- Increment
surfaced:on every loop that appeared, except ones acted on since the last brief. - Write to
briefs/YYYY-MM-DD.md. - Append to
log.md:## [YYYY-MM-DD] brief | <date>.
Rules
Nowmeans this week. The brief is weekly, so a section covering one day would be empty most weeks and would leave the rest of the week unreported.- Rank against stated goals, then by deadline.
- Never invent an item to fill a section. Omit the section.
- Never write a calendar entry. Do not mention that one is missing either.
- Report what is held, and why. See above. Held sources are decisions waiting on you, and a brief that silently reports a vault missing them is worse than no brief, because it is believed.
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
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.

