{"id":"continuity-ledger","name":"continuity-ledger","summary":"クリアを越えた状態保持のための連続性台帳の作成または更新","body":"# Continuity Ledger\n\n> **Note:** This skill is now an alias for `/create_handoff`. Both output the same YAML format.\n\nCreate a YAML handoff document for state preservation across `/clear`. This is the same as `/create_handoff`.\n\n## Process\n\n### 1. Filepath & Metadata\n\n**First, determine the session name from existing handoffs:**\n```bash\nls -td thoughts/shared/handoffs/*/ 2>/dev/null | head -1 | xargs basename\n```\n\nThis returns the most recently modified handoff folder name (e.g., `open-source-release`). Use this as the handoff folder name.\n\nIf no handoffs exist, use `general` as the folder name.\n\n**Create your file under:** `thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml`, where:\n- `{session-name}` is from existing handoffs (e.g., `open-source-release`) or `general` if none exist\n- `YYYY-MM-DD` is today's date\n- `HH-MM` is the current time in 24-hour format (no seconds needed)\n- `description` is a brief kebab-case description\n\n**Examples:**\n- `thoughts/shared/handoffs/open-source-release/2026-01-08_16-30_memory-system-fix.yaml`\n- `thoughts/shared/handoffs/general/2026-01-08_16-30_bug-investigation.yaml`\n\n### 2. Write YAML handoff (~400 tokens)\n\n**CRITICAL: Use EXACTLY this YAML format. Do NOT deviate or use alternative field names.**\n\nThe `goal:` and `now:` fields are shown in the statusline - they MUST be named exactly this.\n\n```yaml\n---\nsession: {session-name from ledger}\ndate: YYYY-MM-DD\nstatus: complete|partial|blocked\noutcome: SUCCEEDED|PARTIAL_PLUS|PARTIAL_MINUS|FAILED\n---\n\ngoal: {What this session accomplished - shown in statusline}\nnow: {What next session should do first - shown in statusline}\ntest: {Command to verify this work, e.g., pytest tests/test_foo.py}\n\ndone_this_session:\n  - task: {First completed task}\n    files: [{file1.py}, {file2.py}]\n  - task: {Second completed task}\n    files: [{file3.py}]\n\nblockers: [{any blocking issues}]\n\nquestions: [{unresolved questions for next session}]\n\ndecisions:\n  - {decision_name}: {rationale}\n\nfindings:\n  - {key_finding}: {details}\n\nworked: [{approaches that worked}]\nfailed: [{approaches that failed and why}]\n\nnext:\n  - {First next step}\n  - {Second next step}\n\nfiles:\n  created: [{new files}]\n  modified: [{changed files}]\n```\n\n**Field guide:**\n- `goal:` + `now:` - REQUIRED, shown in statusline\n- `done_this_session:` - What was accomplished with file references\n- `decisions:` - Important choices and rationale\n- `findings:` - Key learnings\n- `worked:` / `failed:` - What to repeat vs avoid\n- `next:` - Action items for next session\n\n**DO NOT use alternative field names like `session_goal`, `objective`, `focus`, `current`, etc.**\n**The statusline parser looks for EXACTLY `goal:` and `now:` - nothing else works.**\n\n### 3. Mark Session Outcome (REQUIRED)\n\n**IMPORTANT:** Before responding to the user, you MUST ask about the session outcome.\n\nUse the AskUserQuestion tool with these exact options:\n\n```\nQuestion: \"How did this session go?\"\nOptions:\n  - SUCCEEDED: Task completed successfully\n  - PARTIAL_PLUS: Mostly done, minor issues remain\n  - PARTIAL_MINUS: Some progress, major issues remain\n  - FAILED: Task abandoned or blocked\n```\n\nAfter the user responds, mark the outcome:\n```bash\n# Mark the most recent handoff (works with PostgreSQL or SQLite)\nPROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo \"${CLAUDE_PROJECT_DIR:-.}\")\ncd \"$PROJECT_ROOT/opc\" && uv run python scripts/core/artifact_mark.py --latest --outcome <USER_CHOICE>\n```\n\n### 4. Confirm completion\n\nAfter marking the outcome, respond to the user:\n\n```\nHandoff created! Outcome marked as [OUTCOME].\n\nResume in a new session with:\n/resume_handoff path/to/handoff.yaml\n```\n\n## When to Use\n\n- Before running `/clear`\n- Context usage approaching 70%+\n- Multi-day implementations\n- Complex refactors you pick up/put down\n- Any session expected to hit 85%+ context\n\n## When NOT to Use\n\n- Quick tasks (< 30 min)\n- Simple bug fixes\n- Single-file changes\n\n## Why Clear Instead of Compact?\n\nEach compaction is lossy compression—after several compactions, you're working with degraded context. Clearing + loading the handoff gives you fresh context with full signal.","author":"@parcadei","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/continuity_ledger","license":"MIT","category":"writing","lang":"en","tokens":1062,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}