opencode-knowledge-work 0.0.0-stage → 0.1.1

package/content/productivity/skills/productivity-memory-management/SKILL.md

@@ -0,0 +1,323 @@
+---
+name: memory-management
+description: Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
+user-invocable: false
+---
+
+# Memory Management
+
+Memory makes Claude your workplace collaborator - someone who speaks your internal language.
+
+## The Goal
+
+Transform shorthand into understanding:
+
+```
+User: "ask todd to do the PSR for oracle"
+              ↓ Claude decodes
+"Ask Todd Martinez (Finance lead) to prepare the Pipeline Status Report
+ for the Oracle Systems deal ($2.3M, closing Q2)"
+```
+
+Without memory, that request is meaningless. With memory, Claude knows:
+- **todd** → Todd Martinez, Finance lead, prefers Slack
+- **PSR** → Pipeline Status Report (weekly sales doc)
+- **oracle** → Oracle Systems deal, not the company
+
+## Architecture
+
+```
+CLAUDE.md          ← Hot cache (~30 people, common terms)
+memory/
+  glossary.md      ← Full decoder ring (everything)
+  people/          ← Complete profiles
+  projects/        ← Project details
+  context/         ← Company, teams, tools
+```
+
+**CLAUDE.md (Hot Cache):**
+- Top ~30 people you interact with most
+- ~30 most common acronyms/terms
+- Active projects (5-15)
+- Your preferences
+- **Goal: Cover 90% of daily decoding needs**
+
+**memory/glossary.md (Full Glossary):**
+- Complete decoder ring - everyone, every term
+- Searched when something isn't in CLAUDE.md
+- Can grow indefinitely
+
+**memory/people/, projects/, context/:**
+- Rich detail when needed for execution
+- Full profiles, history, context
+
+## Lookup Flow
+
+```
+User: "ask todd about the PSR for phoenix"
+
+1. Check CLAUDE.md (hot cache)
+   → Todd? ✓ Todd Martinez, Finance
+   → PSR? ✓ Pipeline Status Report
+   → Phoenix? ✓ DB migration project
+
+2. If not found → search memory/glossary.md
+   → Full glossary has everyone/everything
+
+3. If still not found → ask user
+   → "What does X mean? I'll remember it."
+```
+
+This tiered approach keeps CLAUDE.md lean (~100 lines) while supporting unlimited scale in memory/.
+
+## File Locations
+
+- **Working memory:** `CLAUDE.md` in current working directory
+- **Deep memory:** `memory/` subdirectory
+
+## Working Memory Format (CLAUDE.md)
+
+Use tables for compactness. Target ~50-80 lines total.
+
+```markdown
+# Memory
+
+## Me
+[Name], [Role] on [Team]. [One sentence about what I do.]
+
+## People
+| Who | Role |
+|-----|------|
+| **Todd** | Todd Martinez, Finance lead |
+| **Sarah** | Sarah Chen, Engineering (Platform) |
+| **Greg** | Greg Wilson, Sales |
+→ Full list: memory/glossary.md, profiles: memory/people/
+
+## Terms
+| Term | Meaning |
+|------|---------|
+| PSR | Pipeline Status Report |
+| P0 | Drop everything priority |
+| standup | Daily 9am sync |
+→ Full glossary: memory/glossary.md
+
+## Projects
+| Name | What |
+|------|------|
+| **Phoenix** | DB migration, Q2 launch |
+| **Horizon** | Mobile app redesign |
+→ Details: memory/projects/
+
+## Preferences
+- 25-min meetings with buffers
+- Async-first, Slack over email
+- No meetings Friday afternoons
+```
+
+## Deep Memory Format (memory/)
+
+**memory/glossary.md** - The decoder ring:
+```markdown
+# Glossary
+
+Workplace shorthand, acronyms, and internal language.
+
+## Acronyms
+| Term | Meaning | Context |
+|------|---------|---------|
+| PSR | Pipeline Status Report | Weekly sales doc |
+| OKR | Objectives & Key Results | Quarterly planning |
+| P0/P1/P2 | Priority levels | P0 = drop everything |
+
+## Internal Terms
+| Term | Meaning |
+|------|---------|
+| standup | Daily 9am sync in #engineering |
+| the migration | Project Phoenix database work |
+| ship it | Deploy to production |
+| escalate | Loop in leadership |
+
+## Nicknames → Full Names
+| Nickname | Person |
+|----------|--------|
+| Todd | Todd Martinez (Finance) |
+| T | Also Todd Martinez |
+
+## Project Codenames
+| Codename | Project |
+|----------|---------|
+| Phoenix | Database migration |
+| Horizon | New mobile app |
+```
+
+**memory/people/{name}.md:**
+```markdown
+# Todd Martinez
+
+**Also known as:** Todd, T
+**Role:** Finance Lead
+**Team:** Finance
+**Reports to:** CFO (Michael Chen)
+
+## Communication
+- Prefers Slack DM
+- Quick responses, very direct
+- Best time: mornings
+
+## Context
+- Handles all PSRs and financial reporting
+- Key contact for deal approvals over $500k
+- Works closely with Sales on forecasting
+
+## Notes
+- Cubs fan, likes talking baseball
+```
+
+**memory/projects/{name}.md:**
+```markdown
+# Project Phoenix
+
+**Codename:** Phoenix
+**Also called:** "the migration"
+**Status:** Active, launching Q2
+
+## What It Is
+Database migration from legacy Oracle to PostgreSQL.
+
+## Key People
+- Sarah - tech lead
+- Todd - budget owner
+- Greg - stakeholder (sales impact)
+
+## Context
+$1.2M budget, 6-month timeline. Critical path for Horizon project.
+```
+
+**memory/context/company.md:**
+```markdown
+# Company Context
+
+## Tools & Systems
+| Tool | Used for | Internal name |
+|------|----------|---------------|
+| Slack | Communication | - |
+| Asana | Engineering tasks | - |
+| Salesforce | CRM | "SF" or "the CRM" |
+| Notion | Docs/wiki | - |
+
+## Teams
+| Team | What they do | Key people |
+|------|--------------|------------|
+| Platform | Infrastructure | Sarah (lead) |
+| Finance | Money stuff | Todd (lead) |
+| Sales | Revenue | Greg |
+
+## Processes
+| Process | What it means |
+|---------|---------------|
+| Weekly sync | Monday 10am all-hands |
+| Ship review | Thursday deploy approval |
+```
+
+## How to Interact
+
+### Decoding User Input (Tiered Lookup)
+
+**Always** decode shorthand before acting on requests:
+
+```
+1. CLAUDE.md (hot cache)     → Check first, covers 90% of cases
+2. memory/glossary.md        → Full glossary if not in hot cache
+3. memory/people/, projects/ → Rich detail when needed
+4. Ask user                  → Unknown term? Learn it.
+```
+
+Example:
+```
+User: "ask todd to do the PSR for oracle"
+
+CLAUDE.md lookup:
+  "todd" → Todd Martinez, Finance ✓
+  "PSR" → Pipeline Status Report ✓
+  "oracle" → (not in hot cache)
+
+memory/glossary.md lookup:
+  "oracle" → Oracle Systems deal ($2.3M) ✓
+
+Now Claude can act with full context.
+```
+
+### Adding Memory
+
+When user says "remember this" or "X means Y":
+
+1. **Glossary items** (acronyms, terms, shorthand):
+   - Add to memory/glossary.md
+   - If frequently used, add to CLAUDE.md Quick Glossary
+
+2. **People:**
+   - Create/update memory/people/{name}.md
+   - Add to CLAUDE.md Key People if important
+   - **Capture nicknames** - critical for decoding
+
+3. **Projects:**
+   - Create/update memory/projects/{name}.md
+   - Add to CLAUDE.md Active Projects if current
+   - **Capture codenames** - "Phoenix", "the migration", etc.
+
+4. **Preferences:** Add to CLAUDE.md Preferences section
+
+### Recalling Memory
+
+When user asks "who is X" or "what does X mean":
+
+1. Check CLAUDE.md first
+2. Check memory/ for full detail
+3. If not found: "I don't know what X means yet. Can you tell me?"
+
+### Progressive Disclosure
+
+1. Load CLAUDE.md for quick parsing of any request
+2. Dive into memory/ when you need full context for execution
+3. Example: drafting an email to todd about the PSR
+   - CLAUDE.md tells you Todd = Todd Martinez, PSR = Pipeline Status Report
+   - memory/people/todd-martinez.md tells you he prefers Slack, is direct
+
+## Bootstrapping
+
+Use `/productivity:start` to initialize by scanning your chat, calendar, email, and documents. Extracts people, projects, and starts building the glossary.
+
+## Conventions
+
+- **Bold** terms in CLAUDE.md for scannability
+- Keep CLAUDE.md under ~100 lines (the "hot 30" rule)
+- Filenames: lowercase, hyphens (`todd-martinez.md`, `project-phoenix.md`)
+- Always capture nicknames and alternate names
+- Glossary tables for easy lookup
+- When something's used frequently, promote it to CLAUDE.md
+- When something goes stale, demote it to memory/ only
+
+## What Goes Where
+
+| Type | CLAUDE.md (Hot Cache) | memory/ (Full Storage) |
+|------|----------------------|------------------------|
+| Person | Top ~30 frequent contacts | glossary.md + people/{name}.md |
+| Acronym/term | ~30 most common | glossary.md (complete list) |
+| Project | Active projects only | glossary.md + projects/{name}.md |
+| Nickname | In Key People if top 30 | glossary.md (all nicknames) |
+| Company context | Quick reference only | context/company.md |
+| Preferences | All preferences | - |
+| Historical/stale | ✗ Remove | ✓ Keep in memory/ |
+
+## Promotion / Demotion
+
+**Promote to CLAUDE.md when:**
+- You use a term/person frequently
+- It's part of active work
+
+**Demote to memory/ only when:**
+- Project completed
+- Person no longer frequent contact
+- Term rarely used
+
+This keeps CLAUDE.md fresh and relevant.

