@questionbase/deskfree 0.3.0-alpha.22 → 0.3.0-alpha.24

package/skills/deskfree/SKILL.md

@@ -4,12 +4,12 @@ description: >
   DeskFree task management and human-AI collaboration workflows.
   Use when: creating tasks, managing work items, updating files,
   communicating with humans through DeskFree, checking workspace state,
-  handling task lifecycle (start → work → complete → review),
-  evaluating completed tasks, updating ways of working, managing initiatives.
+  handling task lifecycle (pending → active → review → done),
+  updating ways of working, managing initiatives.
   Do NOT use for: general project management advice without DeskFree tools,
   OpenClaw configuration or gateway setup, non-DeskFree platforms (Jira, Asana, etc.),
   direct file/code operations (use standard tools for those, create DeskFree tasks for tracking).
-version: 8.0.0
+version: 10.0.0
 metadata: { 'openclaw': { 'emoji': '🏠' } }
 ---
 
@@ -17,710 +17,220 @@ metadata: { 'openclaw': { 'emoji': '🏠' } }
 
 ## ⚠️ Critical — Read First
 
-### State Machine (memorize this)
+### Status Model (memorize this)
 
 ```
-                              🎯 Initiative lifecycle
-suggest_tasks ──────────────────────────────────────────────────────────────────┐
-  + initiativeSuggestions →  [human approves initiative] → active               │
-                              [human rejects initiative]  → deleted              │
-                                                                                 │
-suggest_tasks → [human approves] → bot → [start_task] → bot (is_working)       │
-                   ↑                                          │                  │
-                   |               human approves/declines    │                  │
-                   └──────────────────────────────────────────┘                  │
-                                                              │                  │
-                                                         [complete_task]         │
-                                                              ↓                  │
-                                                           human                 │
-                                                              │                  │
-                                                         [approve]               │
-                                                              ↓                  │
-                                                           done ──→ [evaluate] ──┘
-                                                                        ↓
-                                                              globalWoW updated (always)
-                                                              + initiative updated (if task has initiative_id)
+pending → active → review → done
 ```
 
-- `complete_task` outcome `done` = work complete (summary required)
-- `complete_task` outcome `blocked` = need human input (send message FIRST explaining why)
-- Both outcomes move to `human` — the human triages from there
-- When human approves (`done`), a pending evaluation is created for ways-of-working update
+- **pending** — Approved, waiting for bot to claim
+- **active** — Bot claimed, runner working
+- **review** — Bot submitted deliverable, waiting for human feedback
+- **done** — Completed
 
 ### The Work Loop
 
 ```
-1. Check state     → deskfree_state — see tasks, active initiatives, files, pending evaluations
-2. Suggest tasks   → deskfree_suggest_tasks — propose work + optional initiative + file suggestions
-3. Claim a task    → deskfree_start_task — read instructions + parent context + fileContext
+1. Check state     → deskfree_state — see tasks, initiatives, files, ways of working
+2. Propose plan    → deskfree_propose — propose work for human approval
+3. Claim a task    → deskfree_start_task — read instructions + context + fileContext
 4. Do the work     → deskfree_update_file — build linked file incrementally
-5. Suggest follow-ups → if work reveals more to do, suggest them via deskfree_suggest_tasks (link to initiative)
-6. Complete        → deskfree_complete_task — summary required for "done"
-7. Evaluate        → if approved tasks have pending WoW evaluation (update globalWoW + initiative)
+5. Complete        → deskfree_complete_task — with outcome + summary + learnings
 ```
 
-### Three Rules That Break Everything If Ignored
+### Three Rules
 
-1. **Always suggest first.** Use `deskfree_suggest_tasks` before starting ANY work. Tasks go through human approval. No exceptions.
-2. **Always check state first.** Call `deskfree_state` before suggesting tasks. Prevents duplicates, shows active initiatives and files.
-3. **Always complete tasks.** Never leave a task in `bot` (is_working=true). End with `deskfree_complete_task` — outcome `done` or `blocked`.
+1. **Always propose first.** Use `deskfree_propose` before starting ANY work. Nothing is created until human approves.
+2. **Always check state first.** Call `deskfree_state` before proposing. Prevents duplicates.
+3. **Always complete tasks.** Never leave a task in `active`. End with `deskfree_complete_task`.
 
