Upgrade

Customization

Before executing, check for user customizations at: ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Upgrade/

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)

You MUST send this notification BEFORE doing anything else when this skill is invoked.

1. Send voice notification:

   curl -s -X POST http://localhost:31337/notify \
     -H "Content-Type: application/json" \
     -d '{"message": "Running the WORKFLOWNAME workflow in the Upgrade skill to ACTION"}' \
     > /dev/null 2>&1 &
   

2. Output text notification:

   Running the **WorkflowName** workflow in the **Upgrade** skill to ACTION...
   

Upgrade

Primary Purpose: Generate prioritized upgrade recommendations for LifeOS by understanding the user's context and discovering what's new in the ecosystem.

The skill runs four parallel agent threads that converge into personalized recommendations:

• Thread 0 — Prior-Work Audit (Algorithm, PATTERNS.yaml, hooks, skills, recent ISAs, KNOWLEDGE, feedback memory)
• Thread 1 — User Context (TELOS, projects, recent work, LifeOS state)
• Thread 2 — Source Collection (Anthropic, YouTube, custom sources, GitHub trending)
• Thread 3 — Internal Reflections (algorithm-reflections.jsonl)

Thread 0 is the guard rail against recommending what's already implemented, already researched-and-deferred, or already decided against. Synthesis MUST filter every candidate recommendation through Thread 0's state inventory — never emit a recommendation without a Prior Status assignment.

Workflow Routing

Default workflow: If user says "upgrade" or "check for upgrades" without specifics, run the Upgrade workflow (which includes Thread 3 reflection mining).

Output Format

Canonical spec: References/OutputFormat.md — single source of truth for section order, Prior Status legend, table columns, and hard rules. Both this skill and Workflows/Upgrade.md reference that file rather than inlining their own copies.

Section order: Discoveries → Recommendations → Technique Details → Internal Reflections → Summary → Skipped → Sources Processed.

Print only non-empty Recommendation tiers (no empty 🟡 MEDIUM headers).

Extraction Rules

Extract, don't summarize. Techniques, not recommendations. Verify prior state before recommending.

1. Every output item is a TECHNIQUE — a specific pattern, code snippet, configuration, or approach.
2. Quote or code-block the actual content — show exactly what was said/written.
3. Map to LifeOS components — every technique connects to a specific file, skill, workflow, or system component.
4. Verify Prior State (Thread 0 gate) — Before emitting ANY recommendation, confirm against Thread 0 inventory: is it already in Algorithm / PATTERNS.yaml / hooks / SKILL files / KNOWLEDGE / prior ISAs? Assign a Prior Status emoji and cite evidence. Items that are ✅ DONE go to Skipped, not Recommendations.
5. Two mandatory description fields, ≤2 sentences each, concrete and specific:
   • What It Is: the technique itself — what it does, how it works, what capability it provides
   • How It Helps LifeOS: the specific benefit — which component improves, what gap it fills
6. Provide implementation — show before/after code or specific steps.
7. Skip, don't dilute — if content has no extractable technique, put it in Skipped Content with reason.

Source Type Labels:

Configuration

Skill Files:

• sources.json — Anthropic sources config (30+ sources)
• youtube-channels.json — Base YouTube channels (empty by default)
• State/last-check.json — Anthropic state
• State/youtube-videos.json — YouTube state
• State/github-trending.json — GitHub trending state (seen repos)
• State/twitter-bookmarks-seen.json — Previously processed bookmark URLs

User Customizations (~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Upgrade/):

• EXTEND.yaml — Extension manifest
• youtube-channels.json — User's personal YouTube channels
• user-sources.json — Additional source definitions (e.g., github_trending block)

Tool Reference

Key Principles

1. Extract, Don't Summarize — pull specific techniques, never just link to sources.
2. Quote the Source — actual code, doc quotes, or transcript excerpts.
3. LifeOS-Contextualized — every technique maps to a specific LifeOS file, skill, or component.
4. Explain "Why You" — "this helps because your [X] currently [Y]".
5. TELOS-Connected — reference user's goals and challenges when explaining relevance.
6. Skip Boldly — if content has no extractable technique, skip it entirely.
7. Implementation-Ready — provide actual code changes, not vague recommendations.
8. Claude Code Freshness via claude-code-guide — when discoveries involve Claude Code internals (hooks, settings, slash commands, MCP, agent types, keybindings, Agent SDK, Claude API), spawn Agent(subagent_type="claude-code-guide") to verify LifeOS's current references match the latest API surface.

Anti-Patterns (What NOT to Output)

These output patterns are FAILURES:

The test: if you can say "show me the technique" and there's nothing to show, you've failed.

Workflows

• Upgrade.md — primary workflow; full four-thread analysis with prioritized recommendations
• MineReflections.md — Thread 3 standalone (deep reflection mining)
• AlgorithmUpgrade.md — Algorithm-version-bump-focused upgrade flow
• ResearchUpgrade.md — deep dive on a specific upgrade opportunity
• FindSources.md — discover and evaluate new sources to monitor

Gotchas

• Check ALL sources in parallel — Anthropic blog, changelog, YouTube channels, GitHub releases. Don't check sequentially.
• Upgrades must not break existing skills or workflows. Verify backward compatibility before applying.
• Full upgrade check can take 5-7 minutes. Use run_in_background: true for the outer agent.

Execution Log

After completing any workflow, append a single JSONL entry:

echo '{"ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","skill":"Upgrade","workflow":"WORKFLOW_USED","input":"8_WORD_SUMMARY","status":"ok|error","duration_s":SECONDS}' >> ~/.claude/LIFEOS/MEMORY/SKILLS/execution.jsonl

Replace WORKFLOW_USED with the workflow executed, 8_WORD_SUMMARY with a brief input description, and SECONDS with approximate wall-clock time. Log status: "error" if the workflow failed.