solo-session-protocol

Manages session start, checkpoint, and end protocols for project continuity.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-session-protocol-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-session-protocol
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-session-protocol
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-session-protocol-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo developers lose project context between work sessions, forcing them to manually reconstruct what was done, what decisions are pending, and what to do next. This Skill standardizes session startup, checkpointing, and shutdown so progress, decisions, and TODOs persist across sessions. ## Core Features & Use Cases - 5-Step Session Start Protocol: Reads CLAUDE.md, loads the latest session log, checks pending decisions in decision_log.md, reviews team_plan.md, and reports a proposed plan to the PM for approval. - 6-Step Session End Protocol: Writes a structured session log, updates the decision log, syncs CLAUDE.md sections, recalculates phase progress, and delivers a final PM report. - Mid-Session Checkpoints: Saves interim progress snapshots so work can resume after interruptions. - Use Case: A solo developer says "세션 종료" at the end of the day; the Skill generates a dated session log with completed tasks, decisions, next-session TODOs, and lessons learned, then updates the project plan. ## Quick Start Ask the assistant to start a new session so it restores context from the latest session log and proposes today's goals.

Frequently Asked Questions about solo-session-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore project context when starting a new work session?▼

Run the session start protocol, which reads CLAUDE.md, loads the most recent session log from docs/00_관리/sessions/, checks pending decisions in decision_log.md, and reviews team_plan.md. It then reports a proposed plan to the PM for approval before work begins.

How do I save progress at the end of a work session?▼

Trigger the session end protocol by saying "세션 종료" or "세션 저장". It writes a structured session log with completed tasks, decisions, next-session TODOs, and lessons learned, then updates decision_log.md, team_plan.md, and CLAUDE.md sections.

Can I save progress mid-session without ending it?▼

Yes, use the checkpoint feature by saying "체크포인트 저장" or "중간 진행 상황 저장". It records completed tasks, current agent assignments, and next task readiness into an interim checkpoint file so work can resume later.

What happens if no previous session log exists?▼

The protocol checks the sessions folder and CLAUDE.md history; if nothing is found, it treats the session as the first one, creates session_YYYY-MM-DD_1.md, and reports the situation to the PM.

What are the limitations of this session management approach?▼

It depends on a specific docs folder structure (sessions, decisions, team_plan.md) and CLAUDE.md sections, so projects without this layout need setup first. It also relies on disciplined log writing rather than automated state tracking.