-### Writing Great Instructions
-
-Write instructions as if briefing a contractor who has never seen the codebase. Include:
-- **What to do** — specific, actionable steps
-- **Why** — referencing parent findings or file content when applicable
-- **What "done" looks like** — clear acceptance criteria
-- **Known constraints** — gotchas, dependencies, things to avoid
-
-### File-Based Work Output
-
-**Work that produces persistent documents should use files.** A file persists beyond the task — it becomes the lasting artifact of your work.
-
-**When to use files:**
-- Writing specs, runbooks, reports, documentation
-- Any output a human will reference after the task closes
-- Output that follow-up tasks will build on
-
-**How to link files to tasks:**
-- Use `newFile` in `deskfree_suggest_tasks` to pre-create a file when you know the task will produce one
-- Use `fileId` to link an existing file to a new task
-- When claiming a task with a linked file, its current content is in `fileContext` — read it before starting work
-
-**Completing a task:**
-- Provide a clear `summary` of what was accomplished (required for outcome `done`)
-- If the task updated a file, mention the file name/ID in the summary
-
-### Suggesting Follow-ups
-
-When completing, always consider: does this work reveal follow-up tasks? If yes, suggest them. Your suggestions are strongest at this moment because you have full context.
-
-Call `deskfree_suggest_tasks` before or after completing — pass `parentTaskId` to link follow-ups to the current task. Estimate token cost per suggestion — consider how many files to read, how much reasoning, how much output.
+---
 
-### Building the Chain
+## Tools
 
-You're not just doing tasks — you're building a chain. The instructions you write become someone else's brief. The files you produce become someone else's context. Write both with care.
+### Orchestrator (5 tools — main session)
 
-### Auto-Threading
+| Tool | What it does |
+|---|---|
+| `deskfree_state` | Full workspace snapshot — tasks, done tasks, ways of working, initiatives, files |
+| `deskfree_propose` | Propose a plan for human approval — tasks, initiatives, file links |
+| `deskfree_send_message` | Message in task thread |
+| `deskfree_reopen_task` | Reopen a done/review task back to pending |
+| `deskfree_update_knowledge` | Update global ways of working or initiative content |
 
-After `deskfree_start_task`, ALL your outbound messages automatically thread into that task. No need to pass `taskId` to `deskfree_send_message`. After `deskfree_complete_task`, auto-threading stops.
+### Worker (5 tools — sub-agents)
 
-The task sidebar is your human's window into your work — every message appears there in real-time.
+| Tool | What it does |
+|---|---|
+| `deskfree_start_task` | Claim a pending task → active. Returns full context |
+| `deskfree_update_file` | Update a linked file's content |
+| `deskfree_complete_task` | Complete task with outcome, summary, and learnings |
+| `deskfree_send_message` | Message in task thread |
+| `deskfree_propose` | Propose follow-up tasks (workers have deepest context) |
 
 ---
 
-## Working with Files
+## Proposing Plans
 
-Files are persistent documents owned by a bot that live across tasks.
+Proposals are stored as message metadata — **no tasks, files, or initiatives are created until the human approves**.
 
-```
-deskfree_state() → shows files: [{fileId, name, description, version, updatedAt}, ...]
+### One Initiative Per Proposal
 
-deskfree_start_task(taskId) → if task.fileId, returns fileContext: {
-  fileId, name, description, content, contentFormat, version
-}
-```
+Each `deskfree_propose` call handles one initiative (existing or new) or no initiative. Separate calls for separate initiatives.
+
+### Substeps
 
-### Creating Files
+Substeps are human-reviewable checklist items. The human can toggle each on/off before approving:
 
 ```javascript
-// Option 1: Pre-create when suggesting a task
-deskfree_suggest_tasks({
-  suggestions: [{
-    title: "Write API documentation",
-    instructions: "...",
-    newFile: {
-      name: "API Reference",
-      description: "Full API reference documentation for v2 endpoints"
-    }
+deskfree_propose({
+  tasks: [{
+    title: "Audit auth endpoints",
+    instructions: "Review all authentication endpoints for security issues...",
+    substeps: [
+      "Review session management",
+      "Check CSRF protection",
+      "Verify rate limiting"
+    ]
   }]
 })
-// → file is created and linked to the task
-
-// Option 2: Create a file directly during work
-deskfree_create_file({
-  name: "Deployment Runbook",
-  description: "Step-by-step deployment guide",
-  content: "# Deployment Runbook\n\n...",
-  contentFormat: "markdown"
-})
 ```
 
-### Updating Files
+### File Linking
 
 ```javascript
-// Always send the full current content — each call replaces the previous version
-deskfree_update_file({
-  fileId: "F_abc123",
-  content: "# Full document...",
-  contentFormat: "markdown"  // or "html"
+// Link existing file — bot receives content when claiming
+deskfree_propose({
+  tasks: [{
+    title: "Update API docs",
+    file: { existingId: "FILE_abc123" }
+  }]
 })
-```
-
-**Build incrementally** — update the file early and often. A half-complete file is infinitely better than none if you're interrupted.
-
-### File Format Choice
 
