session-management

Manage .NET session lifecycles by loading handoffs, memory, and instincts.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill session-management-codewithmukesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-management
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/session-management
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill session-management-codewithmukesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sessions often start blind and end without captured context, causing wasted time and lost decisions; this Skill ensures continuity by loading prior work, preserving learnings, and safely wrapping up sessions so future work resumes immediately.

Core Features & Use Cases

  • Session Start Protocol: Automatically load .claude/handoff.md, MEMORY.md, and .claude/instincts.md, detect the .slnx/.sln solution, and confirm MCP tool connectivity before accepting work.
  • Session End Capture: Summarize completed work, check git status, write a concise handoff, extract learnings into MEMORY.md, and update instincts to preserve patterns.
  • Context Preservation & Collaboration: Maintain a clear flow between handoff, memory, instincts, and git commits; support multi-developer handoffs with merge/overwrite choices and concise templates.
  • Use Case: Resume a half-finished feature on branch feature/order-validation by loading the handoff, summarizing pending tasks, and offering to continue from the exact file and line references.

Quick Start

Load session context by reading .claude/handoff.md, MEMORY.md, and .claude/instincts.md, detect the solution file, confirm MCP connectivity, and present a concise summary of completed, pending, and learned items.

Frequently Asked Questions about session-management

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

FAQPage Schema
How do I preserve context and resume a half-finished .NET development session?

To preserve context and resume a .NET development session, this Skill reads .claude/handoff.md and MEMORY.md to load prior work, summarize pending tasks, and offer to continue from exact file and line references.

What is the best way to manage handoffs for multi-developer .NET projects?

Managing multi-developer handoffs involves writing concise handoff files at session end, checking git status, and offering merge or overwrite choices to maintain clear flow between memory, instincts, and git commits.

How does solution detection work when starting a session in a .NET repository?

Solution detection automatically searches across directory levels to locate .slnx or .sln files before accepting work, ensuring the correct project context is loaded for the upcoming development session.

Can I use MCP tools during my .NET development workflow?

Yes, you can use MCP tools during your workflow because the session start protocol confirms MCP tool connectivity alongside loading project context and detecting the .slnx or .sln solution file.

What happens if handoff or memory files are missing when starting a session?

When handoff or memory files are missing, the session management protocol handles the missing context gracefully, allowing you to start a new session without causing errors or blocking project work.

How do I capture learnings and update instincts at the end of a dev session?

To capture learnings at session end, the protocol summarizes completed work, extracts learnings into MEMORY.md, and updates instincts to preserve patterns, writing a concise handoff file for future continuity.