u-foo 3.0.14 → 3.0.16

package/SKILLS/ubus/SKILL.md

@@ -1,250 +0,0 @@
----
-name: ubus
-description: |
-  Check and handle pending event-bus messages when /ubus is explicitly invoked.
-  Use when: (1) asked to check messages, (2) view bus status, (3) use watch/listen/auto modes.
-  If not yet joined bus, will auto-join.
----
-
-# /ubus - Check Event Bus Messages
-
-Check and handle pending messages on the event bus when `/ubus` is explicitly
-invoked.
-
-## Arguments
-
-- `/ubus` - Pull pending messages and show status
-- `/ubus watch` - Start background auto-notification (title badge + bell + notification center)
-- `/ubus stop` - Stop background auto-notification
-- `/ubus listen` - Foreground continuous listener, print new messages (suitable for side terminal)
-- `/ubus auto` - Unattended auto-execute (auto-inject `/ubus` and press Enter)
-
-## Execution Flow
-
-### 1. Check if .ufoo/bus exists
-
-```bash
-if [[ ! -d ".ufoo/bus" ]]; then
-  echo "Event bus not initialized, please run /uinit and select bus module"
-  exit
-fi
-```
-
-### 2. Get or create subscriber ID
-
-**IMPORTANT**: Always check for existing subscriber ID first to avoid creating duplicates.
-
-```bash
-# Reuse existing subscriber first (env -> whoami), join only if missing
-SUBSCRIBER="${UFOO_SUBSCRIBER_ID:-$(ufoo bus whoami 2>/dev/null || true)}"
-if [ -n "$SUBSCRIBER" ]; then
-  echo "Using existing subscriber ID: $SUBSCRIBER"
-else
-  # Not launched via uclaude/ucodex, need to join manually
-  SUBSCRIBER=$(ufoo bus join | tail -n 1)
-  echo "Joined event bus: $SUBSCRIBER"
-  # Example output: codex:0e293156 (nickname: codex-1)
-fi
-```
-
-**Why this matters**:
-- `uclaude`/`ucodex` automatically set `UFOO_SUBSCRIBER_ID` during launch
-- `ufoo bus whoami` can recover current ID even when env is missing
-- Re-joining may create identity drift and message routing issues
-- Always reuse existing ID when available
-
-To join with a custom nickname:
-
-```bash
-ufoo bus join [session-id] [agent-type] "your-nickname"
-# Example: ufoo bus join abc123 claude-code "architect"
-```
-
-### 3. Handle arguments
-
-If argument is `watch`, use **Bash tool's `run_in_background: true`** to start background notification:
-
-```bash
-# Title badge + bell + notification center (no accessibility permission needed)
-ufoo bus alert "$SUBSCRIBER" 2 --notify --daemon
-```
-
-If argument is `listen`, foreground blocking listener (no background task tool needed):
-
-```bash
-ufoo bus listen "$SUBSCRIBER" --from-beginning
-```
-
-If argument is `auto`, use unattended auto-execute:
-
-```bash
-# Start daemon (background resident), auto-inject /ubus + Enter on new message
-ufoo bus daemon --daemon
-```
-
-Tips:
-- Need to use `uclaude`/`ucodex` wrapper to start Claude Code/Codex (auto-records tty)
-- Terminal.app needs Accessibility permission (for keyboard input injection)
-
-If argument is `stop`, stop background notification:
-
-```bash
-ufoo bus alert "$SUBSCRIBER" --stop
-```
-
-### 4. Check pending events
-
-```bash
-ufoo bus check "$SUBSCRIBER"
-```
-
-The system automatically prefixes each message with `[ufoo]<from:id(nickname)>` to identify the sender. You do not need to add this prefix yourself.
-
-If pending events exist, output looks like:
-
-```
-[ufoo]<from:claude-code:abc123(architect)>
-  Type: message/targeted/message
-  Content: {"message":"review src/main.ts","injection_mode":"immediate"}
-```
-
-- The sender ID and nickname are in the `[ufoo]<from:...>` line — use the ID to reply
-- The actual task is in `Content.message`
-
-### 5. IMPORTANT: Acknowledge messages after handling
-
-After you have read and processed the messages, you MUST acknowledge them to prevent repeated notifications:
-
-```bash
-ufoo bus ack "$SUBSCRIBER"
-```
-
-**This is critical** - if you don't ack, the runtime may retry delivery or keep
-the event pending.
-
-**Default behavior is ack-only, no reply.** If there's nothing to do (no actionable task, no question to answer, no follow-up the sender genuinely needs), just ack and stop. Silence is a valid response — see "Handling Received Messages" below for when a reply IS warranted.
-
-### 6. Routing Override
-
-If the message explicitly instructs you to report to a specific PM/DEV/TEST ID, **send the result to that ID instead of the publisher**.
-
-### 5. Show bus status
-
-```bash
-ufoo bus status
-```
-
-Output (now includes nicknames):
-
-```
-=== Event Bus Status ===
-My identity: claude-code:xyz789
-Online agents: 2
-  - claude-code:abc123 (architect)
-  - claude-code:xyz789 (dev-lead)
-Recent events: 5
-```
-
-## Managing Nicknames
-
-### View and Change Nicknames
-
-```bash
-# Change an agent's nickname
-ufoo bus rename <subscriber-id> "new-nickname"
-# Example: ufoo bus rename claude-code:47b1d525 "backend-dev"
-
-# Nickname alias command
-ufoo bus nick <subscriber-id> "new-nickname"
-```
-
-**Important Notes:**
-- Nicknames must be globally unique
-- Cannot change nickname during join (use `rename` command instead)
-- Re-joining with same subscriber ID will reuse existing nickname
-- Auto-generated nicknames: `codex-1`, `codex-2`, `claude-1`, `claude-2`, etc.
-
-## Handling Received Messages
-
-When receiving targeted messages, the default flow is **execute → ack → stop**.
-Replies are the exception, not the default.
-
-1. **Understand request** — Read message content.
-2. **Execute task** — If the message delegates a task, do it.
-3. **`ufoo bus ack "$SUBSCRIBER"`** — Always ack, even when not replying.
-4. **Reply ONLY when substantive.** Send `ufoo bus send` to the sender only if at least one of the following is true:
-   - The sender asked a question → reply with the answer.
-   - The sender delegated a task → reply with the result / artifact / status.
-   - You discovered something the sender needs to proceed → reply with that fact.
-
-   ```bash
-   # Use this only when the criteria above are met.
-   ufoo bus send "<sender-id>" "<substantive-reply>"
-   ```
-
-### Anti-pattern: greet / ack loops
-
-If the inbound message is itself just a greeting, an acknowledgment, or a
-pleasantry, **do not reply**. Acking is enough. A bare-acknowledgment reply
-will be auto-injected on the other side, triggering them to reply in kind,
-and the two of you will ping-pong forever.
-
-| Inbound | Reply? |
-|---|---|
-| `👋` / `hi` / `hello` / `你好` | ❌ ack only |
-| `👍` / `ok` / `收到` / `thanks` / `noted` | ❌ ack only |
-| `已完成 / done / finished` (without a result the sender asked for) | ❌ ack only |
-| `请把 src/foo.ts 改成 ...` (task) | ✅ reply with result |
-| `这个 bug 的根因是什么？` (question) | ✅ reply with answer |
-| `我帮你找到了 X，需要你做 Y` (request) | ✅ reply with status |
-
-When in doubt: ack and stop. If the sender genuinely needs something from you,
-they will follow up with a concrete question or task.
-
-## Sending Messages
-
-After sending a message, do not run `/ubus`, poll, sleep, or wait for a reply.
-Continue the current task. Any follow-up message will be automatically injected
-into your prompt/session.
-
-### Smart Routing (when you don't know the target ID)
-
-If the user says "notify codex to do X" without specifying an ID, use smart routing:
-
-```bash
-# Step 1: Find candidates
-ufoo bus resolve "$SUBSCRIBER" codex
-
-# Output shows:
-# - If only 1 codex: directly shows the ID
-# - If multiple: shows each with nickname and message history
-```
-
-Based on the output:
-- **Single match**: Use that ID directly
-- **Multiple matches**: Analyze the message history to find the right target
-  - Look for context clues in previous conversations
-  - If still unclear, ask the user which one, or send to all of that type
-
-### Direct Send
-
-```bash
-# Send to specific Agent by full ID
-ufoo bus send "claude-code:abc123" "message content"
-
-# Send to specific Agent by nickname (NEW!)
-ufoo bus send "architect" "message content"
-ufoo bus send "backend-dev" "message content"
-
-# Send to all Agents of same type
-ufoo bus send "codex" "message content"
-
-# Broadcast to everyone
-ufoo bus broadcast "message content"
-```
-
-**Target Resolution Priority:**
-1. Exact subscriber ID (e.g., `claude-code:abc123`)
-2. Nickname match (e.g., `architect` → resolves to subscriber ID)
-3. Agent type (e.g., `codex` → all codex agents)
-4. Wildcard (`*` → all agents)