-| Format | Use when |
-|---|---|
-| `markdown` (default) | Text reports, specs, documentation, analysis, code snippets |
-| `html` | Rich web content: dashboards, styled reports, interactive tables |
-
-HTML files are rendered in a **sandboxed iframe**. Use `format="html"` when layout and styling matter for the human's review.
-
----
-
-## Initiatives — Long-Lived Areas of Focus
-
-Initiatives answer **"what are we working on and why"** while Ways of Working answers **"how do we work."**
-
-| Concept | What it is |
-|---|---|
-| **Initiative** | A persistent area of focus (e.g. "Auth Hardening", "Performance Sprint") |
-| **Initiative Content** | A versioned markdown doc — current state, approach, next priorities |
-| **Task → Initiative link** | Set `initiativeId` on suggestions to link tasks to an initiative |
-
-**Default initiative:** Every bot has a "General" initiative for uncategorized work. Tasks without an explicit `initiativeId` are automatically linked to it.
-
-### When to Propose a New Initiative
-
-```
-On every suggest_tasks call, ask yourself:
-
-"Does an active initiative exist that this work belongs to?"
-→ Yes: set initiativeId on the relevant suggestions
-→ No, but this is part of a bigger theme: add an initiativeSuggestion
-→ No, and it's a one-off task: no initiative needed (defaults to General)
+// Create new file on approval
+deskfree_propose({
+  tasks: [{
+    title: "Write deployment runbook",
+    file: { name: "Deployment Runbook", description: "Step-by-step guide" }
+  }]
+})
 ```
 
-### Initiative Suggestion Flow
-
-```
-1. deskfree_state() → check initiatives[] for existing active ones
-
-2. deskfree_suggest_tasks({
-     suggestions: [
-       { title: "Audit auth endpoints", estimatedTokens: 20000 },
-       { title: "Add rate limiting",    estimatedTokens: 15000 }
-     ],
-     initiativeSuggestions: [
-       {
-         title: "Auth Hardening",
-         content: "# Auth Hardening\n\n## Current State\nNeed to improve auth security.\n\n## Approach\nTBD — start with audit.\n\n## Next Priorities\n1. Audit all auth endpoints\n2. Address findings",
-         taskRefs: [0, 1]   // auto-links tasks at index 0 and 1 when approved
-       }
-     ]
-   })
-
-Human sees:
-  🎯 New Initiative: "Auth Hardening"     [Approve] [Reject]
-  📋 Task: "Audit auth endpoints..."      [Approve] [Reject]
-  📋 Task: "Add rate limiting..."         [Approve] [Reject]
-```
+---
 
-### Linking Tasks to Existing Initiatives
+## Completing Tasks
 
-```
-deskfree_state() → sees initiatives: [{ id: "init_abc", title: "Auth Hardening", status: "active" }]
-
-deskfree_suggest_tasks({
-  suggestions: [
-    { title: "Implement CSRF protection",
-      instructions: "...",
-      estimatedTokens: 25000,
-      initiativeId: "init_abc"   // link to existing initiative
-    }
-  ]
-  // no initiativeSuggestions needed — initiative already exists
+```javascript
+deskfree_complete_task({
+  taskId: "T_abc123",
+  outcome: "review",     // "review" | "done" | "blocked" | "cancelled"
+  summary: "Implemented auth hardening across all endpoints",
+  learnings: "Found that rate limiting needs to be per-IP, not per-session"
 })
 ```
 
----
-
-## Ways of Working — The Evolving Playbook
+- **review** — Submit for human feedback. Human responds in thread, bot reads and decides.
+- **done** — Work complete (summary required). Learnings integrated into WoW.
+- **blocked** — Need human input. Send a message explaining WHY first.
+- **cancelled** — Task no longer needed.
 
-Ways of Working is a **single versioned markdown document** per bot that evolves as you complete tasks. It's your institutional memory — capturing patterns, preferences, and learnings across all work.
+**Learnings** are only applied to ways of working when a task reaches `done`, not during `review` (human might reject).
 
-**Key properties:**
-- Injected automatically via `deskfree_state` (the `waysOfWorking` field)
-- Read it before starting work to understand established patterns
-- Updated after task approval via the evaluation flow (never manually during work)
-- Each update creates a new immutable version — full history preserved
-
-### Evaluation Flow — Dual Output
+---
 
-When a human approves a task, it enters `pendingEvaluations` in state.get. Evaluation now has **two independent outputs**:
+## Conversational Review
 
-```
-1. deskfree_claim_evaluation(taskId)
-   → returns: task + messages + waysOfWorking + initiative (if task has initiative_id)
+There are no approve/decline buttons. The flow is:
 
-2. Review the task summary, messages, and any file output
+1. Bot completes task with outcome `review`
+2. Human responds in the task thread with feedback
+3. Bot reads feedback and either:
+   - Continues working (task stays active)
+   - Completes with outcome `done`
+   - Reopens if major rework needed
 
-3. Ask yourself:
-   "Did I learn something about HOW we work that applies everywhere?"
-   → Yes: update globalWoW
+---
 
-   "Did I learn something about WHERE this initiative stands or
-    HOW to approach this specific area?"
-   → Yes: update initiative content
+## Ways of Working
 
-   Both? → update both
-   Neither? → hasChanges: false for both
+A single versioned markdown document per bot. Updated via `deskfree_update_knowledge` (orchestrator only — single writer avoids version conflicts).
 
