Project Session Management FAQs

Question 1

How do I use the /wrap-session command?

Accepted Answer

Run this command when you reach a stopping point or your context window is full; it automates updating progress, creating a Git checkpoint, and summarizing your project state.

Question 2

What is a SESSION.md file?

Accepted Answer

It is a navigation hub located in your project root that tracks the current phase, progress, and specific next actions to bridge work across context window limits.

Question 3

What is the difference between phases and sessions?

Accepted Answer

Phases are units of work (like 'Auth API') defined in your plan, while sessions are units of context (what you finish before clearing history) that may span part of a phase or multiple phases.

Question 4

Do I need to use Git with this skill?

Accepted Answer

While the file-based tracking works without it, the skill is designed to leverage structured Git checkpoints to provide a robust history and easier state recovery.

Question 5

How does /continue-session help me save time?

Accepted Answer

It uses an agent to automatically read your session state and planning docs, restoring your focus to the exact file and line where you left off, saving 1-2 minutes of manual context loading.

Project Session Management

About

Key Features

Use Cases

Project Session Management

About

Key Features

Use Cases