CaptCanadaMan
UserCarry project state across AI coding-agent and chat sessions: a timestamped briefing paired with your AGENTS.md/CLAUDE.md, plus cross-project constellation rollups.
Categories
Indexed Skills (3)
setup-session-briefing
One-time guided setup for agent-session-briefing — creates the briefings hub, scaffolds your first briefing, and wires the continuity pointer into this repo's context file. Run this before first use of agent-session-briefing, or when you want to add a project to the constellation. Walks you through hub location, single-vs-constellation, and the context file, then scaffolds it for you.
agent-session-briefing
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.
chat-session-briefing
Maintain continuity across multi-session projects in a chat interface (claude.ai web or desktop) using a single structured markdown session briefing. Use this skill whenever the user is working on a project that spans multiple conversations, whenever they ask to create or update a session briefing, project status document, or context handoff note, or whenever they mention resuming work from a previous session. Also trigger when the user starts a new multi-step project and needs a system for tracking progress across sessions — even if they don't explicitly say "session briefing." If the user references prior sessions, version histories, or asks to "pick up where we left off," this skill applies. Covers both creating the first briefing for a new project and updating an existing one. For coding agents that run in a repo with a context file (AGENTS.md/CLAUDE.md) and git, use agent-session-briefing instead.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.