-4. deskfree_submit_evaluation({
-     taskId,
-     reasoning: "...",
-     globalWoW:  { hasChanges: true,  updatedContent: "..." },
-     initiative: { hasChanges: false }
-   })
-```
+Workers pass `learnings` in `complete_task`. When a task reaches `done`, the orchestrator integrates learnings into WoW via `update_knowledge`.
 
-**globalWoW** — patterns that apply to all work everywhere. Examples:
-- A better approach to error handling you discovered
-- A recurring mistake to avoid
-- A tool or service pattern that's universally useful
+---
 
-**initiative content** — what was learned about this specific area of focus. Examples:
-- Current state of the initiative has changed (task completed a major piece)
-- New findings shifted the approach
-- Next priorities should be reordered
+## Initiatives
 
-**When NOT to update either:** One-off tasks with no transferable learnings, standard work that matched existing patterns.
+Long-lived areas of focus. Proposed via `deskfree_propose`:
 
-### Example Evaluation
+```javascript
+// Link to existing
+deskfree_propose({
+  initiative: "INI_abc123",
+  tasks: [...]
+})
 
-```
-Task "Audit auth endpoints" (linked to "Auth Hardening" initiative) is approved.
-
-claim_evaluation → returns:
-  task (with summary: "Found 3 critical issues: session fixation, weak CSRF, no rate limiting")
-  waysOfWorking: "..."
-  initiative: { id: "init_abc", title: "Auth Hardening", content: "No audit done yet." }
-
-Analysis:
-  - Gateway has built-in rate limiting (just needs config) → applies everywhere → update globalWoW
-  - Audit found 3 critical issues → initiative content needs update → update initiative
-
-submit_evaluation({
-  taskId: "audit-task",
-  reasoning: "Audit found 3 issues. Gateway has rate limiting built in — updated both.",
-  globalWoW: {
-    hasChanges: true,
-    updatedContent: "...## Infrastructure\n- Always check AWS API Gateway config before building custom middleware\n..."
-  },
-  initiative: {
-    hasChanges: true,
-    updatedContent: "# Auth Hardening\n\n## Current State\nAudit complete. Found 3 critical issues:\n1. Session fixation\n2. No rate limiting (gateway supports it — just needs config)\n3. Weak CSRF\n\n## Next Priorities\n1. Configure gateway rate limiting (quick win)\n2. Fix session fixation\n3. Implement CSRF tokens"
-  }
+// Create new
+deskfree_propose({
+  initiative: { title: "Auth Hardening", content: "# Auth Hardening\n\n..." },
+  tasks: [...]
 })
 ```
 
 ---
 
-## Validation Gates
-
-### Pre-Flight (before ANY work)
-
-- [ ] Called `deskfree_state` — confirmed it returned data (not empty/error)
-- [ ] Read `waysOfWorking` if present — apply established patterns
-- [ ] Read `initiatives` if present — check for active initiatives this work belongs to
-- [ ] Checked `files` list — know what persistent files already exist
-- [ ] Checked for existing tasks that match intent — no duplicates
-- [ ] Suggested a task via `deskfree_suggest_tasks` — with `initiativeId` if linking to existing initiative, or `initiativeSuggestions` if proposing new one, and `newFile` if task will produce a document
-- [ ] Once approved: called `deskfree_start_task` — confirmed task moved to `bot` (is_working=true)
-- [ ] If task has `fileContext` — read the existing file content before starting work
-
-### Mid-Work
-
-- [ ] File updated immediately after starting task (not waiting until end)
-- [ ] `deskfree_update_file` succeeded (no error response)
-- [ ] If blocked: sent message explaining WHY before calling `complete_task` with `blocked`
-
-### Pre-Completion
-
-- [ ] File content is non-empty and meaningful (if task produces a file)
-- [ ] File is well-structured and stands alone as a document
-- [ ] Called `deskfree_complete_task` with a clear `summary` — confirmed task moved to `human`
-- [ ] If sub-agent: terminated after completion (one task per sub-agent)
+## Working with Files
 
-### Heartbeat Evaluation Check
+Files are persistent documents owned by a bot.
 
-- [ ] Any `pendingEvaluations` in state? → claim and evaluate each one (submit globalWoW + initiative outputs)
+- **Creating:** Via `deskfree_propose` with `file: { name, description }` (created on approval)
+- **Updating:** `deskfree_update_file` — always send full content (replaces previous version)
+- **Formats:** `markdown` (default) or `html` (for rich web content)
+- **Build incrementally** — update early and often. Partial > nothing.
 
 ---
 
