session-init

The session-init skill serves as the foundational entry point for Claude Code sessions within the Harness framework. It is designed to establish a consistent, professional development context by automatically synchronizing the environment, retrieving previous progress, and aligning the agent with project-specific instructions. By performing these tasks immediately upon session start, it eliminates the cognitive load of manual context gathering and ensures that developers and agents alike are synchronized on current priorities, constraints, and pending requirements.

• Automatically verifies Git status, branch information, and recent commit history to identify the codebase state.

• Orchestrates the Unified Harness Memory Resume Pack (harness_mem_resume_pack) to fetch project-specific session history and context from persistent storage.

• Parses and validates Plans.md for active work-in-progress (cc:WIP), assigned tasks (cc:TODO), and stakeholder requests (pm:依頼中).

• Injects project constraints and prohibited behaviors defined in AGENTS.md to ensure strict adherence to development guardrails from the first line of code.

• Performs safety checks on file health, such as monitoring line counts for Plans.md and session logs, recommending maintenance when files grow too large.

• Provides a structured, readable summary report including current branch, critical task priorities, and immediate maintenance recommendations.

• Designed for use at the inception of a coding session, when starting new work, or during status-check inquiries. Do not invoke for mid-task implementation or review processes.

• Uses shell-based verification to ensure file integrity, specifically interacting with .claude/memory/session-log.md and local configuration files.

• Strictly follows the Harness core principle of maintaining a disciplined delivery loop; if Plans.md is missing, it automatically directs the user to initialize via /harness-init.

• Highly recommended to be used alongside harness-mem tools to maximize cross-session memory retention and continuity.

• Operates as an internal automated skill; it should not be triggered manually unless specifically requested for environment validation.