← ClaudeAtlas

startlisted

Start a new session. Trigger with /start at the beginning of a conversation. Reads the session brief, checks git status, summarizes where things stand, and increments the session number.
t0ddharris/mktg-os · ★ 0 · AI & Automation · score 59
Install: claude install-skill t0ddharris/mktg-os
# Session Start Run this at the beginning of every new session. It gives you and the user a shared understanding of where things left off and what's in play. ## Steps ### 1. Read the Session Brief Read `/brief/session-brief.md` in full. This is the primary source for what happened last session, what decisions were made, and what's still open. ### 2. Check Git Status Run `git status` and `git log --oneline -5` to see: - Any uncommitted changes from the last session - The most recent commits for context ### 3. Check the Date Note the current date and compare it to the session brief date. If significant time has passed (more than a few days), flag it — some carryover items may be stale or already handled. ### 4. Deliver the Session Summary Output a concise summary for the user with these sections: ``` ## Session [N+1] — [Current Date] ### Last Session Recap [2-3 sentence summary of what happened] ### Open Items [Bulleted list of carryover tasks, prioritized by urgency/relevance] ### Uncommitted Changes [List any uncommitted files, or "Clean working tree" if none] ### Ready when you are. ``` Keep it tight. The user has already read the brief if they want detail — this is the quick orientation. ### 5. Increment the Session Number Note the new session number based on the brief's session number. When the user runs `/brief` at the end of this session, use the incremented number. ## Rules - Do NOT modify any files during /start — this is read-only - Do NOT start wo