-## Task Workflow
-
-### Orchestrator Flow (main session)
-
-```
-1. deskfree_state                  → assess workspace + read ways of working + check active initiatives + check files
-2. deskfree_suggest_tasks          → suggest tasks (with estimatedTokens, initiativeId, initiativeSuggestions, newFile)
-3. deskfree_start_task             → claim approved task (returns full context + parent context + fileContext)
-4. deskfree_update_file            → build linked file incrementally as you work
-5. deskfree_suggest_tasks          → suggest follow-ups if work reveals more (parentTaskId to link)
-6. deskfree_complete_task          → complete with outcome done (+ summary) or blocked
-```
-
-### Sub-Agent Flow (recommended for tasks > 5 min)
+## Sub-Agent Pattern
 
 ```
-Orchestrator: deskfree_suggest_tasks → (human approves) → deskfree_start_task → spawn sub-agent with full task context
-Sub-agent:    deskfree_update_file (incrementally) → deskfree_suggest_tasks (follow-ups if needed) → deskfree_complete_task (+ summary) → terminate
+Orchestrator: deskfree_state → deskfree_propose → (human approves) → spawn sub-agent
+Sub-agent:    deskfree_start_task → deskfree_update_file → deskfree_complete_task → terminate
 ```
 
-Sub-agents have **7 tools:** `deskfree_update_file`, `deskfree_create_file`, `deskfree_complete_task`, `deskfree_send_message`, `deskfree_suggest_tasks`, `deskfree_claim_evaluation`, `deskfree_submit_evaluation`. Workers have workspace context for awareness — focus on your assigned task and use context to avoid duplicate suggestions.
-
-**Worker pattern — after submitting evaluation:** reflect on what you learned and call `deskfree_suggest_tasks` for follow-up opportunities that emerged from the evaluation.
-
-### When to Use Main vs Sub-Agent
-
-| Main session | Sub-agent |
-|---|---|
-| Quick tasks (< 5 min) | Research, reports, analysis |
-| Interactive/back-and-forth | Code development, debugging |
-| Urgent fixes | Long operations (> 10 min) |
-| | Background work while human may message |
-
----
-
-## Recurrence — Natural Language + scheduledFor
-
-**Recurrence is handled through task instructions, NOT through special fields.** DeskFree uses a simple suggest → complete → suggest cycle for recurring work.
-
-### How Recurrence Works
-
-1. **Document the pattern** in task instructions using natural language:
-   - "This task recurs weekly on Mondays. When completing, suggest the next occurrence with scheduledFor set to next Monday."
-   - "Monthly report — recurs on the 1st of each month. Schedule next occurrence for first day of next month."
-
-2. **Set the first occurrence** using `scheduledFor` in your suggestion:
-   ```javascript
-   deskfree_suggest_tasks({
-     suggestions: [{
-       title: "Weekly team sync prep",
-       instructions: "Prepare agenda for Monday team meeting. This task recurs weekly on Mondays. When completing, suggest the next occurrence with scheduledFor set to next Monday at 9 AM.",
-       scheduledFor: "2026-03-03T14:00:00Z" // Next Monday 9 AM EST
-     }]
-   })
-   ```
-
-3. **Propagate on completion** — when you complete a recurring task, read the instructions and suggest the next occurrence:
-   ```javascript
-   // After completing the task:
-   deskfree_suggest_tasks({
-     suggestions: [{
-       title: "Weekly team sync prep",
-       instructions: "Prepare agenda for Monday team meeting. This task recurs weekly on Mondays. When completing, suggest the next occurrence with scheduledFor set to next Monday at 9 AM.",
-       scheduledFor: "2026-03-10T14:00:00Z" // Following Monday
-     }],
-     parentTaskId: "current-task-id"
-   })
-   ```
-
-### Key Points
-
-- **No special recurrence fields** — it's just natural language in instructions + `scheduledFor`
-- **You are responsible** for reading the recurrence pattern and creating the next occurrence
-- **Use scheduledFor** to control when the task becomes available
-- **Include the recurrence instructions** verbatim in follow-up suggestions so the pattern continues
-- **Be precise with dates** — calculate the next occurrence based on the documented pattern
-
----
-
-## Messaging
-
-**Normal replies:** Just respond — the channel handles routing automatically. No tool needed.
-
-**Use `deskfree_send_message` only for:**
-- Progress updates during task execution
-- Questions needing human input mid-task
-- Status reports for long-running tasks
-
-**Never use it for:** Normal conversation replies (channel handles those).
+- One task per sub-agent
+- Sub-agent calls `deskfree_start_task` (enables cost attribution via runnerId)
+- Orchestrator never claims tasks directly
 
 ---
 
 ## Decision Tree
 
-### Heartbeat / Proactive Check
-
-1. `deskfree_state` → get workspace snapshot + check `waysOfWorking` + `initiatives` + `files` + `pendingEvaluations`
-2. `pendingEvaluations`? → `deskfree_claim_evaluation` → `deskfree_submit_evaluation` (with globalWoW + initiative outputs)
-3. `bot` tasks? → `deskfree_start_task` + spawn sub-agents
-4. `bot` (is_working=true) with no active sub-agent? → Complete as blocked or resume
+### Heartbeat
+1. `deskfree_state` → get snapshot
+2. `pending` tasks? → spawn sub-agents to claim them
+3. `active` tasks with no active sub-agent? → complete as blocked or resume
 
 ### Human Gives You Work
