agentsclimarketplace

Session init

Skill mshadmanrahman/pm-operating-system/_context/skills/session-init

An opinionated workflow system that restructures how product managers work with Claude Code. 16 PM skills, 9 agents, 10 coding rules, 13 slash commands, 6 automation hooks, product brain system, and session lifecycle with memory/handoffs.

Install
npx -y skills add mshadmanrahman/pm-operating-system --skill session-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Lightweight session initialization. Reads latest manifests and handoffs to resume context. Loads only what the current task needs. Trigger on session start, "resume", "pick up where I left off", "continue from last session", "init".

SKILL.md

2.1 KB, as published. Nobody here has run it

Session Init Skill

Initializes a session with minimal context. Checks for prior work to resume, cleans stale data, and reports readiness.

When to Activate

  • First message of a new session (if user wants to resume prior work)
  • User says "resume", "init", "pick up where I left off", "continue from last session"

Protocol

Step 1: Check for Active Handoffs

ls -lt _context/handoffs/*.md 2>/dev/null | head -3

If a handoff exists from the last 48 hours, read and summarize the most recent one in 2 sentences.

Step 2: Check for Active Manifests

# Today's manifests
ls .claude/manifests/$(date -u +%Y-%m-%d)/*.jsonl 2>/dev/null
# Yesterday's manifests
ls .claude/manifests/$(date -u -v-1d +%Y-%m-%d)/*.jsonl 2>/dev/null

If manifests exist from today or yesterday:

  1. Count total entries across all files
  2. Extract entries with type: "followup" or type: "error"
  3. Summarize: N findings, N decisions, N follow-ups, N errors

Step 3: Clean Stale Data

# Archive manifest folders older than 7 days
find .claude/manifests/ -maxdepth 1 -type d -mtime +7 -not -name archive -not -name manifests 2>/dev/null | while read dir; do
  mv "$dir" .claude/manifests/archive/ 2>/dev/null
done

Step 4: Report

Present a brief session context (under 150 tokens):

Session ready.
- Handoff: {title} ({date}): {1-line summary}
- Manifests: {N} entries from {date}. Follow-ups: {list}
- Suggested next: {action from handoff or open follow-ups}

If nothing exists:

Clean session. No prior handoffs or manifests.

Rules

  • NEVER load other skills proactively. Skills load on demand by trigger.
  • Keep init output under 150 tokens. The point is to stay lean.
  • If user explicitly states what they want to work on, skip resume checks and go straight to their task.
  • Do NOT read MEMORY.md here; it is auto-loaded by Claude Code already.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.