---
name: fixup-obsidian-sync
description: Use this skill after completing a FixUp block to decide which Obsidian documents need updating — Current Block, Change Log, or Strategy. Does not write content; decides what needs updating and why.
triggers:
  - /fixup-obsidian-sync
---

# FixUp Obsidian Sync

Use after completing a block to decide what Obsidian documents need updating.

## Decision protocol

### Current Block.md
**Update when:** the block status changed (started, completed, blocked, deferred).
**Path:** `~/Library/Mobile Documents/iCloud~md~obsidian/Documents/FixUp/01 FixUp/Current Block.md`
**What to update:** status, completed items, next step.

### Change Log
**Update when:** a meaningful, shippable change was made to production behavior — new feature, fix to domain logic, persistence change, API change, significant UI behavior change.
**Path:** `~/Library/Mobile Documents/iCloud~md~obsidian/Documents/FixUp/01 FixUp/` (or wherever the change log is maintained)
**What to update:** date, what changed, why, any external steps applied.

### FixUp Strategy.md
**Update when:** a strategic direction, architecture decision, or domain design decision was made or changed. Not for individual bug fixes.
**Path:** `~/Library/Mobile Documents/iCloud~md~obsidian/Documents/FixUp/01 FixUp/FixUp Strategy.md`
**What to update:** only if the strategic picture actually changed.

### Builder Raw (via /learn)
**Capture when:** the block produced a non-obvious insight, architectural tradeoff, or reusable learning. Delegate to `/learn` for classification and writing.

## Output format

For each document: UPDATE NEEDED / NO UPDATE NEEDED + one-line reason.
If update is needed: state the exact content that should be written.

## Hard rule

Do not update Obsidian for:
- Trivial changes (renaming, formatting, comment fixes)
- Changes already fully captured in git commit messages
- In-progress blocks not yet at a shippable milestone