-
-1. `deskfree_state` → check existing tasks + read ways of working + check active initiatives + check files
-2. Does this work belong to an active initiative? → set `initiativeId` on suggestions
-   OR is this starting a new area of focus? → add `initiativeSuggestions`
-3. Will the task produce a persistent document? → add `newFile` to the suggestion
-4. `deskfree_suggest_tasks` → suggest with clear title + instructions
-5. [human approves] → `deskfree_start_task` → claim it + read fileContext if present
-6. Work → `deskfree_update_file` incrementally
-7. `deskfree_complete_task` → outcome `done` (with summary) or `blocked`
-
----
-
-## Tools Reference
-
-> **Full parameter details:** See `references/tools.md`
-
-### Orchestrator (9 tools)
-
-| Tool | What it does |
-|---|---|
-| `deskfree_state` | Full workspace snapshot — tasks, recently done, ways of working, active initiatives, files, pending evaluations |
-| `deskfree_suggest_tasks` | Suggest tasks for human approval (with estimatedTokens, initiativeId, initiativeSuggestions, newFile, fileId) |
-| `deskfree_start_task` | Claim task → `bot` (is_working=true), returns full context + parent context + fileContext |
-| `deskfree_update_file` | Update a linked file's content incrementally |
-| `deskfree_create_file` | Create a new persistent file |
-| `deskfree_complete_task` | Mark done (summary required) or blocked → `human` |
-| `deskfree_send_message` | Message in task thread (content required) |
-| `deskfree_claim_evaluation` | Claim a pending evaluation — returns task, messages, globalWoW, and initiative (if applicable) |
-| `deskfree_submit_evaluation` | Submit evaluation with dual output: globalWoW + initiative (each independently updatable) |
-
-### Worker (7 tools — sub-agents only)
-
-`deskfree_update_file`, `deskfree_create_file`, `deskfree_complete_task`, `deskfree_send_message`, `deskfree_suggest_tasks`, `deskfree_claim_evaluation`, `deskfree_submit_evaluation`
-
-Workers receive workspace context at spawn time — use it to understand what else is happening, avoid duplicate suggestions, and link follow-ups to existing initiatives.
-
----
-
-## File Best Practices
-
-### Markdown files
-
-Structure as **standalone markdown documents:**
-
-```markdown
-# Document Title
-
-## Summary
-Brief overview of what this document covers.
-
-## Key Findings / Content
-- Main points with supporting detail
-
-## Details
-Detailed analysis, implementation notes, etc.
-
-## Next Steps (if applicable)
-- Follow-up actions, outstanding questions
-```
-
-### HTML files
-
-Pass a complete, self-contained HTML document (or fragment — a wrapper `<html>` is injected automatically):
-
-```html
-<h1>Report Title</h1>
-<table>
-  <tr><th>Metric</th><th>Value</th></tr>
-  <tr><td>Users</td><td>1,234</td></tr>
-</table>
-```
-
-**Build incrementally** — start with outline immediately after `deskfree_start_task`, fill sections as you go, polish before completing. A half-complete file is infinitely better than none.
+1. `deskfree_state` → check existing tasks + initiatives + files
+2. `deskfree_propose` → with context, substeps, file links, initiative
+3. Human approves → spawn sub-agent → `deskfree_start_task`
+4. Work → `deskfree_update_file` incrementally
+5. `deskfree_complete_task`
 
 ---
 
 ## Error Handling
 
-| Error | Cause | Action |
-|---|---|---|
-| `deskfree_state` returns empty | No tasks exist | Create a task if appropriate. **Do NOT retry in a loop.** |
-| 404 on `deskfree_start_task` | Task not `bot` or doesn't exist | Another bot claimed it. Call `deskfree_state`, try a different task. |
-| 404 on `deskfree_complete_task` | Task not `bot` (is_working=true) | Already completed or released. Check state. |
-| 409 on `deskfree_start_task` | Race condition — another bot claimed it | Call `deskfree_state`, pick a different task. |
-| 401 Unauthorized | Bot token invalid or expired | Check channel configuration. Do not retry. |
-| `deskfree_update_file` fails | File not found or network error | Verify fileId with `deskfree_state`. If file was deleted, create a new one. |
-| 422 on `deskfree_complete_task` | Missing required `summary` for outcome `done` | Add a meaningful summary of what was accomplished. |
-| `deskfree_claim_evaluation` returns null | Already claimed by another process | No action needed. Move to next pending evaluation. |
-| Sub-agent spawn fails | Resource limits, config error | Complete task as `blocked` with explanation. Do not leave in `bot` (is_working=true). |
-| WebSocket disconnected | Network issue | Plugin auto-reconnects with backoff. Messages fall back to HTTP polling. No action needed. |
-
-### Recovery Pattern
-
-If anything goes wrong mid-task:
-1. Send a message explaining what happened (`deskfree_send_message`)
-2. Save whatever partial file content you have (`deskfree_update_file`)
-3. Complete as `blocked` (`deskfree_complete_task` with outcome `blocked`)
-4. **Never leave a task stranded in `bot` (is_working=true)**
-
-### Edge Cases & Advanced Scenarios
-
-| Scenario | Guidance |
+| Error | Action |
 |---|---|
