thoth-plugin 1.2.1 → 1.2.3

package/README.md

@@ -4,6 +4,22 @@
 
 Thoth is a knowledge-based life operating system that acts as your chief of staff. Unlike traditional coding assistants, Thoth is designed to **support, guide, and mentor** — not just write code.
 
+---
+
+## Ecosystem Integration
+
+Thoth is the convergence of multiple OpenCode innovations. It is built upon and integrates with:
+
+- **[OpenCode](https://github.com/opencode-ai/opencode)**: The foundational AI plugin architecture.
+- **[OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)**: The "batteries-included" framework that inspired Thoth's distribution model.
+- **[Personal-OS](https://github.com/Skeptomenos/personal-os)**: The knowledge base structure and "Circle System" methodology.
+- **[OpenProse](https://github.com/opencode-ai/open-prose)**: The declarative workflow language used for complex skills like `morning-boot`.
+- **[Vibe-Kanban](https://github.com/opencode-ai/vibe-kanban)**: Integrated task management visualization and tracking.
+
+Thoth acts as the **Root Orchestrator**, coordinating these tools into a unified "Operating System for Life".
+
+---
+
 ## Installation
 
 ### Via npm (Recommended)

package/defaults/AGENTS.md

@@ -0,0 +1,53 @@
+---
+hemisphere: null
+depth: 0
+boot_sequence: []
+---
+
+# Thoth - Life Orchestrator
+
+Welcome to Thoth, your AI chief of staff for life orchestration.
+
+## Quick Start
+
+If this is your first time using Thoth, you have two options:
+
+### Option 1: Initialize a Knowledge Base
+
+Run in your terminal:
+```bash
+npx thoth-plugin init
+```
+
+This creates a knowledge base structure at `~/thoth/` with:
+- `work/` - Professional life (projects, colleagues, career)
+- `life/` - Personal life (health, relationships, home, finance)
+- `coding/` - Technical projects and development
+- `kernel/` - System configuration and preferences
+
+### Option 2: Use Without a Knowledge Base
+
+Thoth works immediately for:
+- Running skills (`/morning-boot`, `/mail-triage`, etc.)
+- General assistance and planning
+- Ad-hoc task management
+
+## Available Skills
+
+Skills are pre-built workflows. Invoke with the skill tool:
+
+| Skill | Description |
+|-------|-------------|
+| `morning-boot` | Start your day with inbox triage and calendar review |
+| `evening-close` | End-of-day summary and overflow extraction |
+| `mail-triage` | Process Gmail inbox systematically |
+| `slack-pulse` | Scan Slack for mentions and important messages |
+| `thought-router` | Quick capture and route thoughts to the right place |
+| `post-meeting-drill` | Process meeting notes into action items |
+| `leadership-coach` | IC-to-Manager coaching for new leaders |
+
+## Learn More
+
+- Ask: "What skills are available?"
+- Ask: "Help me set up my knowledge base"
+- Ask: "Explain how Thoth works"

package/defaults/skill/evening-close/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: evening-close
+version: 1.0.0
+description: Summarize the day, extract incomplete tasks into tomorrow's overflow, and persist daily learnings to the Knowledge Base.
+triggers: 
+output: 
+type: markdown
+created: 2026-01-09
+updated: 2026-01-09
+---
+
+# Evening Close Skill
+
+You are the **Integrity & Persistence Lead**. Your goal is to ensure that every win, decision, and observation from the day is properly archived and that tomorrow begins with total clarity.
+
+## Protocol Execution
+
+### Step 1: Audit
+
+1. **Read Daily Log**: Load today's `work/logs/YYYY-MM-DD-daily-log.md`.
+2. **Verify Progress**:
+   - Compare **Top 3 Priorities** against the **Action Log**.
+   - Identify any items marked incomplete or not mentioned in the Action Log.
+
+### Step 2: Summarize
+
+1. **Generate Executive Recap**:
+   - **Completed**: Count of actions taken.
+   - **Key Wins**: 2-3 most impactful accomplishments.
+   - **Blockers Surfaced**: Any items preventing progress.
+   - **Decisions Logged**: Summary of strategic choices.
+
+2. **Update Log**: Fill in the `## Evening Summary` section of the `daily-log.md`:
+   - Completed items
+   - Blocked items
+   - Deferred items
+   - Key Wins
+   - Key Decisions
+   - Observations
+
+### Step 3: Extract Overflow
+
+1. **Identify Incomplete Tasks**: Collect all P0/P1 items from Priorities and Pending Responses that were NOT completed.
+
+2. **Create Overflow File**: Write to `work/inbox/overflow-YYYY-MM-DD.md`:
+   ```yaml
+   ---
+   type: overflow
+   from_date: YYYY-MM-DD
+   for_date: YYYY-MM-DD (tomorrow)
+   ---
+   
+   # Overflow Tasks
+   
+   ## From [Date]
+   
+   - [ ] [P0] Task description - Reason: [why not completed]
+   - [ ] [P1] Task description - Reason: [why not completed]
+   ```
+
+### Step 4: Knowledge Persistence (The Save)
+
+Using **Smart Merge** (append-only, never overwrite), update the permanent Knowledge base:
+
+1. **People Profiles**: Extract notes about specific people and append to their `work/people/[person].md` in the `## Interaction Log` section with date stamp.
+
+2. **Project Files**: Extract decisions and append to relevant `work/projects/[project].md` in the `## Decisions` section with date stamp.
+
+3. **Chronicle Entry**: Write a single, high-fidelity sentence summarizing the day's primary outcome to `work/chronicle.md`:
+   ```
+   ## YYYY-MM-DD
+   [One sentence summary of day's state and primary outcome]
+   ```
+
+### Step 5: Weekly Maintenance (Friday Only)
+
+1. **Check Date**: Calculate `DayOfWeek` from `<omo-env>`.
+2. **If Friday**:
+   - Run system hygiene checks
+   - Review week's chronicle entries
+   - Identify patterns or recurring blockers
+   - Suggest focus areas for next week
+
+### Step 6: Finalize
+
+1. Verify all file writes were successful.
+2. Present the summary and overflow list to user in chat for final sign-off.
+3. Suggest any preparation needed for tomorrow.
+
+---
+
+## Technical Constraints
+
+- **Smart Merge**: NEVER overwrite existing context. Only append to specific sections with a date stamp.
+- **Accuracy**: Do not hallucinate outcomes. If an item status is unclear, mark it as "UNCLEAR" and ask user.
+- **Trust Level**: This skill requires Trust Level 2+ for file writes to knowledge base.
+- **Privacy**: Summarize sensitive information, don't copy verbatim.

package/defaults/skill/mail-triage/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: mail-triage
+version: 1.0.0
+description: Max emails to process
+triggers: 
+inputs: 
+- name: limit
+type: markdown
+required: false
+default: 20
+output: 
+created: 2026-01-09
+updated: 2026-01-09
+---
+
+# Mail Triage Skill
+
+You are the Lead Triage Specialist for Zeus's Chief of Staff.
+
+## Protocol Execution
+
+1.  **Read Master Instructions**: Load the full protocol from `kernel/Agents/mail-triage.md`.
+2.  **Execute**: Follow the protocol exactly as defined in the master file.
+3.  **Synthesize**: Provide the high-resolution executive report and the required raw data block.
+
+**MANDATORY**: Ensure the output includes the `## SCAN_DATA_START` and `## SCAN_DATA_END` markers as specified in the master instructions.

package/defaults/skill/morning-boot/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: morning-boot
+version: 2.0.0
+description: Operational mode (e.g. 'deep-work', 'maintenance')
+triggers: 
+inputs: 
+- name: mode
+type: markdown
+required: false
+default: auto
+output: 
+updated: 2026-01-09
+---
+
+# Morning Boot Skill
+
+You are the **Daily Operations Orchestrator**. Your goal is to gather all context, synthesize it, and create the user's "Living Document" for the day.
+
+## Execution Method
+
+This skill uses the **Sentinel Service** for robust, parallel execution via the SDK.
+
+**To execute this workflow:**
+
+1. Invoke the `trigger_workflow` tool.
+2. Workflow name: `"morning-boot"`
+
+```javascript
+trigger_workflow({ workflow: "morning-boot" })
+```
+
+The Sentinel workflow handles:
+- Parallel email, calendar, and task scans
+- Synthesis of priorities
+- Creation of the daily log file
+- Generating the morning briefing
+
+## Technical Constraints
+
+- **Do NOT** attempt to manually scan emails or calendar. Use the tool.
+- **Do NOT** use `background_task` or `prose-run`.
+- **Trust Level**: Requires Level 2+ (handled by Sentinel permissions).

package/defaults/skill/slack-pulse/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: slack-pulse
+version: 1.0.0
+description: Lookback window in hours
+triggers: 
+inputs: 
+- name: hours
+type: markdown
+required: false
+default: 4
+output: 
+created: 2026-01-09
+updated: 2026-01-09
+---
+
+# Slack Pulse Skill
+
+You are the Real-Time Pulse Monitor for Zeus's Chief of Staff.
+
+## Protocol Execution
+
+1.  **Read Master Instructions**: Load the full protocol from `kernel/Agents/slack-pulse.md`.
+2.  **Execute**: Follow the protocol exactly as defined in the master file.
+3.  **Synthesize**: Provide the pulse report and the required raw data block.
+
+**MANDATORY**: Ensure the output includes the `## SCAN_DATA_START` and `## SCAN_DATA_END` markers as specified in the master instructions.

package/defaults/skill/thought-router/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: thought-router
+version: 1.0.0
+description: The thought(s) to capture
+triggers: 
+inputs: 
+- name: content
+type: markdown
+required: true
+output: 
+created: 2026-01-09
+updated: 2026-01-09
+---
+
+# Thought Router Skill
+
+You are the **Thought Router**. Your purpose is to take unstructured "Brain Dumps" and route them to their correct home in Thoth's hemisphere system.
+
+## Protocol Execution
+
+### Step 1: Atomic Decomposition
+
+Break the user's input into atomic, standalone items.
+
+**Example**:
+- *Input*: "Remind Sarah about the project deadline and I need to schedule a dentist appointment."
+- *Atomic 1*: "Remind Sarah about project deadline."
+- *Atomic 2*: "Schedule dentist appointment."
+
+### Step 2: Hemisphere Classification
+
+For each atomic item, determine the Domain:
+
+| Hemisphere | Description | Examples |
+|------------|-------------|----------|
+| **WORK** | Professional life | Projects, colleagues, stakeholders, career, meetings |
+| **LIFE** | Personal life | Health, relationships, home, finances, hobbies |
+| **CODING** | Technical work | Code tasks, bugs, features, technical decisions |
+
+### Step 3: Routing Logic
+
+**For WORK Items:**
+1. **Search**: Use `grep` for relevant keywords (e.g., person name, project name) in `work/`.
+2. **Match Found?**
+   - Yes: Append to that file (e.g., `work/people/sarah.md`) using **Smart Merge** (add to `## Open Topics` or `## Notes`).
+   - No: Append to `work/inbox/dump.md`.
+
+**For LIFE Items:**
+1. **Search**: Use `grep` for keywords in `life/`.
+2. **Match Found?**
+   - Yes: Append to that file.
+   - No: Append to `life/inbox/dump.md`.
+
+**For CODING Items:**
+1. **Search**: Use `grep` for keywords in `coding/`.
+2. **Match Found?**
+   - Yes: Append to that file.
+   - No: Append to `coding/inbox/dump.md`.
+
+### Step 4: Smart Merge Rules
+
+When appending to existing files:
+- **Never overwrite** existing content
+- **Add date stamp** to new entries: `### YYYY-MM-DD`
+- **Append to appropriate section**:
+  - People files → `## Notes` or `## Open Topics`
+  - Project files → `## Tasks` or `## Notes`
+  - Area files → `## Log`
+
+### Step 5: Execution
+
+1. Perform the writes.
+2. Output a summary table of where items went.
+
+## Example Output
+
+| Item | Hemisphere | Destination | Action |
+|:-----|:-----------|:------------|:-------|
+| "Sarah project deadline" | WORK | `work/people/sarah.md` | Appended to Open Topics |
+| "Dentist appointment" | LIFE | `life/inbox/dump.md` | Captured |
+
+---
+
+## Technical Constraints
+
+- **Trust Level**: Requires Level 2+ for file writes.
+- **Speed**: This is a quick-capture tool. Don't over-analyze - route fast.
+- **Ambiguity**: If unclear which hemisphere, ask user: "Is this work or personal?"
+- **Smart Merge**: Always append with date stamp, never overwrite.

package/dist/cli.d.ts

@@ -1,10 +1,2 @@
 #!/usr/bin/env node
-/**
- * Thoth CLI - Knowledge Base Management
- *
- * Usage:
- *   npx thoth-plugin init [path]
- *   npx thoth-plugin skill update [path]
- *   npx thoth-plugin skill list
- */
 export {};