session-init_skill

Overview

This skill initializes a development session by checking the environment and summarizing current task status. It runs lightweight file and Git checks, inspects Plans.md and AGENTS.md, and surfaces any carry-over items from the previous session. Use it at the start of a work session to get a clear, actionable snapshot before you begin.

How this skill works

When triggered, the skill performs parallel checks: Git status and recent commits, Plans.md contents and size, top lines of AGENTS.md, and optional Claude-mem context if configured. It extracts task markers (e.g., cc:WIP, pm:依頼中, cc:TODO), warns if large files need cleanup, and compiles a concise session report with branch, priority tasks, constraints, and next-action suggestions. Claude-mem output is shown only if the user has it enabled.

When to use it

• At the very start of a coding session or daily work block
• When a user asks “what should I work on?” or “start session”
• Before taking new implementation work to ensure context and constraints
• When you need a quick summary of outstanding tasks and blockers
• When you want to confirm role rules and prohibitions from AGENTS.md

Best practices

• Run this skill only at session start — avoid during mid-session reviews or when already implementing
• Ensure Plans.md and AGENTS.md are up to date so the report is accurate
• Keep Plans.md and session-log.md small; the skill warns if they exceed recommended sizes
• Enable Claude-mem for richer historical context, but it is optional
• Confirm AGENTS.md constraints before accepting tasks or changing roles

Example use cases

• Morning check-in to collect branch, recent commits, and top 1–2 priority tasks
• Quick pre-task verification when taking over someone else’s work
• Identifying carry-over WIP and choosing whether to resume or replan
• Detecting large session logs or Plans.md and prompting cleanup
• Generating a short session report to paste into a standup or ticket