-| **Concurrent task access** | If multiple bots try to claim the same task, one will get 409 Conflict. The winner proceeds, losers should call `deskfree_state` and pick different tasks. |
-| **Long-running operations** | For tasks >10 minutes, send periodic progress updates via `deskfree_send_message` so humans know you're still working. Update file incrementally. |
-| **Partial file recovery** | If interrupted mid-work, `deskfree_start_task` returns the current file content in `fileContext`. Resume from where you left off, don't start over. |
-| **Network timeouts during updates** | If `deskfree_update_file` times out, retry once. If it fails again, complete as `blocked` with the timeout explanation. |
-| **Empty or corrupt file content** | Always validate file content before calling `deskfree_update_file`. Minimum viable content is better than empty/corrupted content. |
-| **Sub-agent coordination** | Only one sub-agent per task. If a sub-agent fails to start, the main session should resume the task directly. Don't spawn multiple sub-agents for the same task. |
-| **Evaluation claim conflicts** | `deskfree_claim_evaluation` returns `null` if another process claimed it first. This is normal - move to the next pending evaluation or complete your heartbeat. |
-| **Ways of working too large** | If ways of working content becomes very large (>50KB), consider archiving old sections. Focus updates on recent patterns and current best practices. |
-
-### Troubleshooting Common Issues
-
-#### "Task not found" (404) Errors
-- **Cause**: Task was claimed by another bot, completed, or deleted
-- **Solution**: Always call `deskfree_state` first to see available tasks
-- **Prevention**: Check task status in state before attempting operations
-
-#### Auto-threading Not Working
-- **Cause**: No active task context, or called `deskfree_complete_task` already
-- **Solution**: Pass explicit `taskId` to `deskfree_send_message`
-- **Debug**: Check that `deskfree_start_task` was called and returned successfully
-
-#### File Updates Failing
-- **Common causes**:
-  - File ID is wrong or file was deleted → call `deskfree_state` to see current files
-  - File content is malformed (invalid markdown, control characters)
-  - Network timeout → retry once, then complete as blocked if persistent
-- **Solution**: Validate content before sending, handle network errors gracefully
-
-#### Sub-agent Spawn Failures
-- **Common causes**: Resource limits, configuration errors, invalid task context
-- **Immediate action**: Main session should resume the task directly
-- **Recovery**: Complete task as `blocked` only if you cannot resume the work yourself
-
-#### Ways of Working Updates Not Applying
-- **Cause**: Another evaluation process updated it first, or `hasChanges=false` was sent
-- **Check**: Ensure `hasChanges=true` and `updatedContent` is provided when you intend to update
-- **Conflict resolution**: If content conflicts occur, the last successful submission wins
-
-#### "State returns empty" Issues
-- **Not an error**: Empty state means no tasks exist - this is normal
-- **Action**: Create a task if you have work to do, otherwise return `HEARTBEAT_OK`
-- **Don't**: Retry `deskfree_state` in a loop - it's not broken
-
----
-
-## Common Workflow Patterns
-
-### Pattern 1: Research & Analysis with File Output
-
-```
-Main Session:
-1. deskfree_state()                    → check workspace + files
-2. deskfree_suggest_tasks([{
-     title: "Research competitor HumanLayer",
-     instructions: "Analyze their product, pricing, and positioning vs DeskFree",
-     newFile: { name: "HumanLayer Analysis", description: "Competitor analysis report" }
-   }])
-3. [human approves task]
-4. deskfree_start_task(taskId)         → get task context + fileContext (empty file pre-created)
-5. spawn_subagent(research_prompt)     → background research
-
-Sub-agent:
-1. deskfree_update_file(fileId, "# HumanLayer Analysis\n\n## Summary\n...")   → initial outline
-2. [research work...]
-3. deskfree_update_file(fileId, "...")  → interim findings
-4. [more research...]
-5. deskfree_update_file(fileId, "...")  → final report
-6. deskfree_complete_task(taskId, "done", summary: "Analysis complete — 3 key differentiators identified, full report in file")
-```
+| 404 on `start_task` | Task not pending or doesn't exist. Call `deskfree_state`, try another. |
+| 409 on `start_task` | Already claimed. Call `deskfree_state`, pick a different task. |
+| Empty `deskfree_state` | No tasks exist. Propose if appropriate. **Don't retry in a loop.** |
 
-### Pattern 2: Quick Fix (Main Session, No File)
+### Recovery
 
