agent-session-briefinglisted

Maintain project continuity across coding-agent sessions (Claude Code and any AGENTS.md-style harness) using a markdown session briefing that pairs with the project's agent context file (AGENTS.md, CLAUDE.md, GEMINI.md). Use when working in a local repo or project that spans multiple sessions, when the user asks to create or update a session briefing, status doc, or handoff note, when resuming prior work, or at the end of a session/context window to capture state for the next one. The briefing holds timestamped state — current status, decisions, next steps, open questions; the context file holds timeless operational reference. Briefings live in the session-briefings hub, one per project, with a pointer wired into each project's context file. For chat-based (claude.ai) projects that have no context file, use chat-session-briefing instead.
CaptCanadaMan/session-briefing · ★ 0 · AI & Automation · score 70

Install: claude install-skill CaptCanadaMan/session-briefing

# Agent Session Briefing A system for carrying project state across coding-agent sessions. The briefing is a markdown document — the source of truth for *where a project is, what's been decided, and what's next* — that a fresh session reads to resume cold without relitigating settled work. This is the **agent variant** of the briefing method — for coding agents that run in a repo with an **agent context file** (AGENTS.md, CLAUDE.md, GEMINI.md, …) and a git repo. It deliberately offloads half of the old chat-era briefing to those. (The chat variant — `chat-session-briefing` — keeps everything in one document because a chat project has no context file and no git.) > **Context file = the timeless operational doc your harness auto-loads.** `AGENTS.md` is the > cross-tool open standard (Codex, OpenCode, Aider, RooCode, OpenClaw, …); Claude Code uses > `CLAUDE.md`; Gemini CLI uses `GEMINI.md`. The skill works with whichever you have — the scripts > auto-detect an existing one and otherwise create `AGENTS.md`. ## Relationship to the context file — the boundary that keeps both lean One rule decides where every fact goes: - **Timeless → the agent context file** (AGENTS.md / CLAUDE.md / GEMINI.md — whatever your harness auto-loads). True regardless of when you read it: what the project is, repo layout, how to build/run/test, conventions, environment constraints, load-bearing gotchas. Living, overwritten in place, auto-loaded every session. - **Timestamped → the briefing.**