claude-code-swarm 0.3.6 → 0.3.8

package/references/opentasks/package.json

@@ -1,81 +0,0 @@
-{
-  "name": "opentasks",
-  "version": "0.0.5",
-  "description": "Universal task graph data structure",
-  "type": "module",
-  "main": "./dist/index.js",
-  "module": "./dist/index.js",
-  "types": "./dist/index.d.ts",
-  "bin": {
-    "opentasks": "./dist/cli.js"
-  },
-  "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "import": "./dist/index.js"
-    }
-  },
-  "files": [
-    "dist"
-  ],
-  "scripts": {
-    "build": "tsc",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "test:slow": "RUN_SLOW_TESTS=1 vitest run",
-    "test:slow:watch": "RUN_SLOW_TESTS=1 vitest",
-    "test:e2e": "RUN_FULL_AGENT_TESTS=1 vitest run --config vitest.e2e.config.ts",
-    "test:all": "npm run test && npm run test:slow && npm run test:e2e",
-    "prepublishOnly": "npm run build",
-    "version:patch": "npm version patch && git push && git push --tags",
-    "version:minor": "npm version minor && git push && git push --tags",
-    "version:major": "npm version major && git push && git push --tags",
-    "publish:npm": "npm run build && npm publish",
-    "lint": "eslint src/",
-    "lint:fix": "eslint src/ --fix",
-    "format": "prettier --write \"src/**/*.{ts,js,json}\"",
-    "format:check": "prettier --check \"src/**/*.{ts,js,json}\"",
-    "prepare": "husky"
-  },
-  "keywords": [
-    "tasks",
-    "todo",
-    "task-management"
-  ],
-  "author": "Alex Ngai",
-  "license": "MIT",
-  "devDependencies": {
-    "@beads/bd": "^0.49.1",
-    "@eslint/js": "^9.39.2",
-    "@types/better-sqlite3": "^7.6.13",
-    "@types/node": "^25.0.10",
-    "@types/proper-lockfile": "^4.1.4",
-    "acp-factory": "^0.1.12",
-    "eslint": "^9.39.2",
-    "eslint-config-prettier": "^10.1.8",
-    "husky": "^9.1.7",
-    "lint-staged": "^15.5.2",
-    "prettier": "^3.8.1",
-    "typescript": "^5.3.0",
-    "typescript-eslint": "^8.55.0",
-    "vitest": "^4.0.18"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/alexngai/opentasks.git"
-  },
-  "dependencies": {
-    "agent-session-parser": "^0.1.0",
-    "better-sqlite3": "^12.6.2",
-    "chokidar": "^5.0.0",
-    "graphology": "^0.26.0",
-    "graphology-shortest-path": "^2.1.0",
-    "graphology-traversal": "^0.3.1",
-    "proper-lockfile": "^4.1.2",
-    "sessionlog": "^0.0.5",
-    "zod": "^4.3.6"
-  }
-}

package/references/opentasks/skills/opentasks/SKILL.md