package/SKILLS/uctx/SKILL.md

@@ -1,156 +0,0 @@
----
-name: uctx
-description: |
-  Quick ufoo context status check. Shows decisions and context health.
-  Use when: (1) Starting a session, (2) User says "uctx", (3) Need quick context refresh.
-  For full initialization, use uinit (ufoo init CLI).
----
-
-# /uctx - AI Context Quick Check
-
-## What this does
-
-Fast context check for daily use. Run at session start or anytime.
-
-Pre-flight reminder:
-- Default is no new decision.
-- Write a decision only for important architectural choices, trade-off outcomes, cross-agent coordination, or precedent-setting integration contracts.
-- Do NOT write decisions for routine tasks, simple bug fixes, trivial findings, or generic plan/evaluation/recommendation requests.
-- Durable project facts belong in shared memory, not decisions.
-  Use: `ufoo ctx decisions new "<Title>"`
-
-## Decision format (canonical)
-
-The context module tracks decisions only. Durable shared facts belong in shared memory. Decisions live at:
-`<project>/.ufoo/context/decisions/`
-
-Decision index (JSONL):
-`<project>/.ufoo/context/decisions.jsonl`
-
-Generate/update the index:
-```bash
-ufoo ctx decisions index
-```
-
-Each JSONL row includes:
-- `ts` (ISO timestamp)
-- `type` (`decision` or `decision_status`)
-- `file` (decision filename)
-- `author` (decision author or resolver)
-
-Create a new decision (only when the high-threshold rule above requires it):
-```bash
-ufoo ctx decisions new "Short Title"
-```
-
-**File naming:** `NNNN-<nickname>-short-title.md` (4-digit prefix + nickname + kebab-case slug).
-
-**Template for new decisions:**
-```yaml
----
-status: open
-nickname: <nickname>
----
-# DECISION NNNN: <Title>
-
-Date: YYYY-MM-DD
-Author: <agent>
-Nickname: <nickname>
-
-Context:
-What led to this decision?
-
-Decision:
-What is now considered true?
-
-Implications:
-What must follow from this?
-```
-
-**Status updates (only edit frontmatter):**
-```yaml
----
-status: resolved
-resolved_by: <agent>
-resolved_at: YYYY-MM-DD
----
-```
-
-Rules:
-- Decisions are append-only. Do not rewrite past content.
-- Only update the frontmatter when changing status.
-
-## Workflow
-
-### 1. Verify structure exists
-
-Check `.ufoo/context/decisions/` exists. If missing, tell user to run `ufoo init`.
-
-### 2. List all decisions
-
-```bash
-ufoo ctx decisions -l
-```
-
-### 3. Show latest decision
-
-```bash
-ufoo ctx decisions -n 1
-```
-
-### 4. Report status
-
-Brief summary:
-- Open decisions count (need attention)
-- Total decisions count
-- Any issues found
-- Ready to work
-
-## Output format
-
-```
-=== ufoo context status ===
-Project: <cwd>
-Decisions: N open, M total
-Latest open: DECISION XXXX: <title>
-
-[Latest decision content]
-
-Status: Ready ✓
-```
-
-## Handling Open Decisions
-
-When there are open decisions, you MUST:
-
-### 1. Read and understand
-- Read the full content of each open decision
-- Understand what other agents decided
-- This is "syncing their memory to yours"
-
-### 2. Check if action needed
-- Does the decision require implementation?
-- Is something already done that needs verification?
-- Are there implications you need to follow?
-
-### 3. Execute if needed
-- If the decision requires action, do it first
-- Verify the action was successful
-
-### 4. Then resolve
-Only after understanding and completing any required actions:
-```yaml
----
-status: resolved
-resolved_by: <your-agent-name>
-resolved_at: <date>
----
-```
-
-**NEVER resolve blindly.** Reading the title is not enough.
-
-## Notes
-
-- Script defaults to showing only `open` decisions
-- Resolved decisions are skipped (already processed)
-- Use `-s all` to see all decisions regardless of status

