shipkit-work-memory

shipkit-work-memory - Session Progress & Resume State

Purpose: Capture structured session progress — milestones, blockers, decisions, and resume state — by inferring from conversation and git. User confirms, Claude does the work.

Note: Claude Code's auto-memory (v2.1.59+) automatically saves basic session context. This skill is for structured progress tracking that auto-memory doesn't capture: explicit milestones, decision rationale, blocker status, and handoff state for session continuity.

Output: .shipkit/progress.json — A timeline graph artifact ideal for session history visualization.

---

When to Invoke

User triggers:

• "End session"
• "Log progress"
• "Save checkpoint"
• "What did we do?"
• "Save session"

Suggested after:

• Long implementation sessions
• Before context gets full
• Before switching tasks
• End of work session

---

Prerequisites

None required - Can start fresh.

Uses if available:

• .shipkit/progress.json - Merge with existing sessions
• Git - For modified files detection

---

JSON Schema (Quick Reference)

This skill outputs .shipkit/progress.json using the Shipkit JSON Artifact Convention.

{
  "$schema": "shipkit-artifact",
  "type": "work-memory",
  "version": "1.0",
  "lastUpdated": "2025-01-15T10:00:00Z",
  "source": "shipkit-work-memory",
  "summary": { "totalSessions", "currentPhase", "lastSessionDate", "activeWorkstream", "blockers", "momentum" },
  "sessions": [{ "id", "date", "duration", "workstream", "phase", "accomplished", "filesModified", "decisions", "gotchas", "blockers", "nextSteps", "status" }],
  "workstreams": [{ "id", "name", "status", "startDate", "sessions", "completionEstimate" }],
  "resumePoint": { "lastSession", "immediateNextStep", "context", "openFiles", "relatedArtifacts" },
  "timeline": [{ "date", "event", "type" }]
}

Full schema and field reference: See references/output-schema.md

Realistic example: See references/example.json