session-start

Aggregate incomplete tasks and project state into a session context report.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/t-hasuike/CLysis --skill session-start-t-hasuike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-start
Source: https://github.com/t-hasuike/CLysis/tree/main/legacy-investigation/skills/session-start
Command: npx skills add https://github.com/t-hasuike/CLysis --skill session-start-t-hasuike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recovering and synthesizing context across sessions is tedious and error-prone. This Skill collects incomplete tasks, current project state, open issues, and knowledge changes to present a clear, actionable priority list to the leader.

Core Features & Use Cases

  • Context aggregation: compiles in-progress work, open issues, and knowledge updates into a single report.
  • Role-based workflow: defines Leader, Planner, Worker, and Inspector responsibilities to ensure accountability.
  • Output preservation: saves the generated context to reports/session_context and provides a leader-facing report.
  • Use case: startup a new session to quickly regain situational awareness and set today’s priorities after a long interruption.

Quick Start

Invoke the session-start skill to generate today’s context report.

Frequently Asked Questions about session-start

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

FAQPage Schema
How do I recover context and prioritize tasks at the start of a new work session?▼

To recover session context and prioritize tasks, aggregate incomplete work, project state, open issues, and knowledge changes into a single actionable report. This synthesizes previous session data to present today's priority tasks to the leader.

How does context aggregation from previous sessions work for project management?▼

Context aggregation compiles in-progress work, open issues, and knowledge updates from previous sessions into a single leader-facing report. It defines Leader, Planner, Worker, and Inspector responsibilities to ensure accountability across multiple projects.

What is the best way to summarize incomplete tasks and project state after a long interruption?▼

The best way to summarize incomplete tasks after an interruption is to generate a context report that aggregates in-progress work and open issues. This provides situational awareness and sets today's priorities automatically.

Do I need specific directories or files to generate a session context report?▼

Yes, generating a session context report requires access to the knowledge/ and workspace/in_progress/ directories. The aggregated report is then saved directly to the reports/session_context/ directory for output preservation.

Can I use GitHub Issues to enhance task prioritization and project state recovery?▼

Yes, you can use GitHub Issues to enhance context recovery by running the aggregation in --full mode. This mode integrates memory and GitHub Issues data for a more comprehensive view of open issues alongside local workspace files.

What are the limitations of using automated session context recovery for task management?▼

Limitations include a strict dependency on specific directory structures like knowledge/ and workspace/in_progress/ for file access. Without these predefined folders and the --full mode flag, GitHub Issues and memory data cannot be integrated into the final report.