← ClaudeAtlas

session-startlisted

Brief the user on where the project left off and suggest the next slice, using recent session logs, git history, and the roadmap
ostin-pil/claude-plugins · ★ 0 · AI & Automation · score 73
Install: claude install-skill ostin-pil/claude-plugins
Produce a concise in-chat briefing for starting a new work session. Read-only on repo content (no Write/Edit), but may run `git fetch`, `git switch -c`, and `git worktree add` so the session opens on a clean per-session branch born off `origin/main`. Counterpart to `/session-end`, which finalizes a session. This is the "where am I?" command; `/session-end` is the "wrap it up" command. ## Project configuration The manifest is this skill's configuration. If `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md` does not exist, the project has not adopted the kit: say so, offer to create it, and stop. Never infer the keys and run anyway. The kit ships the template as `lifecycle-manifest.template.md`; locate the installed copy with `find ~/.claude/plugins -path '*lifecycle-kit*' -name lifecycle-manifest.template.md | head -1`. The marketplace's `ADOPTING.md` carries a repo-inspecting setup prompt. Read `.claude/lifecycle-manifest.md` first (resolve via `$(git rev-parse --show-toplevel)/.claude/lifecycle-manifest.md`). Where a step names a manifest key in `code font` (`log_glob`, `log_dir`, `log_pattern`, `log_index`, `log_archive`, `branch_pattern`, `worktree_dir`, `worktree_pattern`, `issues_file`, `plan_doc`), use that key's value. Command bodies write these as `<key>` substitution placeholders (`<integration_ref>`, `<local_main>`, `<remote>`); replace each with the manifest value before running. The surrounding detection prose still names `feature/*`, `main`, and