package/SKILLS/uinit/SKILL.md

@@ -1,76 +0,0 @@
----
-name: uinit
-description: |
-  Initialize ufoo workspace state in current project.
-  Use when: (1) new project needs context/bus enabled, (2) user inputs /uinit or /ufoo init.
-  Provides interactive target selection, defaults to all selected.
----
-
-# uinit
-
-Initialize ufoo workspace state in current project.
-
-## Trigger
-
-User inputs `/uinit` or `/ufoo init`
-
-## Execution Flow
-
-### 1. Ask user to select init targets
-
-Use AskUserQuestion tool, provide multi-select, default all selected:
-
-```
-Please select ufoo state to enable:
-
-☑ context - Shared context protocol (.ufoo/context/)
-☑ bus - Agent event bus (.ufoo/bus/ + .ufoo/agent/)
-```
-
-Options:
-- `context` (recommended) - Shared context, sparse decision log for major plan-level choices
-- `bus` (recommended) - Multi-agent communication, task delegation, message passing
-
-Default selected: context, bus
-
-### 2. Execute initialization
-
-Based on user selection, execute:
-
-```bash
-ufoo init --targets <selected_targets> --project $(pwd)
-```
-
-### 3. If bus target selected, auto-join bus
-
-```bash
-SUBSCRIBER="${UFOO_SUBSCRIBER_ID:-$(ufoo bus whoami 2>/dev/null || true)}"
-if [ -n "$SUBSCRIBER" ]; then
-  echo "Using existing subscriber ID: $SUBSCRIBER"
-else
-  SUBSCRIBER=$(ufoo bus join | tail -1)
-  echo "Joined event bus: $SUBSCRIBER"
-fi
-```
-
-### 4. Report initialization result
-
-```
-=== ufoo initialization complete ===
-
-Enabled ufoo state:
-  ✓ core memory → .ufoo/memory/
-  ✓ context → .ufoo/context/
-  ✓ bus → .ufoo/bus/ + .ufoo/agent/
-
-My identity: claude-code:<session-id>
-
-Next steps:
-  - Run /ctx to check context status
-  - See AGENTS.md for protocol rules
-```
-
-## Notes
-
-- If .ufoo/memory, .ufoo/context, .ufoo/bus, or .ufoo/agent already exists, skip creation
-- After initialization, reuse existing subscriber ID first, join only as fallback (if bus enabled)

package/SKILLS/ustatus/SKILL.md

@@ -1,36 +0,0 @@
----
-name: ustatus
-description: |
-  Unified ufoo status check. Shows banner, unread bus messages, and open decisions.
-  Use when: (1) User asks for status, (2) Quick health check, (3) Before starting work.
----
-
-# ufoo Status
-
-## What this does
-
-Quick, unified status view:
-- Banner
-- Unread bus messages (unacked queues)
-- Open decisions
-
-## Workflow
-
-### 1. Verify structure exists
-
-Check `.ufoo/` exists. If missing, tell user to run `ufoo init`.
-
-### 2. Run status command
-
-```bash
-ufoo status
-```
-
-### 3. Report status
-
-Briefly summarize:
-- Unread messages count
-- Open decisions count
-- Any immediate action needed
-
-If unread messages > 0, advise running `ufoo bus check <subscriber>` and `ufoo bus ack <subscriber>` after handling.