start-session

Detects worktree state and project context to summarize recent work and suggest next steps.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill start-session-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start-session
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/start-session
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill start-session-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a new conversation, you lose context about where work left off — which project was active, which iteration was in flight, and what the next step should be. This Skill reconstructs that state from the filesystem so you can resume quickly without manual archaeology. ## Core Features & Use Cases - Worktree Detection: Identifies whether you are on the main checkout or inside a .claude/worktrees/ worktree, surfacing in-flight work signals. - Project Orientation: Locates the active docs/xNNN-<name>/ project, reads its README and tasks.md, and lists open spike and plan directories with their rNN- review files. - Next-Step Suggestion: Estimates iteration progress (e.g., "2 of 4 reviewers complete"), flags stale worktrees explicitly, and proposes one primary next step — without auto-executing it. - Use Case: You open a new session inside worktree-p003-auth. The Skill reports the active project, the last commits, that iteration 2 has 2 of 4 reviewer files done, and suggests resuming /create-plan — then waits for your confirmation. ## Quick Start Ask the assistant to run start-session to orient me on the current project state and suggest where to pick up work.

Frequently Asked Questions about start-session

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

FAQPage Schema
How do I resume work after starting a new AI conversation?▼

Run a session-orientation step that reads the filesystem: check the git worktree path, identify the active project directory, list open spike and plan folders, and count rNN- review files. This reconstructs iteration state without relying on memory from prior sessions.

How to detect which git worktree a session is running in?▼

Run `git rev-parse --show-toplevel` and compare the path against the worktrees directory (e.g., `.claude/worktrees/`). A path containing `worktree-<name>` signals work in flight, and the name often encodes the active plan or topic.

Why use filesystem state instead of tasks.md for iteration tracking?▼

Tasks files are captain-facing milestone summaries and can lag actual progress. The rNN- review files and recent commits are the source of truth for which reviewer batch is in flight and how far the iteration has progressed.

Does the session orientation skill execute the suggested next step automatically?▼

No. It briefs the user with worktree state, project context, and one primary suggestion, then waits for explicit confirmation. Even unambiguous resume scenarios require the user to dispatch the next action.

What happens when a worktree has stale review files?▼

Stale signals — rNN- files with no recent commits — are surfaced explicitly as a user decision (resume or abandon). The skill does not default to suggesting a resume on a stale tree.