Update Claude Code skill with compaction survival, enhanced TodoWrite integration, and CLI docs (#85)

Thanks for accepting the original contribution! I've made some updates based on
real-world usage.

Some of the examples in the original were a bit idiosyncratic to my own work,
so I've generalized them to use universal programming scenarios (authentication,
database migrations, API design) that should be more relatable to any developer.

I've also added some broader improvements to the skill. Apologies for not doing
these as two separate pull requests - I hope bundling them together is OK.

These improvements came largely from asking Claude to reflect on what was useful
and difficult about using the skill - in particular, Claude felt that the
post-compaction scenario was a powerful one because normally a context compaction
causes severe loss of state.

Main changes:
- Add comprehensive compaction survival guide with note-taking patterns
- Replace basic TodoWrite integration with temporal layering pattern
- Add bd export/import documentation with collision resolution
- Clarify when to ask before creating issues vs creating directly
- Add database discovery rules for multi-DB scenarios

examples/claude-code-skill/references/WORKFLOWS.md

@@ -5,6 +5,7 @@ Detailed step-by-step workflows for common bd usage patterns with checklists.
 ## Contents
 
 - [Session Start Workflow](#session-start) - Check bd ready, establish context
+- [Compaction Survival](#compaction-survival) - Recovering after compaction events
 - [Discovery and Issue Creation](#discovery) - Proactive issue creation during work
 - [Status Maintenance](#status-maintenance) - Keeping bd status current
 - [Epic Planning](#epic-planning) - Structuring complex work with dependencies
@@ -42,6 +43,52 @@ Session Start (when bd is available):
 
 ---
 
+## Compaction Survival {#compaction-survival}
+
+**Critical**: After compaction events, conversation history is deleted but bd state persists. Beads are your only memory.
+
+**Post-compaction recovery checklist:**
+
+```
+After Compaction:
+- [ ] Run bd list --status in_progress to see active work
+- [ ] Run bd show <issue-id> for each in_progress issue
+- [ ] Read notes field to understand: COMPLETED, IN PROGRESS, BLOCKERS, KEY DECISIONS
+- [ ] Check dependencies: bd dep tree <issue-id> for context
+- [ ] If notes insufficient, check bd list --status open for related issues
+- [ ] Reconstruct TodoWrite list from notes if needed
+```
+
+**Pattern**: Well-written notes enable full context recovery even with zero conversation history.
+
+**Writing notes for compaction survival:**
+
+**Good note (enables recovery):**
+```
+bd update issue-42 --notes "COMPLETED: User authentication - added JWT token
+generation with 1hr expiry, implemented refresh token endpoint using rotating
+tokens pattern. IN PROGRESS: Password reset flow. Email service integration
+working. NEXT: Need to add rate limiting to reset endpoint (currently unlimited
+requests). KEY DECISION: Using bcrypt with 12 rounds after reviewing OWASP
+recommendations, tech lead concerned about response time but benchmarks show <100ms."
+```
+
+**Bad note (insufficient for recovery):**
+```
+bd update issue-42 --notes "Working on auth feature. Made some progress.
+More to do later."
+```
+
+The good note contains:
+- Specific accomplishments (what was implemented/configured)
+- Current state (which part is working, what's in progress)
+- Next concrete step (not just "continue")
+- Key context (team concerns, technical decisions with rationale)
+
+**After compaction**: `bd show issue-42` reconstructs the full context needed to continue work.
+
+---
+
 ## Discovery and Issue Creation {#discovery}
 
 **When encountering new work during implementation:**