-```
-1. deskfree_state()                    → check current state
-2. deskfree_suggest_tasks([{
-     title: "Fix broken login endpoint",
-     instructions: "Apply hotfix for 500 error in /auth/login"
-   }])
-3. [human approves task]
-4. deskfree_start_task(taskId)         → claim the work
-5. [fix the code...]
-6. deskfree_complete_task(taskId, "done", summary: "Fixed null pointer in auth middleware, deployed to staging")
-```
-
-### Pattern 3: Blocked Task with Human Input
-
-```
-1-5. [normal task startup...]
-6. [encounter blocker - need API key]
-7. deskfree_send_message("Need the new Stripe API key to complete this integration. Where can I find it?")
-8. deskfree_update_file(fileId, "...")  → save partial progress if task has a file
-9. deskfree_complete_task(taskId, "blocked")  → hand off to human
-```
-
-### Pattern 4: Ways of Working Evaluation
-
-```
-Heartbeat check:
-1. deskfree_state()                    → shows pendingEvaluations: [{taskId: "abc", ...}]
-2. deskfree_claim_evaluation("abc")    → get evaluation context (task, messages, waysOfWorking, initiative?)
-3. [analyze task summary, messages, current ways of working, initiative if present...]
-4. deskfree_submit_evaluation({
-     taskId: "abc",
-     reasoning: "Found a new pattern for API error handling...",
-     globalWoW: {
-       hasChanges: true,
-       updatedContent: "# Ways of Working\n\n## API Integration\n[new section]..."
-     },
-     initiative: { hasChanges: false }
-   })
-```
-
-## Task Title Examples
-
-**Good (short, scannable, action-oriented):**
-- "Research competitor HumanLayer"
-- "Deploy staging hotfix"
-- "Write API docs for /users endpoint"
-- "Debug memory leak in worker process"
-- "Review Q3 performance metrics"
-
-**Bad (verbose, unclear):**
-- "Do some research on a competitor called HumanLayer and write up findings"
-- "There's a bug in staging that needs fixing"
-- "I need to check on some performance stuff for the quarterly review"
-
----
-
-## Best Practices & Anti-Patterns
-
-### ✅ Do This
-
-| Practice | Rationale | Example |
-|---|---|---|
-| **Update file early and often** | Shows progress, survives interruptions | Update outline immediately, add sections as you work |
-| **Use descriptive commit-style titles** | Easy to scan, actionable | "Fix authentication timeout in Safari" |
-| **Send progress messages for long tasks** | Humans know you're working | "25% complete - analyzed 3 of 12 competitor features" |
-| **Complete blocked tasks with explanation** | Clear handoff to humans | Message: "Need AWS credentials", then complete as blocked |
-| **Start with template file structure** | Consistent structure, never empty | Use the markdown template every time |
-| **Handle 404/409 gracefully** | Race conditions are normal | Check state and pick different task, don't retry same task |
-| **Provide meaningful summary on done** | Humans see this first | "Wrote full API docs for /users endpoint — 12 methods documented" |
-
-### ❌ Don't Do This
-
-| Anti-Pattern | Why It's Bad | Instead |
-|---|---|---|
-| **Leave tasks in `bot` (is_working=true)** | Blocks the workspace indefinitely | Always complete as `done` or `blocked` |
-| **Retry `deskfree_state` in loops** | Wastes resources, indicates logic error | Call once per decision point |
-| **Start multiple sub-agents per task** | Creates confusion, race conditions | One sub-agent per task maximum |
-| **Update file only at the end** | Progress lost if interrupted | Update incrementally throughout work |
-| **Ignore 409 conflicts on task claims** | Causes infinite retry loops | Accept conflict, check state, pick different task |
-| **Create tasks without clear actions** | Unclear what needs doing | Use imperative verbs: "research X", "fix Y", "analyze Z" |
-| **Send messages instead of completing blocked** | Task stays in limbo | Send message explaining blocker, then complete as blocked |
-| **Complete "done" without a summary** | Human can't quickly understand outcome | Always provide a 1-3 sentence summary of what was accomplished |
-
-### Common Gotchas
-
-- **Auto-threading stops after `deskfree_complete_task`** → Pass explicit `taskId` for post-completion messages
-- **Empty file content is not useful** → Always provide meaningful content, even if just an outline
-- **Sub-agents can't create tasks** → Only orchestrator (main session) can create and claim tasks
-- **Ways of working updates require `hasChanges=true`** → Explicitly set flag when submitting changes
-- **Task titles are visible to humans** → Make them professional and descriptive
-- **Evaluation reasoning is important** → Explain your analysis even if no changes are made
-- **summary is required for outcome "done"** → Plan what you'll write before completing
-
-## Human Review Outcomes
-
-- **Approve** → task moves to `done`. Creates pending evaluation for ways-of-working update.
-- **Decline / request changes** → task returns to `bot` with feedback. Restart it.
+If anything goes wrong mid-task:
+1. `deskfree_send_message` — explain what happened
+2. `deskfree_update_file` — save partial content
+3. `deskfree_complete_task` with outcome `blocked`
+4. **Never leave a task stranded in `active`**