resume

To recover context after context window compression, the resume skill reloads critical feature details from task files and git status. It detects the current project state, active tasks, and recent code changes so you pick up exactly where you left off.

To resume an interrupted development task, the skill analyzes your git branch name to automatically detect the active feature. It loads feature context files to highlight progress, blockers, and immediate next steps for your current coding session.

Assessing code state when returning to a project is handled by checking git status and evaluating uncommitted changes. The resume skill provides a structured summary of progress, next steps, and code state to maintain continuity in long-running development tasks.

Task files are not strictly required for context recovery; the skill can detect feature names from git branch names alone. However, loading feature context from task files provides deeper insight into progress, blockers, and immediate next steps.

Yes, you can get a summary of blockers and next steps by loading feature context from task files. The resume skill prioritizes active tasks and provides a structured summary of progress, blockers, and immediate next steps for your current feature.

You should not rely on automated session management when you lack git status data or feature context files. Context recovery depends on analyzing active tasks, branch names, and code state to generate a structured summary of progress and next steps.