Skip to content

Work Buddy Knowledge Handbook

This documentation is auto-generated from the knowledge store.

209 units across 4 types:

  • capability: 113
  • directions: 38
  • system: 44
  • workflow: 14

Architecture

  • Architecture & Repo Structure system — Repository layout, subsystem organization, and development conventions
  • Contracts system — Explicit work commitments — schema, lifecycle, bounded deliverables
  • Knowledge System system — Unified agent self-documentation — typed units, DAG hierarchy, full-content search index with BM25 + dense embeddings
  • MCP Server Import Discipline system — Critical safety constraint: why heavy library imports in capability callables deadlock the MCP server, and the correct pattern to avoid it
  • Repository Structure system — Directory layout — what lives where, with subsystem README pointers
  • Retry Queue system — Background retry system for transient operation failures — sidecar sweep, error classification, adaptive backoff, workflow DAG integration
  • Workflow System system — Workflow execution — DAG, execution policy, auto-run steps, conductor, step result visibility

Browser

  • Browser system — Browser capabilities and workflows
  • Chrome Triage workflow — Triage currently-open Chrome tabs through a four-tier pipeline:
  • Chrome Triage Directions directions — How to run Chrome tab triage — pipeline overview, agent role (validate Sonnet's groups), available actions

Context

  • Context system — Context capabilities and workflows
  • Chrome Activity capability — Query Chrome browsing history from the rolling tab ledger. Supports: hot_tabs (ranked by engagement), changes (opened/closed/navigated/engaged/moved), sessions (domain clusters), tabs_at (snapshot at a time), context (tab proximity and window layout), details (full URLs by filter), status (ledger health). Output is compact (no URLs) — use details query for full URLs.
  • Chrome Cluster capability — Cluster currently-open Chrome tabs by semantic similarity. Extracts page content, embeds with document-tower model, and clusters via Louvain. Completely free — no LLM calls. Returns tab groups with cohesion scores. Set use_content=false for title-only clustering (faster, works when extension can't extract).
  • Chrome Content capability — Extract full page text from currently-open Chrome tabs. Filter by domain or title substring, or get top-engagement tabs. Free — no LLM calls. Use for single-tab inspection or reading specific page content.
  • Chrome Infer capability — Infer what the user is working on by reading page content from engaged Chrome tabs and analyzing with Haiku. Evaluates provided theories against actual page evidence. Caches results per tab to avoid redundant API calls. ~$0.001/call.
  • Chrome Tab Close capability — Close specified Chrome tabs by tab ID. Returns count of closed/missing tabs. Use after triage decisions.
  • Chrome Tab Group capability — Create a Chrome tab group or add tabs to an existing group. Returns the group ID.
  • Chrome Tab Move capability — Move Chrome tabs to a specific position or window.
  • Collect And Orient workflow — Generate a fresh context bundle and use it to orient on the user's current work state. This is the primary "what's going on right now?" workflow.
  • Context Collection Directions directions — How to collect context and synthesize an orientation — priority order, flags, contract cross-reference
  • Context Review Directions directions — How to review an existing context bundle — freshness check, same synthesis rules as context-collect, no re-collection
  • Context Bundle capability — Run all (or selected) collectors and save a context bundle to disk. Use individual collectors (context_git, context_chat, etc.) when you only need one source.
  • Context Calendar capability — Google Calendar schedule for a given date. Also checks plugin readiness.
  • Context Chat capability — Recent Claude Code conversations and CLI history with tool usage, duration, and outcome snippets
  • Context Chrome capability — Currently open Chrome tabs (requires Chrome extension running)
  • Context Git capability — Recent git activity across all repos: commits, diffs, dirty trees. Pass annotate=true to tag commits made by agent sessions with their session ID.
  • Context Messages capability — Inter-agent messaging state: pending, recent, unread messages
  • Context Obsidian capability — Obsidian vault summary: journal entries, recently modified notes
  • Context Projects capability — Active projects with identity, state, and trajectory — synthesized from vault directories, STATE.md files in repos, task tags, git activity, and contracts
  • Context Search capability — Search indexed content (conversations, documents, tabs). Requires IR index — build with ir_index first. Methods: 'substring' (exact match, no embedding service), 'keyword' (BM25), 'semantic' (dense), or comma-delimited combo like 'keyword,semantic' (default, RRF fused).
  • Context Smart capability — Smart Connections context: semantically related notes to active contracts
  • Context Tasks capability — Obsidian task summary: outstanding tasks + recent state changes (last 48h by default)
  • Context Wellness capability — Wellness tracker summary from recent journal entries
  • Datacore Compile Plan capability — Compile a structured JSON query plan into a Datacore query string. Plan keys: target (required), path, tags, tags_any, status, text_contains, exists, frontmatter, child_of, parent, expressions, negate.
  • Datacore Evaluate capability — Evaluate a Datacore expression (e.g. arithmetic, field access).
  • Datacore Fullquery capability — Execute a Datacore query with timing and revision metadata. Same as datacore_query but includes duration_s and revision.
  • Datacore Get Page capability — Get a single vault page by path with Datacore metadata: frontmatter, sections, tags, links, timestamps.
  • Datacore Query capability — Execute a Datacore query against the vault index. Supports @page, @section, @block, @task, @list-item, @codeblock with filters like path(), tags, childof(), parentof(). Returns serialized results.
  • Datacore Run Plan capability — Compile and execute a structured query plan in one step. Preferred over raw datacore_query when building queries programmatically — the plan schema is simpler and validates before execution.
  • Datacore Schema capability — Summarize the vault's Datacore schema: object types, top tags, frontmatter keys, path prefixes. Use before building queries to understand what's available.
  • Datacore Status capability — Check if Datacore plugin is installed, initialized, and queryable. Returns version, index revision, and object type counts.
  • Datacore Validate capability — Validate a Datacore query string without executing it. Returns parse error details if invalid.
  • Ir Index capability — Build or check the IR search index. Run 'build' to index conversations for semantic search. Run 'status' to check index health.
  • Review Latest Bundle workflow — Read the most recent existing context bundle without re-collecting. Faster than collect-and-orient when a recent bundle already exists.
  • Session Find Uncommitted directions — How to invoke and present uncommitted session results — per-entry format and follow-up suggestion
  • Session Commits capability — Extract git commits made during Claude Code sessions. Parses raw JSONL for Bash tool calls containing 'git commit' and their results. Scope to one session or scan all recent sessions.
  • Session Expand capability — Full context around a specific message in a session. Returns untruncated text for the target and surrounding messages.
  • Session Get capability — Browse messages in a Claude Code session. Paginated with role/type filtering. Use after context_search finds a session.
  • Session Locate capability — Jump from a context_search hit to the relevant conversation page. Takes a span_index from search result metadata and returns messages centered on that chunk.
  • Session Search capability — Hybrid search within a single session. Uses IR (keyword/semantic/substring) scoped to the session, then resolves chunk hits to message-level results via the span map.
  • Session Uncommitted capability — Find agent sessions that wrote files still present in dirty git state. Answers: 'which sessions wrote code that was never committed?' Cross-references Write/Edit/NotebookEdit tool calls against git status --porcelain across all repos.
  • Session Wb Activity capability — Summary of what a session did through work-buddy's MCP gateway — capabilities invoked, workflows run, errors, key artifacts. Reads from the per-session activity ledger.
  • Session Inspection system — Random-access into individual Claude Code conversation sessions — browsing, search, context expansion, git commit extraction
  • Triage Execute capability — Execute triage decisions from the review view. Takes the user's Phase 2 response (group_decisions, reassignments) and the original presentation, then performs all actions: close tabs, create tasks, record into tasks, organize tab groups.
  • Triage Item Detail capability — Retrieve the Haiku summary and/or raw content for a specific triage item. Use during triage review to inspect items with content gaps. Works for any source (Chrome tabs, journal entries, conversations). Requires a prior triage pipeline run.

Contracts

  • Contracts system — Contracts capabilities and workflows
  • Active Contracts capability — List all contracts with status=active
  • Analyze Contracts workflow — Review all active contracts, check health, and surface issues for the user.
  • Contract Check Directions directions — How to analyze contracts — health flags, alignment check, per-contract next actions, blindspot cross-reference
  • Contract Creation Directions directions — How to guide contract creation — interview flow, minimum viable fields, scope checking, WIP awareness, confirmation rules
  • Contract Constraints capability — Get active contracts with their current bottleneck constraints
  • Contract Health capability — Health check report: status counts, overdue, stale, missing fields
  • Contract Wip Check capability — Check if active contract count is within the WIP limit (max 3)
  • Contracts Summary capability — Markdown summary of all contracts with title, status, deadline, progress
  • Create Contract workflow — Guide the user through defining a new contract for a bounded deliverable.
  • Overdue Contracts capability — List contracts past their deadline
  • Stale Contracts capability — List contracts not reviewed in N days (default 7)

Daily Journal

  • Daily Journal system — Daily Journal capabilities and workflows
  • Journal Backlog Processing Directions directions — How to run Running Notes backlog pipeline — cluster review, routing proposals, rewrite presentation
  • Process Backlog workflow — Orchestrates the full backlog processing pipeline: segment Running Notes into threads, route each thread to its destination with user confirmation, and rewrite Running Notes with only the items that remain open.
  • Segment Notes workflow — Read the Running Notes section from a journal file, identify coherent threads of related content, and annotate the text with inline thread IDs. The raw text is never modified — only HTML comment tags are inserted.
  • Update Journal workflow — Append activity-detected Log entries to an Obsidian journal file.

Dev

  • Development system — Developmental mode — tools and directions for building, debugging, and modifying work-buddy itself
  • Work-Buddy Commit directions — Commit with test verification, knowledge doc hygiene, PII check, branch management, push + PR creation, and structured metadata recording via commit_record
  • MCP Gateway Design Tenets directions — Five architectural principles for designing capabilities, plus the priming hazard and agentic stub patterns for workflow authoring
  • Development Mode directions — Enter developmental agent mode — orient on architecture, key locations, and dev workflow for modifying work-buddy itself
  • Documentation Architecture directions — Where system documentation lives, what is canonical vs legacy, and how to make documentation changes
  • MCP Registry Reload directions — Reload the MCP gateway capability registry without restarting the server to pick up code changes
  • Obsidian Plugin Integration directions — Build a new Obsidian plugin integration for work-buddy — probe, wrap, package, and optionally collect
  • Session Retrospective directions — Switch to developmental mode and critique/debug this session's execution — then fix what you find

Journal

  • Journal system — Journal capabilities and workflows
  • Activity Timeline capability — Infer recent activity from journal entries and optionally deeper signals. Returns a structured timeline with events, gaps, and relative timestamps. Use for understanding what happened during a time window.
  • Day Planner capability — Day Planner operations: check plugin status, read current plan, generate schedule from events+tasks, or write plan to journal. Composite: replaces separate check_ready/get_plan/generate/write/resync calls.
  • Hot Files capability — Rank vault files by activity intensity, fusing modification frequency (vault events) with writing intensity (Keep the Rhythm). Hierarchically collapses busy directories to prevent context flooding. Use sub_directory to drill into a specific area.
  • Journal Sign In capability — Read sign-in state (sleep/energy/mood/check-in/motto) and wellness trends, optionally write fields. Composite: replaces separate extract_sign_in + interpret_wellness + write_sign_in calls.
  • Journal State capability — Read journal state: target date, activity window, existing entries
  • Journal Write capability — Append log entries or persist a briefing to the journal. For log entries: pass time/description tuples. For briefing: pass markdown to wrap in a callout.
  • Running Notes capability — Read the Running Notes section from the user's daily journal. This is the primary stream-of-consciousness capture zone where the user records ideas, observations, and notes throughout the day. Supports filtering by date range, last N days, or same-day only. Call with same_day=true for just today's entries, or days=N for recent history.
  • Journal Update Directions directions — How to detect activity and append journal Log entries — format, synthesis rules, approval flow
  • Vault Write At Location capability — Insert content at a specific section in a vault note. Configurable note (path or resolver like 'latest_journal', 'today'), section (header text), and position ('top' or 'bottom' of section). Used by Telegram capture and general-purpose vault writing.

Memory

  • Memory system — Memory capabilities and workflows
  • Memory Prune capability — Delete memories from the bank. CONSENT-GATED, IRREVERSIBLE. Call with no args to list documents for review. Then provide document_id to delete a specific document's memories, or memory_type to bulk-delete a category (world/experience/observation).
  • Memory Read capability — Read from personal memory (Hindsight). No LLM cost. Modes: 'search' (default) — semantic + keyword recall, use descriptive topic phrases with specific entity names for best results; 'model' — fetch a mental model by ID; 'recent' — list latest memories.
  • Memory Reflect capability — LLM-powered reasoning over memories. CONSENT-GATED: triggers a server-side LLM call against your Anthropic API key (~1-3K tokens per call). Use memory_read for free retrieval first.
  • Memory Write capability — Store a personal fact, preference, or constraint in memory

Messaging

  • Messaging system — Messaging capabilities and workflows
  • Get Thread capability — Get all messages in a conversation thread
  • Query Messages capability — Query messages by recipient, sender, status, or limit
  • Read Message capability — Fetch a single message with full body content
  • Reply To Message capability — Reply to an existing message
  • Send Message capability — Send a message to another agent or project
  • Update Message Status capability — Update a message's status (e.g., pending → resolved)

Metacognition

  • Metacognition system — Metacognition capabilities and workflows
  • Blindspot Detection Directions directions — How to scan for active blindspot patterns — pattern table, intervention levels, cascade checking, rewriting template

Morning

  • Morning Routine system — Configurable morning routine — journal, tasks, contracts, calendar, metacognition
  • Morning Routine Directions directions — How to run the morning routine — sign-in conversation, blindspot scan, synthesis, plan-today, quality checks
  • Morning Routine workflow — Configurable morning routine that coordinates journal, tasks, contracts, calendar, and metacognition into a single briefing-first flow. Collect everything, then synthesize and act.

Notifications

  • Notification & Consent System system — Multi-surface notifications, requests, and consent — Obsidian, Telegram, Dashboard
  • Consent System directions — How consent-gated operations work — auto-request in gateway, pre-flight bundling, session scope, risk levels
  • Consent Grant capability — LOW-LEVEL: Direct consent grant for deferred resolution ONLY. Do NOT use this to bypass the consent flow — use consent_request instead, which notifies the user and waits for their approval. This capability exists for: (1) manual resolution after a consent_request timeout when the user later approves out-of-band, (2) programmatic grants from surface callbacks. All grants are session-scoped. Modes: 'always' (24h), 'temporary' (TTL-based), 'once' (single-use).
  • Consent List capability — List all consent entries with their status (mode, tier, expiry for temporary grants).
  • Consent Request capability — One-call consent flow: create a consent request, deliver to all available surfaces, and optionally poll + auto-resolve. The modal shows Allow always / Allow for N min / Allow once / Deny options. Without timeout_seconds: non-blocking (returns request_id for later polling via request_poll + consent_request_resolve). With timeout_seconds: blocks until user responds, then auto-resolves (writes the grant on approval, returns denial on deny). Max recommended timeout: 110s to stay within MCP limits.
  • Consent Request List capability — List all pending (unresolved) consent requests.
  • Consent Request Resolve capability — Approve or deny a pending consent request. If approved, writes the grant and dispatches the callback (session resume or messaging).
  • Consent Revoke capability — Revoke a previously granted consent for an operation.
  • Notification List Pending capability — List all pending notifications and requests awaiting user response.
  • Notification Send capability — Send a fire-and-forget notification to the user via all available surfaces (Obsidian, Telegram if enabled). No response expected. Optionally target specific surfaces.
  • Sending Notifications directions — How to send fire-and-forget notifications — parameters, surface rendering, and examples
  • Sending Requests and Consent directions — How to request user decisions — request_send, consent_request, surface rendering, blocking vs non-blocking, and handling responses
  • Request Poll capability — Check/wait for a response to a previously delivered request. Without timeout_seconds: single immediate check. With timeout_seconds: blocks until response or timeout (max recommended: 110s). Response is cleared from Obsidian after reading (one-shot).
  • Request Send capability — Create a request, deliver to all available surfaces, and optionally poll for the user's response. Supports choice, boolean, freeform, and range response types. Without timeout_seconds: non-blocking (returns immediately, use request_poll later). With timeout_seconds: blocks until response or timeout (max recommended: 110s to stay within MCP call limits).
  • Notification Surfaces system — Surface details — Obsidian modals, Telegram messages, Dashboard forms
  • Telegram Bot system — Telegram bot for mobile access — commands, setup, architecture

Obsidian

  • Obsidian Integration system — Obsidian vault integration — bridge, tasks, datacore, smart connections, vault writer
  • Obsidian Bridge system — HTTP bridge to Obsidian — eval_js, latency handling, timeout retry rules
  • Google Calendar Integration system — Google Calendar access via Obsidian Google Calendar plugin (stale/unmaintained) + eval_js bridge
  • Datacore Query Directions directions — How to translate user intent into Datacore vault queries — schema-first, decomposition, plan vs raw query, validate-and-repair
  • Day Planner Plugin Integration system — Obsidian Day Planner plugin (v0.28.0) integration -- plan entry format, settings, runtime surface
  • Keep the Rhythm Integration system — Writing activity tracking via KTR plugin (v0.2.8) -- per-file word/char deltas in 5-minute buckets
  • Smart Connections Ecosystem system — Smart Plugins ecosystem (9 plugins, Pro license) -- SmartEnv runtime, embedding, semantic search, memory pressure
  • Tag Wrangler Integration system — Tag operations via Tag Wrangler plugin (v0.6.4) + metadataCache -- read, rename, merge, tag pages
  • Obsidian Tasks Plugin Integration system — Runtime integration with Tasks plugin (v7.23.1) -- cache API, ownership split, mutation pipeline, tag behavior
  • Vault Event Tracking system — Event-driven file change tracking for Obsidian -- replaces O(n) mtime scanning, persists in localStorage
  • Vault Location Writer system — Section-aware vault writing — insert content at specific locations in notes

Operations

  • Operations system — How to operate work-buddy — MCP gateway, sessions, Python environment
  • Agent Sessions system — Session ID setup, agent directories, Python conda environment, and Poetry dependency management
  • MCP Gateway directions — How to discover and call MCP gateway capabilities — the primary interface for agents

Projects

  • Projects system — Project registry — identity, observations, memory, discovery, and lifecycle
  • Deleting a Project directions — Pre-flight steps before deleting a project — confirm slug, explain impact, then call
  • Discovering Project Candidates directions — How to evaluate and triage project_discover candidates — create, alias, or ignore
  • Listing Projects directions — How to list and present projects — grouping by status, detail drill-down via project_get
  • Creating a Project directions — Parameter defaults, slug rules, when to ask vs infer, and post-creation ritual for project_create
  • Recording Project Observations directions — What makes a good observation, slug disambiguation, and existence prerequisite for project_observe
  • Project Create capability — Manually create a project that the collector can't discover (books, businesses, admin workflows, etc.)
  • Project Delete capability — Delete a project from the identity registry (consent-gated). Hindsight memories are preserved.
  • Project Discover capability — Discover project candidates from task tags and git repos not yet in the registry. Returns candidates for agent review — evaluate each and use project_create to promote real projects.
  • Project Get capability — Get a single project with its recent observations (identity + state + trajectory)
  • Project List capability — List all projects with observation counts, optionally filtered by status
  • Project Memory capability — Read from the project memory bank (Hindsight-backed). Modes: 'search' (semantic recall, optionally scoped to one project), 'model' (fetch a mental model: project-landscape, active-risks, recent-decisions, inter-project-deps), 'recent' (latest project memories)
  • Project Observe capability — Record an observation about a project — strategic decisions, supervisor feedback, pivots, blockers, or anything that shapes trajectory but wouldn't appear in code or tasks
  • Project Update capability — Update a project's identity: name, status, or description

Routing

  • Routing system — Routing capabilities and workflows
  • Route Information workflow — Given a batch of discrete information items (each with an ID, raw text, and optional agent-proposed metadata), present routing recommendations to the user in clusters, get confirmation or correction, and execute the approved routings.

Services

  • Services & Infrastructure system — Sidecar-managed services — dashboard, messaging, embedding, and service pointers
  • Dashboard system — Web dashboard for system observability — Flask service, dev mode, remote access, development rules
  • Hindsight Memory system — Persistent personal memory layer via Hindsight — semantic search, mental models, retention
  • Inter-Agent Messaging system — Inter-agent messaging service for cross-session communication
  • Sidecar Daemon system — Unified process supervisor, cron scheduler, and message-driven job dispatcher

Status

  • Status system — Status capabilities and workflows
  • Feature Status capability — Show which tools, features, and capabilities are available or disabled, and why. Use this to diagnose missing integrations.
  • List Sessions capability — List all known agent sessions with metadata
  • Llm Call capability — Make a single LLM API call (Tier 2 execution). Cheaper than spawning a full agent session. Supports freeform text or structured JSON output via output_schema (inline dict or named schema from work_buddy/llm/schemas/). Handles caching, cost tracking, and model tier selection automatically.
  • Llm Costs capability — Check LLM token usage, costs, and breakdown for this session. Shows per-task costs, per-model costs, cache hit rates, and top callers.
  • Mcp Registry Reload capability — Invalidate and rebuild the capability registry. Use after code changes to pick up new capabilities without restarting the MCP server.
  • Remote Session Begin capability — Launch or resume a visible Claude Code session in a real terminal window. If session_id or session_name is provided, resumes that session; otherwise starts a new one. Designed for Remote Control (phone app) connection.
  • Remote Session List capability — List resumable Claude Code sessions from ~/.claude/sessions/. Shows session ID, name, cwd, and start time.
  • Service Health capability — Check if the messaging service is running
  • Session Activity capability — Query the session activity ledger — what this agent session has done through work-buddy. Filters by event type, capability, category, status. Returns last N matching entries (newest first).
  • Session Summary capability — Compact summary of what this agent session has done — counts by category/capability, errors, mutations, key artifacts created, workflow progress.
  • Setup Help Directions directions — How to present component health diagnostics — structured output format, lead with the fix
  • Setup Help capability — Diagnose why a component isn't working. Runs automated check sequences that walk dependency chains and stop at the first failure with a root cause and fix suggestion. Use 'all' for an overview of all components, or specify a component ID (e.g. 'hindsight', 'obsidian', 'postgresql') for targeted diagnostics.
  • Sidecar Jobs capability — List all scheduled sidecar jobs with their next fire time, heartbeat status, and whether exclusion windows are active.
  • Sidecar Status capability — Check if the sidecar daemon is running and get its current state: supervised services health, scheduler status, and upcoming job schedule.
  • Tailscale Status Directions directions — Check Tailscale VPN status — daemon state, tailnet identity, online peers, Serve config
  • Tailscale Status capability — Check Tailscale VPN status: daemon state, tailnet identity, online peers, and Serve configuration (published ports).

Tasks

  • Tasks system — Tasks capabilities and workflows
  • Task Assign Directions directions — How to assign a task — presentation format, completion tracking, state change protocol
  • Task Briefing Directions directions — How to present the daily task status summary — concise format, required sections, one next action
  • Task Handoff Directions directions — How to write a structured session handoff prompt and package it as a task note
  • Inline Todos workflow — Find #wb/TODO markers across the vault, present them for triage, execute the freeform instructions, and clean up handled tags.
  • Inline TODOs Directions directions — How to triage and execute #wb/TODO vault markers — batch presentation, execution rules, tag cleanup
  • Task Creation Directions directions — How to create a task with minimal prompting and correct inference
  • Scattered Tasks Directions directions — How to present scattered task results and triage into action categories
  • Task Triage workflow — Interactive inbox review: surface tasks that need decisions, collect user input, apply state changes.
  • Task Archive capability — Move completed tasks from master list to tasks/archive.md
  • Task Assign capability — Claim a task for the current session and get full context (text, note, metadata)
  • Task Briefing capability — Daily task status summary with contract constraints, MITs, focused, overdue, stale, suggestions
  • Task Change State capability — Update task metadata: state, urgency, due date (any combo)
  • Task Create capability — Create a new task in the master task list. Optionally attach a note file for details/subtasks.
  • Task Delete capability — Permanently delete a task: remove line, note file, and store record. Consent-gated.
  • Task Review Inbox capability — Get inbox tasks with suggested actions (mit, snooze, kill, needs_date)
  • Task Scattered capability — Find open tasks scattered across the vault outside the master task list. Groups by file with counts. Uses Datacore structural queries.
  • Task Stale Check capability — Find forgotten/stale tasks across inbox, snoozed, MIT, and focused
  • Task Sync capability — Compare master task list against SQLite store: detect orphans, create missing store records, report checkbox mismatches
  • Task Toggle capability — Toggle a task between TODO and DONE (checkbox, done date, store state). Consent-gated.
  • Task Triage Directions directions — How to run interactive task triage — presentation rules, actions, summary format
  • Weekly Review workflow — Agentic weekly planning session. The agent assembles the strategic picture,
  • Weekly Review Directions directions — How to run the weekly task review — MIT drafting, WIP enforcement, constraint validation
  • Weekly Review Data capability — Gather all data for the weekly review: contracts, constraints, WIP, tasks, staleness, suggestions

Testing

  • Testing system — Testing capabilities and workflows
  • Stress Test workflow — Subprocess isolation validation workflow. The compute-primes step runs

Threads

  • Threads system — Threads capabilities and workflows
  • Thread Management Directions directions — When and how to use conversation threads — decision guide, response types, behavioral notes
  • Thread Ask capability — Ask a question in a thread and optionally wait for the user's response.
  • Thread Close capability — Close a conversation thread.
  • Thread Create capability — Create a new conversation thread with the user. Opens a chat sidebar on the dashboard.
  • Thread List capability — List conversation threads.
  • Thread Poll capability — Check if the latest question in a thread has been answered.
  • Thread Send capability — Send a message in an existing thread (fire-and-forget, no response expected).