@@ -1,139 +0,0 @@
----
-name: opentasks
-description: Use when managing work items, linking external data (Slack, docs, URLs) to tasks, querying task dependencies or blockers, leaving cross-system feedback on specs or issues, or coordinating work across multiple task systems. Use when the agent has access to the `opentasks` CLI.
-user-invocable: false
----
-
-# OpenTasks
-
-OpenTasks is a graph connector that adds a relationship layer across task systems. It does not replace those systems — it provides cross-system edges, feedback, and dependency tracking.
-
-## CLI Commands
-
-All operations go through the `opentasks` CLI, which talks to the daemon over IPC.
-
-### Link — create or remove edges
-
-```bash
-opentasks link --from t-x7k9 --to c-a2b3 --type implements
-opentasks link --from t-x7k9 --to t-m4n5 --type blocks
-opentasks link --from t-x7k9 --to e-k7m2 --type references --metadata '{"context":"bug report"}'
-opentasks link --from t-aaa --to t-bbb --type blocks --remove
-```
-
-Returns `{ success, edgeId? }`. Idempotent. `blocks` edges are cycle-checked.
-
-### Query — search nodes, edges, blockers, ready work
-
-```bash
-opentasks query '{"ready": {}}'
-opentasks query '{"blockers": {"nodeId": "t-r8s9", "activeOnly": true}}'
-opentasks query '{"blocking": {"nodeId": "t-x7k9", "transitive": true}}'
-opentasks query '{"edges": {"from_id": "t-x7k9", "type": "references"}}'
-opentasks query '{"tasks": {"specId": "c-a2b3"}}'
-opentasks query '{"feedback": {"nodeId": "c-a2b3", "resolved": false}}'
-opentasks query '{"unresolvedFeedback": {}}'
-```
-
-Exactly one query key per call. Returns `{ items, total?, hasMore }`.
-
-| Key | Purpose |
-|-----|---------|
-| `nodes` | Filter nodes by type, status, tags, search |
-| `edges` | Filter edges by from_id, to_id, type |
-| `ready` | Unblocked open tasks (tags?, priority?, assignee?) |
-| `blockers` | What blocks a node (transitive?, activeOnly?) |
-| `blocking` | What a node blocks (transitive?) |
-| `feedback` | Feedback on a node (type?, resolved?) |
-| `unresolvedFeedback` | All unresolved feedback (targetId?) |
-| `tasks` | Tasks implementing a context (specId) |
-| `specs` | Specs a task implements (issueId) |
-
-### Annotate — feedback lifecycle
-
-```bash
-# Create feedback
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"Implemented OAuth.","type":"comment"}}'
-
-# With source issue link
-opentasks annotate '{"targetId":"c-a2b3","fromId":"t-x7k9","create":{"content":"Done.","type":"comment"}}'
-
-# Anchored suggestion
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"Add rate limiting","type":"suggestion","anchor":{"line":15}}}'
-
-# Resolve / dismiss / reopen
-opentasks annotate '{"targetId":"c-a2b3","resolve":"f-t1u2"}'
-opentasks annotate '{"targetId":"c-a2b3","dismiss":"f-t1u2"}'
-opentasks annotate '{"targetId":"c-a2b3","reopen":"f-t1u2"}'
-```
-
-### Create — add nodes
-
-```bash
-opentasks create --type issue --title "Fix SSO redirect" --status open --tags auth,bug --priority 1
-opentasks create --type spec --title "OAuth2 for API" --status active --content "## Requirements\n..."
-opentasks create --type external --title "Slack: SSO bug" --uri "slack://C04ABCD/p123" --source slack --metadata '{"author":"alex"}'
-```
-
-### Get / Update / Delete
-
-```bash
-opentasks get t-x7k9
-opentasks update t-x7k9 --status closed
-opentasks update t-x7k9 --title "New title" --metadata '{"key":"val"}'
-opentasks delete t-x7k9
-opentasks delete t-x7k9 --hard
-```
-
-## Node Types
-
-| Type | Prefix | Required | Purpose |
-|------|--------|----------|---------|
-| `spec` | `s-` | title | Requirements, intent, context |
-| `issue` | `i-` | title, status | Actionable work items |
-| `feedback` | `f-` | title, target_id, feedback_type | Comments, suggestions, requests |
-| `external` | `e-` | title, uri, source | References to external systems |
-
-All nodes support optional: `content`, `priority` (0-4), `tags[]`, `parent_id`, `metadata`.
-
-## Edge Types
-
-| Type | Semantics | Cycle-checked |
-|------|-----------|---------------|
-| `blocks` | from must complete before to can start | Yes |
-| `implements` | task implements context | No |
-| `references` | general reference | No |
-| `related` | loose association | No |
-| `child-of` | hierarchical containment | No |
-| `parent-of` | inverse of child-of | No |
-| `depends-on` | soft dependency (informational, not used by `ready`) | No |
-| `discovered-from` | found while working on | No |
-| `duplicates` | from is duplicate of to | No |
-| `supersedes` | from replaces to | No |
-
-Edge types are extensible via string.
-
-## URI Conventions
-
-Nodes across systems are identified by URIs:
-
-```
-native://c-a2b3                    # OpenTasks native node
-beads://./bd-x7k9                  # Beads issue
-taskmaster://./auth-prd            # Taskmaster spec
-claude://current/t-abc             # Claude task
-slack://C04ABCD/p1234567890        # Slack message (custom)
-github://owner/repo/pull/42        # GitHub PR (custom)
-```
-
-The `uri` field on ExternalNodes is freeform. Use consistent schemes for deduplication.
-
-## Specialized Workflows
-
-**Linking external data** (Slack messages, docs, URLs): See [linking-external-data.md](linking-external-data.md)
-
-**Spec to implementation** (create spec, break into issues, track to completion): See [spec-to-implementation.md](spec-to-implementation.md)
-
-**Feedback and review** (cross-system feedback, suggestion lifecycle): See [feedback-and-review.md](feedback-and-review.md)
-
-**Dependency management** (blockers, ready queries, work loops): See [dependency-management.md](dependency-management.md)

