session-end
Skill0 starsChanged 29 days agoApache-2.0View on GitHub
End an AOD architect session - write the journal entry (done, not done, decisions, open questions, next step), check it, and commit the project memory so the next session starts from a clean tree. Use when the user wraps up, before a long break, or when the context is getting long.
30 other projects use a version of this.
Adopted by
Most recently taken up by
- mikkiola/radartheir own version, first seen Nov 15, 2026
- spizganed/skillstheir own version, first seen Nov 8, 2026
- edxleon/runspectortheir own version, first seen Nov 8, 2026
- salvo8519/fairmarktheir own version, first seen Nov 8, 2026
- puritysb/AgentDecktheir own version, first seen Nov 2, 2026
- ravindu57/SCMLtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use ship.
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.
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- puritysb/AgentDeck★ 288same name
- faizkhairi/claude-code-blueprint★ 73same name
- Kanevry/session-orchestrator★ 53same name
- valpere/session-indexer★ 42same name
- namedtoaster/The-Last-Mile★ 39same name
- iamneilroberts/claude-skills★ 26same name
- IlyaGorsky/memory-toolkit★ 13same name
- edxleon/runspector★ 9same name
- mae616/ai-template★ 9same name
- freskhu/genesis★ 5same name
20 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.
In this repository17 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- adrSkill
- closeSkill
- cross-reviewSkill
- decisionSkill
- delegateSkill
- doctorSkill
- exploreSkill
- initSkill
- packetSkill
- preflightSkill
- retroSkill
- session-startSkill
- specSkill
- verifySkill
- waveSkill
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 23 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
- Distinctive: line 13
Not done: what was planned but not finished, and why.
- Very specific: line 19
If contracts are unlocked, aod lock.
“Common” is measured: kept by at least 6 in 10 of the 23 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
End an architect session
CLI: aod means node "${CLAUDE_PLUGIN_ROOT}/scripts/aod.mjs".
aod journal new --topic <short-slug>returns today's entry (creating it from the template if needed).- Fill every section, short and factual:
- Done: tasks merged (ids, rounds), ADRs/specs written, anything verified.
- Not done: what was planned but not finished, and why.
- Decisions: one line each with the ADR id; a decision made in chat that is not in an ADR yet gets one now
(
/aod:adr). - Open questions: pending decision requests to the user, unknowns.
- Next step: the single concrete action the next session should start with (task id, command, file).
aod journal checkmust pass.- If contracts are unlocked,
aod lock. Background jobs still running are noted in the journal. aod session endreports what is left (status: pending-commitis normal, not an error). When only.agents/memory files are pending and the user agrees,aod session end --commitcommits them (docs: session journal <date>). Code changes are committed separately, never folded into the journal commit.
Ledger rule: .agents/tasks/index.json and index.md may stay uncommitted on the base branch while you work.
They are committed by aod merge (with the task) or by aod session end --commit, whichever comes first, and
never on a task branch.
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.