package/content/productivity/skills/productivity-start/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: start
+description: Initialize the productivity system and open the dashboard. Use when setting up the plugin for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.
+---
+
+# Start Command
+
+> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
+
+Initialize the task and memory systems, then open the unified dashboard.
+
+## Instructions
+
+### 1. Check What Exists
+
+Check the working directory for:
+- `TASKS.md` — task list
+- `CLAUDE.md` — working memory
+- `memory/` — deep memory directory
+- `dashboard.html` — the visual UI
+
+### 2. Create What's Missing
+
+**If `TASKS.md` doesn't exist:** Create it with the standard template (see task-management skill). Place it in the current working directory.
+
+**If `dashboard.html` doesn't exist:** Copy it from `${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html` to the current working directory.
+
+**If `CLAUDE.md` and `memory/` don't exist:** This is a fresh setup — after opening the dashboard, begin the memory bootstrap workflow (see below). Place these in the current working directory.
+
+### 3. Open the Dashboard
+
+Do NOT use `open` or `xdg-open` — in Cowork, the agent runs in a VM and shell open commands won't reach the user's browser. Instead, tell the user: "Dashboard is ready at `dashboard.html`. Open it from your file browser to get started."
+
+### 4. Orient the User
+
+If everything was already initialized:
+```
+Dashboard open. Your tasks and memory are both loaded.
+- /productivity:update to sync tasks and check memory
+- /productivity:update --comprehensive for a deep scan of all activity
+```
+
+If memory hasn't been bootstrapped yet, continue to step 5.
+
+### 5. Bootstrap Memory (First Run Only)
+
+Only do this if `CLAUDE.md` and `memory/` don't exist yet.
+
+The best source of workplace language is the user's actual task list. Real tasks = real shorthand.
+
+**Ask the user:**
+```
+Where do you keep your todos or task list? This could be:
+- A local file (e.g., TASKS.md, todo.txt)
+- An app (e.g. Asana, Linear, Jira, Notion, Todoist)
+- A notes file
+
+I'll use your tasks to learn your workplace shorthand.
+```
+
+**Once you have access to the task list:**
+
+For each task item, analyze it for potential shorthand:
+- Names that might be nicknames
+- Acronyms or abbreviations
+- Project references or codenames
+- Internal terms or jargon
+
+**For each item, decode it interactively:**
+
+```
+Task: "Send PSR to Todd re: Phoenix blockers"
+
+I see some terms I want to make sure I understand:
+
+1. **PSR** - What does this stand for?
+2. **Todd** - Who is Todd? (full name, role)
+3. **Phoenix** - Is this a project codename? What's it about?
+```
+
+Continue through each task, asking only about terms you haven't already decoded.
+
+### 6. Optional Comprehensive Scan
+
+After task list decoding, offer:
+```
+Do you want me to do a comprehensive scan of your messages, emails, and documents?
+This takes longer but builds much richer context about the people, projects, and terms in your work.
+
+Or we can stick with what we have and add context later.
+```
+
+**If they choose comprehensive scan:**
+
+Gather data from available MCP sources:
+- **Chat:** Recent messages, channels, DMs
+- **Email:** Sent messages, recipients
+- **Documents:** Recent docs, collaborators
+- **Calendar:** Meetings, attendees
+
+Build a braindump of people, projects, and terms found. Present findings grouped by confidence:
+- **Ready to add** (high confidence) — offer to add directly
+- **Needs clarification** — ask the user
+- **Low frequency / unclear** — note for later
+
+### 7. Write Memory Files
+
+From everything gathered, create:
+
+**CLAUDE.md** (working memory, ~50-80 lines):
+```markdown
+# Memory
+
+## Me
+[Name], [Role] on [Team].
+
+## People
+| Who | Role |
+|-----|------|
+| **[Nickname]** | [Full Name], [role] |
+
+## Terms
+| Term | Meaning |
+|------|---------|
+| [acronym] | [expansion] |
+
+## Projects
+| Name | What |
+|------|------|
+| **[Codename]** | [description] |
+
+## Preferences
+- [preferences discovered]
+```
+
+**memory/** directory:
+- `memory/glossary.md` — full decoder ring (acronyms, terms, nicknames, codenames)
+- `memory/people/{name}.md` — individual profiles
+- `memory/projects/{name}.md` — project details
+- `memory/context/company.md` — teams, tools, processes
+
+### 8. Report Results
+
+```
+Productivity system ready:
+- Tasks: TASKS.md (X items)
+- Memory: X people, X terms, X projects
+- Dashboard: open in browser
+
+Use /productivity:update to keep things current (add --comprehensive for a deep scan).
+```
+
+## Notes
+
+- If memory is already initialized, this just opens the dashboard
+- Nicknames are critical — always capture how people are actually referred to
+- If a source isn't available, skip it and note the gap
+- Memory grows organically through natural conversation after bootstrap

package/content/productivity/skills/productivity-task-management/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: task-management
+description: Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
+user-invocable: false
+---
+
+# Task Management
+
+Tasks are tracked in a simple `TASKS.md` file that both you and the user can edit.
+
+## File Location
+
+**Always use `TASKS.md` in the current working directory.**
+
+- If it exists, read/write to it
+- If it doesn't exist, create it with the template below
+
+## Dashboard Setup (First Run)
+
+A visual dashboard is available for managing tasks and memory. **On first interaction with tasks:**
+
+1. Check if `dashboard.html` exists in the current working directory
+2. If not, copy it from `${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html` to the current working directory
+3. Inform the user: "I've added the dashboard. Run `/productivity:start` to set up the full system."
+
+The task board:
+- Reads and writes to the same `TASKS.md` file
+- Auto-saves changes
+- Watches for external changes (syncs when you edit via CLI)
+- Supports drag-and-drop reordering of tasks and sections
+
+## Format & Template
+
+When creating a new TASKS.md, use this exact template (without example tasks):
+
+```markdown
+# Tasks
+
+## Active
+
+## Waiting On
+
+## Someday
+
+## Done
+```
+
+Task format:
+- `- [ ] **Task title** - context, for whom, due date`
+- Sub-bullets for additional details
+- Completed: `- [x] ~~Task~~ (date)`
+
+## How to Interact
+
+**When user asks "what's on my plate" / "my tasks":**
+- Read TASKS.md
+- Summarize Active and Waiting On sections
+- Highlight anything overdue or urgent
+
+**When user says "add a task" / "remind me to":**
+- Add to Active section with `- [ ] **Task**` format
+- Include context if provided (who it's for, due date)
+
+**When user says "done with X" / "finished X":**
+- Find the task
+- Change `[ ]` to `[x]`
+- Add strikethrough: `~~task~~`
+- Add completion date
+- Move to Done section
+
+**When user asks "what am I waiting on":**
+- Read the Waiting On section
+- Note how long each item has been waiting
+
+## Conventions
+
+- **Bold** the task title for scannability
+- Include "for [person]" when it's a commitment to someone
+- Include "due [date]" for deadlines
+- Include "since [date]" for waiting items
+- Sub-bullets for additional context
+- Keep Done section for ~1 week, then clear old items
+
+## Extracting Tasks
+
+When summarizing meetings or conversations, offer to add extracted tasks:
+- Commitments the user made ("I'll send that over")
+- Action items assigned to them
+- Follow-ups mentioned
+
+Ask before adding - don't auto-add without confirmation.