package/references/opentasks/skills/opentasks/dependency-management.md

@@ -1,119 +0,0 @@
-# Dependency Management
-
-Set up dependency chains, query what's blocked and ready, manage work ordering.
-
-## blocks vs depends-on
-
-| Edge | Used by `ready` query | Cycle-checked | Use when |
-|------|----------------------|---------------|----------|
-| `blocks` | Yes | Yes | Work genuinely can't start until blocker closes |
-| `depends-on` | No | No | "Nice to have first" but not strictly required |
-
-## Setting Up Dependencies
-
-### Linear chain: A → B → C → D
-
-```bash
-opentasks link --from t-aaa --to t-bbb --type blocks
-opentasks link --from t-bbb --to t-ccc --type blocks
-opentasks link --from t-ccc --to t-ddd --type blocks
-```
-
-### Diamond: A blocks B+C, both block D
-
-```bash
-opentasks link --from t-aaa --to t-bbb --type blocks
-opentasks link --from t-aaa --to t-ccc --type blocks
-opentasks link --from t-bbb --to t-ddd --type blocks
-opentasks link --from t-ccc --to t-ddd --type blocks
-```
-
-B and C can run in parallel once A closes. D waits for both.
-
-### Cycle detection
-
-Creating a `blocks` edge that would form a cycle returns an error:
-
-```bash
-# Given: A blocks B, B blocks C
-opentasks link --from t-ccc --to t-aaa --type blocks
-# → { success: false, error: "Would create circular dependency" }
-```
-
-### Removing dependencies
-
-```bash
-opentasks link --from t-aaa --to t-bbb --type blocks --remove
-```
-
-## Querying
-
-### What blocks a node?
-
-```bash
-# Direct blockers
-opentasks query '{"blockers": {"nodeId": "t-ddd"}}'
-
-# Full chain (transitive)
-opentasks query '{"blockers": {"nodeId": "t-ddd", "transitive": true}}'
-
-# Only active (non-closed, non-archived)
-opentasks query '{"blockers": {"nodeId": "t-ddd", "activeOnly": true}}'
-```
-
-### What does a node block?
-
-```bash
-opentasks query '{"blocking": {"nodeId": "t-aaa", "transitive": true}}'
-```
-
-### What's ready to work on?
-
-Returns open tasks with zero active blockers.
-
-```bash
-# All ready work
-opentasks query '{"ready": {}}'
-
-# Filtered
-opentasks query '{"ready": {"tags": ["auth"], "priority": {"min": 0, "max": 2}, "limit": 5}}'
-```
-
-## Agent Work Loop
-
-```
-loop:
-  1. opentasks query '{"ready": {"limit": 1}}'       → pick highest-priority unblocked issue
-  2. If empty, stop.
-  3. opentasks update t-x7k9 --status in_progress
-  4. Do the work.
-  5. opentasks update t-x7k9 --status closed
-  6. opentasks query '{"blocking": {"nodeId": "t-x7k9"}}'  → see what's now unblocked
-  7. Repeat.
-```
-
-## Cross-System Dependencies
-
-`blocks` edges work across systems. The `ready` query evaluates them uniformly.
-
-```bash
-opentasks link --from "beads://./bd-setup" --to t-x7k9 --type blocks
-opentasks link --from t-x7k9 --to "claude://current/t-abc" --type blocks
-```
-
-## Discovering Work During Implementation
-
-```bash
-# Create the discovered issue
-opentasks create --type issue --title "Token refresh fails for expired sessions" --status open --tags auth,bug --priority 1
-# → t-new1
-
-# Link to where it was discovered
-opentasks link --from t-new1 --to t-x7k9 --type discovered-from
-
-# If it blocks current work:
-opentasks link --from t-new1 --to t-x7k9 --type blocks
-
-# Update original to blocked
-opentasks update t-x7k9 --status blocked
-```

