session-state

Updates SESSION_STATE.md and AGENTS.md continuity sections to record project handoff state.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahsanghalib/ai-workflow --skill session-state-ahsanghalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-state
Source: https://github.com/ahsanghalib/ai-workflow/tree/main/skills/session-state
Command: npx skills add https://github.com/ahsanghalib/ai-workflow --skill session-state-ahsanghalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work pauses or hands off between sessions, context about current focus, blockers, and next steps is lost. This Skill keeps an existing project's SESSION_STATE.md and AGENTS.md continuity section current so the next session can resume without guessing. ## Core Features & Use Cases - State Updates: Records current focus, active SPEC/PLAN, completed and in-progress work, blockers, findings, validation results, and next steps in the project-root SESSION_STATE.md. - Continuity Contract Enforcement: Ensures AGENTS.md contains exactly one Session continuity section with the required bullets, without duplicating or replacing existing content. - Safety Boundaries: Refuses to create missing files (routing to project-init instead), never reads secrets or .env contents, and never writes outside the resolved project root. - Use Case: Before ending a coding session, invoke this Skill to capture what was done, what validation ran, and what the next session should tackle first. ## Quick Start Update this project's SESSION_STATE.md with the current status, blockers, and next steps before I hand off to another session.

Frequently Asked Questions about session-state

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

FAQPage Schema
How do I update SESSION_STATE.md before handing off a project?▼

Invoke the session-state skill after meaningful work or before handoff. It reads the existing SESSION_STATE.md and AGENTS.md, derives current state from repository evidence and actual validation output, then updates only those files with status, blockers, and next steps.

What should a session handoff document contain?▼

A handoff document should record current focus, active SPEC/PLAN references, completed and in-progress work, blockers, assumptions, validation performed, and next steps. Keep it concise at roughly 50-150 lines and move permanent knowledge to README or architecture docs.

Can session-state create SESSION_STATE.md if it is missing?▼

No. If SESSION_STATE.md or AGENTS.md is missing, the skill stops and directs you to project-init strict bootstrap, which owns template-based creation. It only updates existing files and never creates a parallel state schema.

Does session-state commit changes or modify application code?▼

No. The skill never stages, commits, changes application files, or modifies remote state. It only edits the project-root SESSION_STATE.md and the AGENTS.md continuity section, then reports the exact files changed and validation performed.

Why should SESSION_STATE.md be excluded from version control?▼

SESSION_STATE.md is short-term working context, not permanent project knowledge, so the root .gitignore should cover it. The skill verifies ignore coverage and reports gaps rather than silently editing .gitignore.