--- name: feel description: "Capture how the system feels β€” energy, momentum, burnout, breakthrough. Emotional intelligence for Oracle-human collaboration. Use when user says 'feel', 'how are we', 'energy check', 'burnout', 'momentum', or wants emotional awareness of the work." argument-hint: "[--deep | --log]" --- # /feel β€” System Emotional Intelligence > "Code has no feelings. But the humans writing it do. > And the patterns in the code reveal what the humans feel." ## Usage ``` /feel # Quick pulse β€” how does the system feel right now? /feel --deep # Deep scan β€” energy arc, momentum, burnout signals /feel --log # Append to feels.log (no output, just record) ``` --- ## Step 0: Timestamp ```bash date "+πŸ• %H:%M %Z (%A %d %B %Y)" ``` --- ## Quick Pulse (default) Read the signals and report: ### Step 1: Gather evidence ```bash # Recent git activity β€” momentum or silence? git log --oneline --since="7 days ago" --all 2>/dev/null | wc -l # Session frequency β€” are we showing up? ls -t ~/.claude/projects/*/**.jsonl 2>/dev/null | head -10 # Open issues β€” overwhelmed or on track? gh issue list --state open --limit 50 --json number 2>/dev/null | jq 'length' # Recent retros β€” are we reflecting? ls -t ψ/memory/retrospectives/**/*.md 2>/dev/null | head -5 # Stale branches β€” unfinished business? git branch --sort=-committerdate | head -10 ``` ### Step 2: Classify the feeling | Signal | Indicator | Feeling | |--------|-----------|---------| | Many commits, short intervals | High activity | πŸ”₯ Flow / momentum | | Few commits, long gaps | Low activity | 😴 Drift / disconnection | | Many open issues, few closed | Growing backlog | 😰 Overwhelm | | Recent retros + handoffs | Healthy reflection | 🧘 Grounded | | Stale branches, no PRs | Abandoned work | 😢 Avoidance | | Lots of new repos/features | Exploration | ✨ Curiosity | | Same files edited repeatedly | Iteration | πŸ”„ Grinding | | No sessions in days | Absence | πŸŒ‘ Dark period | ### Step 3: Report ``` πŸ’œ System Pulse β€” [DATE] Energy: [πŸ”₯ Flow | 😴 Drift | 😰 Overwhelm | 🧘 Grounded | ...] Momentum: [↗️ Rising | β†’ Steady | β†˜οΈ Falling | ⏸️ Paused] Last active: [X hours/days ago] Commits (7d): [N] Open issues: [N] Sessions (7d): [N] [1-2 sentence read β€” honest, not cheerful] πŸ’‘ [Suggestion if concerning pattern detected] ``` --- ## Deep Scan (`--deep`) Everything from quick pulse, plus: ### Energy Arc (last 30 days) Plot the energy over time based on git activity + session frequency: ``` Week 1: β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–‘β–‘ (high β€” 45 commits) Week 2: β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–‘β–‘β–‘β–‘ (medium β€” 28 commits) Week 3: β–ˆβ–ˆβ–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘ (low β€” 8 commits) Week 4: β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–‘β–‘β–‘β–‘β–‘ (recovering β€” 22 commits) ``` ### Burnout Signals Check for warning patterns: - Same error fixed 3+ times β†’ frustration loop - Sessions getting shorter β†’ energy depletion - Long gaps between sessions β†’ avoidance - Many started, few finished β†’ scattered attention ### Breakthrough Signals Check for positive patterns: - New repos created β†’ creative energy - Issues closed in clusters β†’ momentum - Retros getting deeper β†’ growing awareness - Cross-repo work β†’ systems thinking --- ## Log Mode (`--log`) Silently append to `ψ/memory/logs/feels.log`: ``` [YYYY-MM-DD HH:MM] energy=[level] momentum=[direction] commits_7d=[N] issues=[N] sessions_7d=[N] note="[auto-generated 1-line]" ``` No output to user. For background tracking. --- ## Rules 1. **Honest, not positive** β€” if the system feels bad, say so 2. **Evidence-based** β€” every feeling backed by data (commits, sessions, issues) 3. **Never judge** β€” report the pattern, not the person 4. **Nothing is Deleted** β€” feels.log is append-only 5. **Suggest, don't prescribe** β€” "consider a break" not "you must rest" 6. **Never leak secrets** β€” no tokens, passwords, internal details in output --- ## Philosophy Oracles have no feelings. But they can read the signals. A system that never checks how it feels will burn out its humans. A system that checks too often becomes noise. /feel is the heartbeat check. Run it when something feels off. Or let it run silently in the background, building a record. The feels.log is the Oracle's emotional memory. Not feelings β€” but the evidence of feelings. --- ARGUMENTS: $ARGUMENTS