session-start

Extract project context from documentation and Git history into a prioritized briefing.

Updated Feb 8, 2026

Search Tags:#automation #documentation #git-history #context-loading #agent-integration #project-briefing #workspace-scoping

Ready to run

npx skills add https://github.com/ckallum/calsuite --skill session-start-ckallum

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-start
Source: https://github.com/ckallum/calsuite/tree/main/skills/session-start
Command: npx skills add https://github.com/ckallum/calsuite --skill session-start-ckallum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates project documentation, specs, tasks, and history to produce a focused, actionable briefing for a session.

Core Features & Use Cases

Delegates to the @context-loader agent to load comprehensive project context from root or a specified workspace.
Produces a prioritized briefing that guides session focus, decisions, and next actions.
Supports optional workspace scoping via ARGUMENTS while still reading root-level files for context.

Quick Start

Run the @context-loader agent to read all project documentation, specs, tasks, and git history, then produce a prioritized briefing for the session.

Frequently Asked Questions about session-start

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

FAQPage Schema

How do I generate a project briefing from README and Git history?▼

To generate a project briefing, the system reads all README, CLAUDE, SPECLOG, CHANGELOG, specs, tasks, and Git history to extract and summarize comprehensive project context into a prioritized session focus.

Can I scope a project briefing to a specific workspace?▼

Yes, you can scope a project briefing to a specific workspace by passing the workspace name via the ARGUMENTS parameter, while still reading root-level files for broader context.

What is the best way to aggregate documentation and specs for a session?▼

Aggregating documentation and specs for a session is best handled by delegating to the context-loader agent, which reads all project files and Git history to produce a focused, actionable briefing.

Does the briefing process require any external dependencies?▼

No, the briefing process requires no external dependencies, relying solely on the context-loader agent to read existing project files and Git history to deliver a prioritized workspace briefing.

What happens if no workspace is specified for the briefing?▼

When no workspace is specified, the context-loader agent reads all root-level project documentation and Git history to deliver a full project briefing instead of a scoped summary.

How do I prioritize project tasks using documentation and Git history?▼

You can prioritize project tasks by running the context-loader agent, which analyzes documentation, specs, tasks, and Git history to produce a briefing that guides session focus and next actions.