session-start

Resume interrupted development sessions and present project state with next steps.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/tomgun/agentic-framework --skill session-start-tomgun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-start
Source: https://github.com/tomgun/agentic-framework/tree/main/.agentic/lib/agents/claude/skills/session-start
Command: npx skills add https://github.com/tomgun/agentic-framework --skill session-start-tomgun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Quickly resume interrupted development sessions and provide a concise project dashboard so work can continue without manual context gathering.

Core Features & Use Cases

  • Interrupted-work detection: Runs WIP checks and surfaces uncommitted changes or in-progress feature work so you can continue, review, or roll back safely.
  • Context aggregation: Silently reads STATUS.md, HUMAN_NEEDED.md, recent JOURNAL entries, and todo/WIP tooling to summarize current focus, progress, and blockers.
  • Guided next steps: Presents a structured dashboard with last session summary, current focus, progress status, and explicit next actions or available workflows (plan, sync, implement).
  • Use case: Return to a codebase after a break and instantly see what was in progress, whether any files are uncommitted, and what to do next.

Quick Start

Ask the agent to start a session, check for interrupted work, and show the project dashboard.

Frequently Asked Questions about session-start

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

FAQPage Schema
How do I resume interrupted development work in an agentic framework?▼

To resume interrupted development work, start a session to run WIP checks and read STATUS.md files. This aggregates your project context, surfaces uncommitted changes, and presents a dashboard with suggested next steps for your agentic framework repository.

What is the best way to check project status and uncommitted changes after a break?▼

Checking project status after a break involves reading repository files like HUMAN_NEEDED.md and recent JOURNAL entries. The session start process executes wip/todo helper commands to summarize current focus, progress, and any blockers so you can safely continue.

Can I use a project dashboard to see what was in progress during my last session?▼

Yes, you can use a project dashboard to see what was in progress. It reads JOURNAL entries and todo tooling to provide a structured summary of your last session, current focus, progress status, and explicit next actions like plan, sync, or implement workflows.

Do I need shell access to run wip and todo checks for session start?▼

Yes, you need shell access to run wip and todo checks. The session start process requires shell access to execute .agentic scripts, read repository status files, and run wip/todo helper commands to detect interrupted work and surface in-progress features.

Why does session start require specific files like STATUS.md and HUMAN_NEEDED.md?▼

Session start requires files like STATUS.md and HUMAN_NEEDED.md to aggregate context and inform decision making. Silently reading these repository status files allows the dashboard to summarize current focus, progress, and blockers without manual context gathering.