fix: align bd prime guidance with skill's hybrid TodoWrite approach

Changes bd prime output from "no TodoWrite" to a nuanced hybrid approach
that matches skills/beads/SKILL.md guidance:

- Track strategic work in beads (multi-session, dependencies, discovered work)
- TodoWrite is fine for simple single-session linear tasks
- When in doubt, prefer bd—persistence you don't need beats lost context

Fixes #499

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

cmd/bd/prime.go

@@ -144,8 +144,9 @@ func outputMCPContext(w io.Writer, stealthMode bool) error {
 ` + closeProtocol + `
 
 ## Core Rules
-- Track ALL work in beads (no TodoWrite tool, no markdown TODOs)
-- Use bd MCP tools (mcp__plugin_beads_beads__*), not TodoWrite or markdown
+- Track strategic work in beads (multi-session, dependencies, discovered work)
+- TodoWrite is fine for simple single-session linear tasks
+- When in doubt, prefer bd—persistence you don't need beats lost context
 
 Start: Check ` + "`ready`" + ` tool for available work.
 `
@@ -222,8 +223,9 @@ bd sync                     # Push to remote
 ` + closeNote + `
 
 ## Core Rules
-- Track ALL work in beads (no TodoWrite tool, no markdown TODOs)
-- Use ` + "`bd create`" + ` to create issues, not TodoWrite tool
+- Track strategic work in beads (multi-session, dependencies, discovered work)
+- Use ` + "`bd create`" + ` for issues, TodoWrite for simple single-session execution
+- When in doubt, prefer bd—persistence you don't need beats lost context
 - Git workflow: hooks auto-sync, run ` + "`bd sync`" + ` at session end
 - Session management: check ` + "`bd ready`" + ` for available work