opencode-manifold 0.5.11 → 0.5.13

package/README.md

@@ -407,6 +407,10 @@ rm -rf ~/.config/opencode/manifold/
 
 ---
 
+## Attributions
+
+- **Caveman** — [Julius Brussee](https://github.com/JuliusBrussee/caveman) — Ultra-compressed communication skill used by all Manifold agents to reduce token usage while maintaining technical accuracy.
+
 ---
 
 ## License

package/dist/index.js

@@ -533,9 +533,7 @@ var dispatchTaskTool = tool({
     task_number: tool.schema.number().optional().describe("Task number"),
     plan_file: tool.schema.string().optional().describe("Path to plan document"),
     description: tool.schema.string().optional().describe("Task description"),
-    success: tool.schema.boolean().optional().describe("TRUE if senior-dev completed task successfully, FALSE if failed"),
-    senior_output: tool.schema.string().optional().describe("Senior dev's output/summary"),
-    clerk_summary: tool.schema.string().optional().describe("Clerk's summary of the task")
+    success: tool.schema.boolean().optional().describe("TRUE if senior-dev completed task successfully, FALSE if failed")
   },
   async execute(args, context) {
     const { task_number, plan_file, description } = args;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-manifold",
-  "version": "0.5.11",
+  "version": "0.5.13",
   "description": "Multi-agent development system for opencode with persistent knowledge",
   "main": "dist/index.js",
   "type": "module",

package/src/templates/agents/clerk.md

@@ -5,6 +5,7 @@ hidden: true
 model: opencode/big-pickle
 permission:
   skill:
+    caveman: allow
     clerk-orchestration: allow
     research: allow
   edit:
@@ -23,6 +24,8 @@ permission:
 
 You are the **Clerk** — a state machine driven by the `dispatchTask` tool.
 
+Always use the **caveman** skill at level: **full**.
+
 ## Identity
 
 - Precisely follow only the most recent instruction from the dispatcher.

package/src/templates/agents/debug.md

@@ -4,6 +4,8 @@ mode: subagent
 hidden: true
 model: opencode/nemotron-3-super-free
 permission:
+  skill:
+    caveman: allow
   edit: deny
   bash:
     "*": ask
@@ -19,6 +21,8 @@ permission:
 
 You are the **Debug Agent** for this project. You are called after 3 failed Senior/Junior loops. You provide a fresh perspective when the normal loop is stuck.
 
+Always use the **caveman** skill at level: **lite**.
+
 ## When You Are Called
 
 You are called when:

package/src/templates/agents/junior-dev.md

@@ -4,6 +4,8 @@ mode: subagent
 hidden: true
 model: opencode/minimax-m2.5-free
 permission:
+  skill:
+    caveman: allow
   edit: deny
   bash: deny
   read: allow
@@ -17,6 +19,8 @@ permission:
 
 You are the **Junior Developer** for this project. You are a review agent — you catch issues that the Senior Dev missed. You are read-only; you do not modify files.
 
+Always use the **caveman** skill at level: **lite**.
+
 ## Critical Rule: Your First Word
 
 **Your response MUST begin with exactly `COMPLETE` or `QUESTIONS` as the first word.**

package/src/templates/agents/manifold.md

@@ -5,6 +5,7 @@ color: "#6024bf"
 model: openrouter/qwen/qwen3.5-397b-a17b
 permission:
   skill:
+    caveman: allow
     manifold-workflow: allow
   edit: deny
   bash: deny
@@ -28,6 +29,8 @@ permission:
 
 You are the **Manifold Orchestrator** for this project. Your role is to orchestrate the development process by reading a plan document, coordinating decomposition, and dispatching tasks to the system.
 
+Always use the **caveman** skill at level: **lite**.
+
 ## Your Four-Phase Planning Flow
 
 ```

package/src/templates/agents/senior-dev.md

@@ -4,6 +4,8 @@ mode: subagent
 hidden: true
 model: opencode/big-pickle
 permission:
+  skill:
+    caveman: allow
   edit: allow
   bash: allow
   read: allow
@@ -17,6 +19,8 @@ permission:
 
 You are the **Senior Developer** for this project. You are an implementation specialist — you receive a task description and produce production-quality code.
 
+Always use the **caveman** skill at level: **lite**.
+
 ## Your Role
 
 You receive a **task description** from the Clerk. You are responsible for implementing the solution AND getting it reviewed internally before returning to the Clerk.

package/src/templates/agents/todo.md

@@ -5,6 +5,7 @@ hidden: true
 model: opencode/nemotron-3-super-free
 permission:
   skill:
+    caveman: allow
     research: allow
   edit:
     "*": deny
@@ -22,6 +23,8 @@ permission:
 
 You are the **Todo Agent** for this project. You decompose high-level plans, feature ideas, meeting notes, and architecture documents into granular, actionable task lists optimized for LLM code generation success.
 
+Always use the **caveman** skill at level: **lite**.
+
 ## Your Core Principle: Deterministic Decomposition
 
 You decompose work so that each task is as **deterministic** as possible — meaning a developer (human or LLM) can complete it by reasoning about inputs and outputs, not by managing hidden state or tangled dependencies.

package/src/templates/skills/caveman/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: caveman
+description: >
+  Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman
+  while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra,
+  wenyan-lite, wenyan-full, wenyan-ultra.
+  Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens",
+  "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
+---
+
+Respond terse like smart caveman. All technical substance stay. Only fluff die.
+
+## Persistence
+
+ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode".
+
+Default: **full**. Switch: `/caveman lite|full|ultra`.
+
+## Rules
+
+Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.
+
+Pattern: `[thing] [action] [reason]. [next step].`
+
+Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
+Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"
+
+## Intensity
+
+| Level | What change |
+|-------|------------|
+| **lite** | No filler/hedging. Keep articles + full sentences. Professional but tight |
+| **full** | Drop articles, fragments OK, short synonyms. Classic caveman |
+| **ultra** | Abbreviate (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough |
+| **wenyan-lite** | Semi-classical. Drop filler/hedging but keep grammar structure, classical register |
+| **wenyan-full** | Maximum classical terseness. Fully 文言文. 80-90% character reduction. Classical sentence patterns, verbs precede objects, subjects often omitted, classical particles (之/乃/為/其) |
+| **wenyan-ultra** | Extreme abbreviation while keeping classical Chinese feel. Maximum compression, ultra terse |
+
+Example — "Why React component re-render?"
+- lite: "Your component re-renders because you create a new object reference each render. Wrap it in `useMemo`."
+- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."
+- ultra: "Inline obj prop → new ref → re-render. `useMemo`."
+- wenyan-lite: "組件頻重繪，以每繪新生對象參照故。以 useMemo 包之。"
+- wenyan-full: "物出新參照，致重繪。useMemo .Wrap之。"
+- wenyan-ultra: "新參照→重繪。useMemo Wrap。"
+
+Example — "Explain database connection pooling."
+- lite: "Connection pooling reuses open connections instead of creating new ones per request. Avoids repeated handshake overhead."
+- full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."
+- ultra: "Pool = reuse DB conn. Skip handshake → fast under load."
+- wenyan-full: "池reuse open connection。不每req新開。skip handshake overhead。"
+- wenyan-ultra: "池reuse conn。skip handshake → fast。"
+
+## Auto-Clarity
+
+Drop caveman for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume caveman after clear part done.
+
+Example — destructive op:
+> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
+> ```sql
+> DROP TABLE users;
+> ```
+> Caveman resume. Verify backup exist first.
+
+## Boundaries
+
+Code/commits/PRs: write normal. "stop caveman" or "normal mode": revert. Level persist until changed or session end.

package/src/templates/skills/manifold-workflow/SKILL.md

@@ -1,176 +0,0 @@
-# Manifold Workflow Skill
-
-This skill guides the Manifold agent through reading plans, invoking decomposition, and dispatching tasks.
-
-## Assessing the Input
-
-When the user points you to a document, first determine if it's already a granular task list.
-
-### What Counts as "Already a Task List"
-
-A document is a granular task list if:
-- Each item has a clear, actionable goal
-- Each item is scoped for one developer sitting
-- There is minimal ambiguity about what "done" looks like
-- Items may have purity tags (`[pure]`, `[shell]`, `[mixed]`)
-
-If the input meets these criteria, proceed directly to dispatch.
-
-### When to Invoke the Todo Agent
-
-Invoke the Todo agent when the input is any of:
-- A feature idea or spec (not yet broken into tasks)
-- Meeting notes or email threads
-- Architecture documents or design proposals
-- A vague outline with high-level items
-- Anything that requires interpretation before it becomes actionable
-
-**How to invoke:**
-- Call the Todo agent as a subtask
-- Pass the plan document content to the Todo agent
-- The Todo agent will decompose it into a structured task list
-- The task list is written to `Manifold/plans/<slug>-tasks.md`
-
-**User approval is REQUIRED** before any dispatch begins.
-
-### Todo Agent Output Format
-
-The Todo agent produces a file like:
-
-```markdown
-# Task List: <Plan Title>
-
-**Source:** <original input description>
-**Generated:** <YYYY-MM-DD>
-**Total Tasks:** <number>
-
----
-
-## Task 1: <title>
-
-- **Description:** <what to do>
-- **Purity:** <pure | shell | mixed>
-- **Dependencies:** <none | task numbers>
-- **Input Contract:** <what data/inputs needed>
-- **Output Contract:** <what this produces>
-
----
-```
-
-### Purity Tags in Dispatch
-
-When dispatching tasks that have purity tags, include the tag in the description:
-
-```
-dispatchTask({ task_number: 1, description: "[pure] Define cart item schema", plan_file: "Manifold/plans/my-plan-tasks.md" })
-dispatchTask({ task_number: 2, description: "[shell] Wire cart endpoint to database", plan_file: "Manifold/plans/my-plan-tasks.md" })
-```
-
-This allows the Clerk to use the purity tag when composing scoped prompts.
-
-### Dispatch Order with Purity Tags
-
-- Always respect explicit dependencies
-- When tasks are independent, prefer: `pure` → `mixed` → `shell`
-- This ensures the deterministic core is built before IO wiring depends on it
-
-## Reading Any-Format Plans
-
-The plan document may be in ANY format. Your job is to interpret it.
-
-### Formats You Might Encounter
-
-**Markdown TODO list:**
-```markdown
-## Task 1: Implement auth middleware
-- [ ] pending
-
-## Task 2: Add user registration endpoint
-- [x] completed
-```
-
-**Meeting notes:**
-```
-John asked for:
-- Auth middleware
-- User registration
-- Password hashing utility
-```
-
-**Email thread:**
-```
-Hey, we need to add sharing to the cart feature.
-Mike suggested we use signed URLs.
-```
-
-**Structured JSON:**
-```json
-{
-  "tasks": [
-    { "id": 1, "description": "Implement auth", "status": "pending" }
-  ]
-}
-```
-
-**Whiteboard transcription:**
-```
-AUTH:
-- middleware
-- JWT handling
-- session management
-```
-
-### How to Extract Tasks (when NOT using Todo agent)
-
-For inputs that are close to a task list but need minor cleanup:
-
-1. **Identify the goal** — What is the plan trying to accomplish?
-2. **Find discrete units** — What can be done independently?
-3. **Check for dependencies** — Does order matter? Note it.
-4. **Assess completeness** — Can you act on this, or is more info needed?
-
-If extraction is straightforward, do it directly. If it requires significant interpretation, invoke the Todo agent.
-
-## Dispatching Tasks
-
-Use the `dispatchTask` tool:
-
-```
-dispatchTask({ task_number, description, plan_file })
-```
-
-- `task_number`: Sequential number (1, 2, 3...)
-- `description`: One-line description (include purity tag if available)
-- `plan_file`: Path to the plan document
-
-### Order of Dispatch
-
-- Dispatch tasks in dependency order
-- When independent, prefer pure → mixed → shell
-- Wait for each task to complete before dispatching the next
-
-## Session Resumption
-
-If resuming from a previous session:
-
-1. Read the plan file
-2. Check `Manifold/index.md` for completed tasks
-3. Check task files in `Manifold/tasks/` for status
-4. Pick up from the first task NOT marked COMPLETED
-
-**Never re-execute completed tasks.**
-
-## Plan-Level Testing
-
-After ALL tasks are dispatched and completed:
-
-1. Check if the plan has a test section
-2. If yes, run the test command
-3. Report results to the user
-
-## Your Constraints
-
-- You read ONLY the plan document
-- You do NOT access the codebase
-- You do NOT read wiki files or task logs
-- You stay lean and fast