u-foo 3.0.13 → 3.0.15

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.