package/references/opentasks/skills/opentasks/feedback-and-review.md

@@ -1,100 +0,0 @@
-# Feedback and Review
-
-Leave feedback on context and tasks, manage suggestion lifecycles, query unresolved items.
-
-## Feedback Types
-
-| Type | Use For |
-|------|---------|
-| `comment` | Status updates, implementation notes, observations |
-| `suggestion` | Proposed changes to target content |
-| `request` | Action needed — blocking questions, approvals |
-
-## Creating Feedback
-
-### Basic comment
-
-```bash
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"Implemented OAuth. Deferred SAML to follow-up.","type":"comment"}}'
-```
-
-### Implementation feedback (linked to source issue)
-
-```bash
-opentasks annotate '{"targetId":"c-a2b3","fromId":"t-x7k9","create":{"content":"Google OAuth requires access_type=offline for refresh tokens — added to config.","type":"comment"}}'
-```
-
-`fromId` creates a link from the task to the feedback for traceability.
-
-### Anchored suggestion
-
-```bash
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"Rate limiting needed here — OAuth endpoints are brute-force targets.","type":"suggestion","anchor":{"line":15,"text":"OAuth2 endpoints"}}}'
-```
-
-Anchors use `line` (exact), `text` (fuzzy match), or both. Text anchors survive content edits better.
-
-### Blocking request
-
-```bash
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"Which GitHub OAuth scopes? Spec says user profile but integration may need repo access.","type":"request"}}'
-```
-
-## Querying Feedback
-
-```bash
-# All feedback on a node
-opentasks query '{"feedback": {"nodeId": "c-a2b3"}}'
-
-# Unresolved suggestions only
-opentasks query '{"feedback": {"nodeId": "c-a2b3", "type": "suggestion", "resolved": false}}'
-
-# All unresolved feedback globally
-opentasks query '{"unresolvedFeedback": {}}'
-
-# Unresolved feedback for a specific target
-opentasks query '{"unresolvedFeedback": {"targetId": "c-a2b3"}}'
-```
-
-## Lifecycle Management
-
-```bash
-# Resolve (addressed)
-opentasks annotate '{"targetId":"c-a2b3","resolve":"f-t1u2"}'
-
-# Dismiss (not applicable)
-opentasks annotate '{"targetId":"c-a2b3","dismiss":"f-t1u2"}'
-
-# Reopen
-opentasks annotate '{"targetId":"c-a2b3","reopen":"f-t1u2"}'
-```
-
-## Review Workflow
-
-```bash
-# 1. Read spec
-opentasks get c-a2b3
-
-# 2. Check existing feedback
-opentasks query '{"feedback": {"nodeId": "c-a2b3"}}'
-
-# 3. Leave feedback
-opentasks annotate '{"targetId":"c-a2b3","create":{"content":"...","type":"comment"}}'
-
-# 4. Before implementing — check unresolved
-opentasks query '{"feedback": {"nodeId": "c-a2b3", "resolved": false}}'
-
-# 5. After addressing — resolve
-opentasks annotate '{"targetId":"c-a2b3","resolve":"f-abc1"}'
-```
-
-## Cross-System Feedback
-
-When source and target are in different systems, OpenTasks stores the feedback (native systems can't handle cross-refs).
-
-```bash
-# Beads issue commenting on Taskmaster spec
-opentasks annotate '{"targetId":"taskmaster://./auth-prd","fromId":"beads://./bd-x7k9","create":{"content":"Sections 1-3 done. Section 4 descoped.","type":"comment"}}'
-```
-
-Same-system feedback routes to native comments when the provider supports them.

package/references/opentasks/skills/opentasks/linking-external-data.md

@@ -1,103 +0,0 @@
-# Linking External Data
-
-Bind non-task artifacts — Slack messages, Google Docs, Notion pages, emails, URLs — to context and tasks in the graph.
-
-## Pattern
-
-Two steps: create an ExternalNode, then link it.
-
-### 1. Create the ExternalNode
-
-```bash
-opentasks create --type external \
-  --title "Alex: SSO redirect loop after IdP response" \
-  --uri "slack://C04ABCD/p1234567890" \
-  --source slack \
-  --metadata '{"channel_name":"#engineering","permalink":"https://workspace.slack.com/archives/C04ABCD/p1234567890","author":"alex","text":"auth flow is broken for SSO users — getting redirect loop after IdP response"}'
-# → { id: "e-k7m2", ... }
-```
-
-### 2. Link to the relevant node
-
-```bash
-opentasks link --from t-x7k9 --to e-k7m2 --type references \
-  --metadata '{"context":"Original bug report from #engineering"}'
-```
-
-## URI Conventions
-
-The `uri` field is freeform. Consistent schemes enable deduplication.
-
-| Source | Format | Example |
-|--------|--------|---------|
-| Slack message | `slack://[channel]/p[ts]` | `slack://C04ABCD/p1234567890` |
-| Slack thread | `slack://[channel]/t[thread_ts]` | `slack://C04ABCD/t1234567880` |
-| Google Doc | `gdoc://[doc-id]` | `gdoc://1BxiMVs0XRA5nF...` |
-| Notion page | `notion://[page-id]` | `notion://a1b2c3d4-e5f6-...` |
-| Figma file | `figma://[file-key]` | `figma://abc123DEF456` |
-| GitHub PR | `github://[owner]/[repo]/pull/[num]` | `github://org/repo/pull/42` |
-| Generic URL | `web://[url]` | `web://example.com/page` |
-
-## Edge Type Selection
-
-| Situation | Edge Type |
-|-----------|-----------|
-| Bug report, source document | `references` |
-| Found during investigation | `discovered-from` |
-| Loosely related context | `related` |
-
-Direction: typically `issue → external` or `spec → external`.
-
-## Deduplication
-
-Check before creating:
-
-```bash
-opentasks query '{"nodes": {"type": "external", "search": "slack://C04ABCD/p1234567890"}}'
-```
-
-If a node with that URI exists, skip creation and link to the existing node.
-
-## Phantom Nodes (URL only)
-
-If the agent only has a URL and can't fetch content:
-
-```bash
-opentasks create --type external \
-  --title "Related Slack thread" \
-  --uri "slack://C04ABCD/t1234567880" \
-  --source slack \
-  --metadata '{"permalink":"https://workspace.slack.com/archives/C04ABCD/p1234567880"}'
-```
-
-An agent with access to the external system can later enrich via `opentasks update`.
-
-## Querying Linked Data
-
-```bash
-# All references from a task
-opentasks query '{"edges": {"from_id": "t-x7k9", "type": "references"}}'
-
-# All external nodes from Slack
-opentasks query '{"nodes": {"type": "external", "search": "slack"}}'
-```
-
-## Complete Example
-
-```
-Agent working on "Fix SSO redirect loop":
-
-1. Search Slack via MCP → find 3 relevant messages
-
-2. For each, create ExternalNode:
-   opentasks create --type external --title "..." --uri "slack://..." --source slack --metadata '{...}'
-
-3. Link each to the task:
-   opentasks link --from t-x7k9 --to e-k7m2 --type references
-   opentasks link --from t-x7k9 --to e-k7m3 --type references
-   opentasks link --from t-x7k9 --to e-k7m4 --type discovered-from
-
-4. Later, another agent queries context:
-   opentasks query '{"edges": {"from_id": "t-x7k9", "type": ["references", "discovered-from"]}}'
-   → Gets back ExternalNodes with Slack content in metadata
-```

package/references/opentasks/skills/opentasks/spec-to-implementation.md

@@ -1,98 +0,0 @@
-# Spec to Implementation
-
-Full lifecycle: create a context, break into issues, set up dependencies, track to completion.
-
-## Native Workflow
-
-### 1. Create context
-
-```bash
-opentasks create --type spec \
-  --title "OAuth2 authentication for API" \
-  --content "## Requirements\n\n- Google OAuth2 with PKCE\n- GitHub OAuth2\n- Token refresh\n- Session management" \
-  --status active --tags auth --priority 1
-# → { id: "c-a2b3" }
-```
-
-### 2. Create issues
-
-```bash
-opentasks create --type issue --title "Set up OAuth provider config" --status open --tags auth --priority 1
-# → t-x7k9
-
-opentasks create --type issue --title "Implement Google OAuth login" --status open --tags auth --priority 1
-# → t-m4n5
-
-opentasks create --type issue --title "Implement GitHub OAuth login" --status open --tags auth --priority 2
-# → t-p6q7
-
-opentasks create --type issue --title "Token refresh and sessions" --status open --tags auth --priority 2
-# → t-r8s9
-```
-
-### 3. Link issues to spec
-
-```bash
-opentasks link --from t-x7k9 --to c-a2b3 --type implements
-opentasks link --from t-m4n5 --to c-a2b3 --type implements
-opentasks link --from t-p6q7 --to c-a2b3 --type implements
-opentasks link --from t-r8s9 --to c-a2b3 --type implements
-```
-
-### 4. Set up dependencies
-
-```bash
-opentasks link --from t-x7k9 --to t-m4n5 --type blocks   # config before Google
-opentasks link --from t-x7k9 --to t-p6q7 --type blocks   # config before GitHub
-opentasks link --from t-m4n5 --to t-r8s9 --type blocks   # Google before sessions
-opentasks link --from t-p6q7 --to t-r8s9 --type blocks   # GitHub before sessions
-```
-
-### 5. Execute with ready queries
-
-```bash
-opentasks query '{"ready": {}}'
-# → [t-x7k9] (only config is unblocked)
-
-# Work on it
-opentasks update t-x7k9 --status in_progress
-# ... do work ...
-opentasks update t-x7k9 --status closed
-
-# Query again
-opentasks query '{"ready": {}}'
-# → [t-m4n5, t-p6q7] (both unblocked, parallelizable)
-```
-
-### 6. Leave implementation feedback
-
-```bash
-opentasks annotate '{"targetId":"c-a2b3","fromId":"t-m4n5","create":{"content":"Google OAuth implemented with PKCE. Requires access_type=offline for refresh tokens.","type":"comment","anchor":{"text":"Google OAuth2 with PKCE"}}}'
-```
-
-### 7. Check progress
-
-```bash
-# All tasks of the context
-opentasks query '{"tasks": {"specId": "c-a2b3"}}'
-
-# Remaining blockers for sessions issue
-opentasks query '{"blockers": {"nodeId": "t-r8s9", "activeOnly": true}}'
-```
-
-## Cross-System Workflow
-
-When context and tasks live in different systems, OpenTasks provides the graph layer between them.
-
-```bash
-# Taskmaster spec + Beads issue
-opentasks link --from "beads://./bd-x7k9" --to "taskmaster://./auth-prd" --type implements
-
-# Query tasks across systems
-opentasks query '{"tasks": {"specId": "taskmaster://./auth-prd"}}'
-
-# Native issue + Claude subtask
-opentasks link --from "claude://current/t-abc" --to t-x7k9 --type child-of
-```
-
-OpenTasks doesn't manage content in external systems. Use their native tools (bd CLI, tm CLI, Claude TaskCreate) for CRUD, then use OpenTasks for cross-system edges.