Skip to content

MCP Server Reference

The MCP server exposes 114 tools from the live registry.

The current registry contains 114 tools (107 in the core allTools registry plus 7 runtime task tools).

CategoryCountDescription
Core WU Operations7Context and primary WU lifecycle operations.
Extended WU Lifecycle19WU maintenance, recovery, prep, and cleanup flows.
Initiatives8Initiative planning, assignment, and status operations.
Memory14Session memory, checkpoints, recovery, and coordination flows.
Agent4Agent session lifecycle and issue capture operations.
Orchestration & Delegation4Initiative orchestration, monitoring, and delegation helpers.
Flow & Metrics5Flow analysis and metrics tooling.
Validation5Validation and health-check operations.
Setup & Bootstrap16Initialization, onboarding, and environment setup flows.
Parity & Utilities26File, git, plan, state, config, and parity helpers.
Runtime Task Tools7Kernel runtime task lifecycle tools.

Context and primary WU lifecycle operations.

Get current LumenFlow context including location, git state, and active WU

Input: None

Run LumenFlow quality gates (lint, typecheck, tests)

Input:

ParameterTypeRequiredDescription
docs_onlybooleanNoRun docs-only gates (skip lint/typecheck/tests)
full_lintbooleanNoRun full lint instead of incremental
full_testsbooleanNoRun full test suite instead of incremental
full_coveragebooleanNoForce full test suite and coverage gate (implies full_tests)
coverage_modestringNoCoverage gate mode: “warn” or “block”
verbosebooleanNoStream output in agent mode instead of logging to file

Claim a Work Unit and create worktree for implementation

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to claim (e.g., WU-1234)
lanestringYesLane for the WU
cloudbooleanNoUse cloud/branch-pr mode (no worktree, PR-based completion for cloud agents)
branch_onlybooleanNoUse branch-only mode (no worktree, direct branch work)
pr_modebooleanNoUse PR mode (create PR instead of auto-merge)
sandboxbooleanNoLaunch post-claim session through wu:sandbox (requires sandbox_command in MCP)
sandbox_commandstring[]NoCommand argv to run with —sandbox (e.g., [“node”, “-v”])

Create a new Work Unit specification

Input:

ParameterTypeRequiredDescription
idstringNoWU ID (e.g., WU-1234). Auto-generated if omitted.
lanestringYesLane name (e.g., “Framework: Core”)
titlestringYesWork Unit title
descriptionstringNoWU description (Context: … Problem: … Solution: …)
acceptancestring[]NoAcceptance criteria (array of strings)
code_pathsstring[]NoCode paths affected by this WU
test_paths_unitstring[]NoUnit test file paths
test_paths_e2estring[]NoE2E test file paths
test_paths_manualstring[]NoManual test descriptions
exposure”ui” | “api” | “backend-only” | “documentation”NoExposure level (ui, api, backend-only, documentation)
spec_refsstring[]NoSpec/plan references (lumenflow:// URIs)
initiativestringNoParent initiative (INIT-XXX or slug)
phaseintegerNoPhase number within initiative
prioritystringNoPriority level (P0, P1, P2, P3)
typestringNoWU type (feature, bug, refactor, documentation)

Complete a Work Unit (merge, stamp, cleanup). MUST be run from main checkout.

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to complete
skip_gatesbooleanNoSkip gates check (requires reason and fix_wu)
reasonstringNoReason for skipping gates
fix_wustringNoWU ID that will fix the skipped issue

List all Work Units (WUs) with optional status filter

Input:

ParameterTypeRequiredDescription
status”ready” | “in_progress” | “blocked” | “waiting” | “done”No
lanestringNo

Get detailed status of a specific Work Unit

Input:

ParameterTypeRequiredDescription
idstringYesWU ID (e.g., WU-1412)
jsonbooleanNoOutput as JSON

WU maintenance, recovery, prep, and cleanup flows.

Block a Work Unit and move it from in_progress to blocked status

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to block
reasonstringYesReason for blocking
remove_worktreebooleanNoRemove worktree when blocking

Generate handoff prompt for sub-agent WU execution

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to spawn
clientstringNoTarget client (e.g. claude-code, codex-cli, gemini-cli)
thinkingbooleanNoEnable extended thinking
budgetnumberNoToken budget for extended thinking
parent_wustringNoParent WU ID for orchestrator context
no_contextbooleanNoSkip memory context injection
evidence_onlybooleanNoRecord wu:brief evidence without generating handoff prompt output

Clean up worktree and branch after PR merge (PR-based completion workflow)

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to cleanup
artifactsbooleanNoRemove build artifacts

Generate delegation prompt and record explicit lineage intent

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to spawn
clientstringNoTarget client (e.g. claude-code, codex-cli, gemini-cli)
thinkingbooleanNoEnable extended thinking
budgetnumberNoToken budget for extended thinking
parent_wustringNoParent WU ID for orchestrator context
no_contextbooleanNoSkip memory context injection
evidence_onlybooleanNoRecord wu:brief evidence without generating handoff prompt output

Safely delete WU YAML files with micro-worktree isolation

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to delete
dry_runbooleanNoShow what would be deleted without making changes
batchstringNoDelete multiple WUs (comma-separated)

Visualize WU dependency graph

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to analyze
format”table” | “json” | “ascii” | “mermaid”NoOutput format
depthnumberNoMaximum traversal depth
direction”up” | “down” | “both”NoGraph direction

Edit Work Unit spec fields with micro-worktree isolation

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to edit
descriptionstringNoNew description text
acceptancestring[]NoAcceptance criteria to add
notesstringNoNotes text to add
code_pathsstring[]NoCode paths to add
lanestringNoNew lane assignment
priority”P0” | “P1” | “P2” | “P3”NoNew priority
initiativestringNoInitiative ID
phasenumberNoPhase number within initiative
no_strictbooleanNoBypass strict validation

Suggest lane for a WU based on code paths and description

Input:

ParameterTypeRequiredDescription
idstringNoWU ID to analyze (reads YAML)
pathsstring[]NoCode paths to analyze
descstringNoWU description/title text

Fast validation of code_paths and test paths before gates run (under 5 seconds vs 2+ minutes)

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to preflight
worktreestringNoOverride worktree path

Prepare WU for completion by running gates in worktree

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to prepare
docs_onlybooleanNoRun docs-only gates
full_testsbooleanNoRun full incremental test suite instead of tests.unit scoped execution

Create and claim a prototype WU with relaxed validation

Input:

ParameterTypeRequiredDescription
lanestringNo
titlestringNo
descriptionstringNo
code_pathsstring[]No
labelsstring[]No
assigned_tostringNo

Clean stale worktrees (dry-run by default)

Input:

ParameterTypeRequiredDescription
executebooleanNoExecute cleanup (default is dry-run)

Analyze and fix WU state inconsistencies

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to recover
action”resume” | “reset” | “nuke” | “cleanup”NoRecovery action to take
forcebooleanNoRequired for destructive actions like nuke
jsonbooleanNoOutput as JSON

Release an orphaned WU from in_progress back to ready state for reclaiming

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to release
reasonstringNoReason for releasing

Unified WU repair tool - detect and fix WU state issues

Input:

ParameterTypeRequiredDescription
idstringNoWU ID to check/repair
checkbooleanNoAudit only, no changes
allbooleanNoCheck/repair all WUs
claimbooleanNoClaim repair mode
adminbooleanNoAdmin repair mode
repair_statebooleanNoState repair mode

Run a command through the hardened WU sandbox backend

Input:

ParameterTypeRequiredDescription
idstringYesWU ID (e.g., WU-1687)
worktreestringNoOptional worktree path override
commandstring[]YesCommand argv to execute (e.g., [“node”, “-e”, “process.exit(0)”])

Unblock a Work Unit and move it from blocked to in_progress status

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to unblock
reasonstringNoReason for unblocking
create_worktreebooleanNoCreate worktree when unblocking

Safely unlock a lane lock with audit logging

Input:

ParameterTypeRequiredDescription
lanestringNoLane name to unlock
reasonstringNoReason for unlocking
forcebooleanNoForce operation
listbooleanNoList all current lane locks
statusbooleanNoShow detailed status for the lane

Validate WU YAML files against schema (strict mode by default)

Input:

ParameterTypeRequiredDescription
idstringYesWU ID to validate
no_strictbooleanNoBypass strict validation

Initiative planning, assignment, and status operations.

Add a Work Unit to an initiative, optionally assigning to a phase

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID to link WU to
wustringYesWU ID to add (or array for batch)
phasenumberNoPhase number to assign (1-based)

Bulk assign WUs to an initiative based on lane prefix rules

Input:

ParameterTypeRequiredDescription
configstringNoPath to lane bucket configuration file
applybooleanNoApply changes (default is dry-run)
sync_from_initiativestringNoReconcile WUs from a specific initiative

Create a new initiative for multi-phase project orchestration

Input:

ParameterTypeRequiredDescription
idstringYesInitiative ID (e.g., INIT-001)
slugstringYesInitiative slug (kebab-case, e.g., my-initiative)
titlestringYesInitiative title
prioritystringNoPriority level (P0, P1, P2, P3)
ownerstringNoOwner email or name
target_datestringNoTarget completion date (YYYY-MM-DD)

Edit initiative fields

Input:

ParameterTypeRequiredDescription
idstringYesInitiative ID to edit
status”draft” | “open” | “in_progress” | “done” | “archived”NoNew initiative status
blocked_bystringNoInitiative ID that blocks this initiative
blocked_reasonstringNoReason for blocking
unblockbooleanNoRemove blocked_by and blocked_reason fields
add_lanestring[]NoLanes to add (repeatable)
remove_lanestring[]NoLanes to remove (repeatable)
notesstringNoNote to append to notes array
descriptionstringNoReplace the initiative description field
add_phasestring[]NoPhase titles to add (repeatable)
add_success_metricstring[]NoSuccess metrics to add (repeatable, deduplicated)
phase_idstringNoPhase ID to update (use with phase_status)
phase_status”pending” | “in_progress” | “done” | “blocked”NoNew phase status
phase_titlestringNoNew phase title
createdstringNoSet created date (YYYY-MM-DD format)
phase_execution_order”sequential” | “parallel”NoPhase execution order (sequential or parallel)
dependency_modelstringNoDependency model for the initiative

List all initiatives with optional status filter

Input:

ParameterTypeRequiredDescription
statusstringNoFilter by initiative status
format”table” | “json”NoOutput format (table, json)
colorbooleanNoEnable colored output

Link an existing plan or create a new plan template for an initiative

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID to link plan to
planstringNoPath to existing plan file (markdown)
createbooleanNoCreate a new plan template instead of linking

Remove a Work Unit from an initiative

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID to unlink WU from
wustringYesWU ID to remove

Get detailed status of a specific initiative including WUs and progress

Input:

ParameterTypeRequiredDescription
idstringYesInitiative ID or slug
format”table” | “json”NoOutput format (table, json)
colorbooleanNoEnable colored output

Session memory, checkpoints, recovery, and coordination flows.

Save a progress checkpoint for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to checkpoint
messagestringNoCheckpoint message
sessionstringNoSession ID to link checkpoint to (UUID)
progressstringNoProgress summary
next_stepsstringNoNext steps description
triggerstringNoHandoff trigger type (e.g., clear, handoff)

Clean up stale memory data

Input:

ParameterTypeRequiredDescription
dry_runbooleanNoPreview cleanup without making changes
ttlstringNoRemove nodes older than duration (e.g., 30d, 7d, 24h)
session_idstringNoSession ID to consider closed

Get memory context for a Work Unit, optionally filtered by lane

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to get context for
lanestringNoFilter by lane
max_sizenumberNoMaximum context size in bytes
max_recent_summariesnumberNoMaximum number of recent summaries
max_project_nodesnumberNoMaximum number of project nodes
format”json” | “human”NoOutput format
include_rosterbooleanNoInclude a coordination roster section cross-linking delegations + sessions
initiativestringNoInitiative ID to scope roster to

Create a memory node (e.g., for bug discovery)

Input:

ParameterTypeRequiredDescription
messagestringYesMemory node message
wustringNoWU ID to associate with
typestringNoNode type (e.g., discovery, session, checkpoint, note)
tagsstring[]NoTags for the node
discovered_fromstringNoParent node ID for provenance tracking
sessionstringNoSession ID to link node to (UUID)
prioritystringNoPriority level (P0, P1, P2, P3)

Delete or archive a memory node

Input:

ParameterTypeRequiredDescription
idstringYesMemory node ID to delete
tagstringNoDelete all nodes matching this tag
older_thanstringNoDelete nodes older than duration (e.g., 30d)
dry_runbooleanNoPreview deletion without making changes

Export memory for a Work Unit as markdown or JSON

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to export
format”markdown” | “json”NoExport format
typestringNoFilter by node type
lifecyclestringNoFilter by lifecycle (ephemeral, session, wu, project)

Check coordination signals from other agents

Input:

ParameterTypeRequiredDescription
sincestringNoTime filter (e.g., “30m”, “1h”)
wustringNoFilter by WU ID
lanestringNoFilter by lane

Initialize memory layer for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringNoWU ID to initialize memory for

Check pending memory nodes for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to check pending nodes for
typestringNoFilter by node type
format”json” | “human”NoOutput format

Generate recovery context after compaction for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringNo
max_sizenumberNo
format”json” | “human”No
quietbooleanNo
base_dirstringNo

Broadcast a coordination signal to other agents

Input:

ParameterTypeRequiredDescription
messagestringYesSignal message
wustringYesWU ID to associate with
typestringNoSignal type (e.g., handoff, unblock, alert)
senderstringNoSender identifier (agent/session)
target_agentstringNoTarget agent identifier
originstringNoSignal origin context (e.g., cli, mcp, remote)
remote_idstringNoRemote signal ID for cross-system correlation
rolestringNoSender ADR-014 role descriptor
target_rolestringNoIntended-recipient role descriptor
initiativestringNoInitiative scope (e.g., INIT-060)
delegation_idstringNoDelegation registry linkage (dlg-XXXX)

Start a memory session for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to start session for
lanestringNoLane name
agent_typestringNoAgent type (e.g., general-purpose, explore, test-engineer)
context_tierstringNoContext tier (core, full, minimal)

Summarize memory context for a Work Unit

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to summarize
dry_runbooleanNoPreview summary without making changes

Triage discovered bugs for a Work Unit, optionally promoting to WU

Input:

ParameterTypeRequiredDescription
wustringNoWU ID to triage discoveries for
promotestringNoMemory node ID to promote to Bug WU
lanestringNoLane for promoted Bug WU
archivestringNoMemory node ID to archive
reasonstringNoReason for archiving

Agent session lifecycle and issue capture operations.

Query and display logged agent incidents/issues summary

Input:

ParameterTypeRequiredDescription
sincenumberNoDays to include (default: 7)
categorystringNoFilter by category
severity”blocker” | “major” | “minor” | “trivial”NoFilter by severity

Log a workflow issue or incident during agent execution

Input:

ParameterTypeRequiredDescription
category”workflow” | “tooling” | “confusion” | “violation” | “error”YesIssue category
severity”blocker” | “major” | “minor” | “info”YesSeverity level
titlestringYesShort description (5-100 chars)
descriptionstringYesDetailed context (10-2000 chars)
resolutionstringNoHow the issue was resolved
tagsstring[]NoTags for categorization
stepstringNoCurrent workflow step (e.g., wu:done, gates)
filesstring[]NoRelated file paths

Start an agent session for tracking WU execution

Input:

ParameterTypeRequiredDescription
wustringYesWU ID to work on (e.g., WU-1234)
tiernumberYesContext tier (1, 2, or 3)
agent_typestringNoAgent type (default: claude-code)

End the current agent session and return summary

Input: None

Initiative orchestration, monitoring, and delegation helpers.

Display delegation and launch records for WUs or initiatives

Input:

ParameterTypeRequiredDescription
wustringNoWU ID to show delegation / launch records for (e.g., WU-1234)
initiativestringNoInitiative ID to show delegation / launch records for (e.g., INIT-001)
jsonbooleanNoOutput as JSON

Show compact initiative status including evidence-based orchestration state

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID or slug (e.g., INIT-001)

Plan, launch, and reconcile initiative execution with structured orchestration artifacts

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID to orchestrate (e.g., INIT-001)
dry_runbooleanNoShow the logical wave plan without launching or refreshing workers
progressbooleanNoShow current reconciled progress only
checkpoint_per_wavebooleanNoProcess one logical wave / launch attempt, then exit without polling

Monitor orchestration progress, stalls, returned workers, and recovery signals

Input:

ParameterTypeRequiredDescription
thresholdnumberNoStuck detection threshold in minutes (default: 30)
recoverbooleanNoRun recovery actions for stuck spawns
dry_runbooleanNoShow what would be done without taking action
sincestringNoShow recent signals/checkpoints since (e.g., 30m, 1h)
wustringNoFilter by WU ID
signals_onlybooleanNoOnly show signal traffic (skip broader orchestration evidence)

Flow analysis and metrics tooling.

Identify flow bottlenecks in the workflow (WIP violations, stuck WUs, etc.)

Input:

ParameterTypeRequiredDescription
limitnumberNoNumber of bottlenecks to show (default: 10)
format”json” | “table” | “mermaid”NoOutput format: json, table, mermaid
jsonbooleanNoOutput as JSON (shorthand for —format json)

Generate flow metrics report with cycle time, throughput, and other DORA metrics

Input:

ParameterTypeRequiredDescription
startstringNoStart date (YYYY-MM-DD)
endstringNoEnd date (YYYY-MM-DD), defaults to today
daysnumberNoDays to report (default: 7)
format”json” | “table”NoOutput format: json, table
jsonbooleanNoOutput as JSON (shorthand for —format json)

View workflow metrics (lumenflow:metrics alias)

Input:

ParameterTypeRequiredDescription
subcommand”lanes” | “dora” | “flow” | “all”NoMetrics subcommand (lanes, dora, flow, all)
format”json” | “table”NoOutput format
daysnumberNoDays window for metrics calculation
outputstringNoCustom output file path
dry_runbooleanNoPreview without writing

View workflow metrics (lanes, dora, flow, all)

Input:

ParameterTypeRequiredDescription
subcommand”lanes” | “dora” | “flow” | “all”NoMetrics subcommand (lanes, dora, flow, all)
format”json” | “table”NoOutput format
daysnumberNoDays window for metrics calculation
outputstringNoCustom output file path
dry_runbooleanNoPreview without writing

Capture a snapshot of current LumenFlow metrics

Input:

ParameterTypeRequiredDescription
type”all” | “dora” | “lanes” | “flow”NoSnapshot type: all, dora, lanes, flow (default: all)
outputstringNoOutput file path
daysnumberNoDays window for metrics calculation
dry_runbooleanNoPreview without writing snapshot file
format”json” | “table”NoOutput format

Validation and health-check operations.

Validate WU YAML files and status consistency

Input:

ParameterTypeRequiredDescription
idstringNoSpecific WU ID to validate
strictbooleanNoFail on warnings too
done_onlybooleanNoOnly validate done WUs

Validate canonical LumenFlow skill definitions and projected vendor skills

Input:

ParameterTypeRequiredDescription
skillstringNoSpecific skill to validate (e.g., “wu-lifecycle”)

Validate agent synchronization state

Input: None

Validate backlog synchronization between WU YAMLs and backlog.md

Input: None

Validate skills specification files

Input: None

Initialization, onboarding, and environment setup flows.

Connect workspace.yaml to cloud control plane

Input:

ParameterTypeRequiredDescription
endpointstringNo
org_idstringNo
project_idstringNo
token_envstringNo
policy_mode”authoritative” | “tighten-only” | “dev-override”No
sync_intervalintegerNo
outputstringNo
forcebooleanNo

Initialize LumenFlow in a project

Input:

ParameterTypeRequiredDescription
clientstringNoClient type (claude, cursor, windsurf, codex, all, none)
mergebooleanNoMerge into existing files using bounded markers
fullbooleanNoAdd docs + agent onboarding + task scaffolding
minimalbooleanNoSkip agent onboarding docs (only core files)
frameworkstringNoAdd framework hint + overlay docs

List all available LumenFlow CLI commands

Input: None

Sync agent documentation after upgrading LumenFlow packages

Input: None

Diagnose LumenFlow configuration and safety components

Input: None

Run quality gates (lumenflow-gates alias)

Input:

ParameterTypeRequiredDescription
docs_onlybooleanNoRun docs-only gates (skip lint/typecheck/tests)
full_lintbooleanNoRun full lint instead of incremental
full_testsbooleanNoRun full test suite instead of incremental
full_coveragebooleanNoForce full test suite and coverage gate (implies full_tests)
coverage_modestringNoCoverage gate mode: “warn” or “block”
verbosebooleanNoStream output in agent mode instead of logging to file

Initialize LumenFlow workflow framework in a project

Input:

ParameterTypeRequiredDescription
clientstringNoClient type (claude, cursor, windsurf, codex, all, none)
mergebooleanNoMerge into existing files using bounded markers
fullbooleanNoAdd docs + agent onboarding + task scaffolding
minimalbooleanNoSkip agent onboarding docs (only core files)
frameworkstringNoAdd framework hint + overlay docs

Generate enforcement hooks for a specific client (e.g., claude-code)

Input:

ParameterTypeRequiredDescription
clientstringYesTarget client (e.g. claude-code, codex-cli, cursor, gemini-cli)

View workflow metrics (lumenflow:metrics alias)

Input:

ParameterTypeRequiredDescription
subcommand”lanes” | “dora” | “flow” | “all”NoMetrics subcommand (lanes, dora, flow, all)
format”json” | “table”NoOutput format
daysnumberNoDays window for metrics calculation
outputstringNoCustom output file path
dry_runbooleanNoPreview without writing

Interactive setup wizard for LumenFlow workspace (alias)

Input:

ParameterTypeRequiredDescription
yesbooleanNo
domain”software-delivery” | “infra” | “custom”No
project_namestringNo
outputstringNo
forcebooleanNo
skip_pack_installbooleanNo
skip_dashboardbooleanNo

Run LumenFlow release workflow (versioning, npm publish)

Input:

ParameterTypeRequiredDescription
dry_runbooleanNoPreview release without publishing

Sync LumenFlow templates to the project

Input: None

Upgrade LumenFlow packages to latest versions

Input: None

Run validation checks (lumenflow-validate alias)

Input:

ParameterTypeRequiredDescription
idstringNoSpecific WU ID to validate
strictbooleanNoFail on warnings too
done_onlybooleanNoOnly validate done WUs

Interactive setup wizard for LumenFlow workspace

Input:

ParameterTypeRequiredDescription
yesbooleanNo
domain”software-delivery” | “infra” | “custom”No
project_namestringNo
outputstringNo
forcebooleanNo
skip_pack_installbooleanNo
skip_dashboardbooleanNo

Initialize workspace.yaml from interactive prompts

Input:

ParameterTypeRequiredDescription
yesbooleanNo
outputstringNo
forcebooleanNo

File, git, plan, state, config, and parity helpers.

Clean stale backlog entries and archive old completed WUs

Input:

ParameterTypeRequiredDescription
executebooleanNo
dry_runbooleanNo
stale_days_in_progressnumberNo
stale_days_readynumberNo
archive_daysnumberNo

Read and display a value from workspace.yaml

Input:

ParameterTypeRequiredDescription
keystringNo

Safely update workspace.yaml via micro-worktree

Input:

ParameterTypeRequiredDescription
keystringNo
valuestringNo

Sync agent onboarding docs and skills to existing projects

Input:

ParameterTypeRequiredDescription
vendor”claude” | “cursor” | “aider” | “all” | “none”No
forcebooleanNo

Delete files or directories with safety flags

Input:

ParameterTypeRequiredDescription
pathstringNo
recursivebooleanNo
forcebooleanNo

Edit a file via exact string replacement

Input:

ParameterTypeRequiredDescription
pathstringNo
old_stringstringNo
new_stringstringNo
encodingstringNo
replace_allbooleanNo

Read a file with optional line ranges and encoding

Input:

ParameterTypeRequiredDescription
pathstringNo
encodingstringNo
start_linenumberNo
end_linenumberNo
max_sizenumberNo

Write content to a file with audit trail

Input:

ParameterTypeRequiredDescription
pathstringNo
contentstringNo
encodingstringNo
no_create_dirsbooleanNo

Run LumenFlow quality gates

Input:

ParameterTypeRequiredDescription
docs_onlybooleanNoRun docs-only gates (skip lint/typecheck/tests)
full_lintbooleanNoRun full lint instead of incremental
full_testsbooleanNoRun full test suite instead of incremental
full_coveragebooleanNoForce full test suite and coverage gate (implies full_tests)
coverage_modestringNoCoverage gate mode: “warn” or “block”
verbosebooleanNoStream output in agent mode instead of logging to file

Run docs-only quality gates

Input:

ParameterTypeRequiredDescription
docs_onlybooleanNoRun docs-only gates (skip lint/typecheck/tests)
full_lintbooleanNoRun full lint instead of incremental
full_testsbooleanNoRun full test suite instead of incremental
full_coveragebooleanNoForce full test suite and coverage gate (implies full_tests)
coverage_modestringNoCoverage gate mode: “warn” or “block”
verbosebooleanNoStream output in agent mode instead of logging to file

Show git branch listing and current branch

Input:

ParameterTypeRequiredDescription
base_dirstringNo
listbooleanNo
allbooleanNo
remotesbooleanNo
show_currentbooleanNo
containsstringNo

Show git diff with staged/name-only/stat modes

Input:

ParameterTypeRequiredDescription
base_dirstringNo
refstringNo
stagedbooleanNo
name_onlybooleanNo
statbooleanNo
pathstringNo

Show git commit log with filters

Input:

ParameterTypeRequiredDescription
base_dirstringNo
refstringNo
onelinebooleanNo
max_countnumberNo
formatstringNo
sincestringNo
authorstringNo

Show git status with optional porcelain/short modes

Input:

ParameterTypeRequiredDescription
base_dirstringNo
pathstringNo
porcelainbooleanNo
shortbooleanNo

Link or create a plan for an initiative

Input:

ParameterTypeRequiredDescription
initiativestringYesInitiative ID to link plan to
planstringNoPath to existing plan file (markdown)
createbooleanNoCreate a new plan template instead of linking

Check lane configuration health (overlaps and coverage gaps)

Input:

ParameterTypeRequiredDescription
jsonbooleanNo
verbosebooleanNo
no_coveragebooleanNo

Generate lane suggestions from codebase context

Input:

ParameterTypeRequiredDescription
dry_runbooleanNo
interactivebooleanNo
outputstringNo
jsonbooleanNo
no_llmbooleanNo
include_gitbooleanNo

Create a new plan for a WU or initiative

Input:

ParameterTypeRequiredDescription
idstringNo
titlestringNo

Edit or append content to a plan section

Input:

ParameterTypeRequiredDescription
idstringNo
sectionstringNo
contentstringNo
appendstringNo

Link an existing plan URI to a WU or initiative

Input:

ParameterTypeRequiredDescription
idstringNo
planstringNo

Promote plan from draft to approved status

Input:

ParameterTypeRequiredDescription
idstringNo
forcebooleanNo

Cleanup stale signals using TTL policy

Input:

ParameterTypeRequiredDescription
dry_runbooleanNo
ttlstringNo
unread_ttlstringNo
max_entriesnumberNo
jsonbooleanNo
quietbooleanNo
base_dirstringNo

Bootstrap state store from existing WU YAML files

Input:

ParameterTypeRequiredDescription
executebooleanNo
dry_runbooleanNo
forcebooleanNo
wu_dirstringNo
state_dirstringNo

Clean stale state, memory, and signal data

Input:

ParameterTypeRequiredDescription
dry_runbooleanNo
signals_onlybooleanNo
memory_onlybooleanNo
events_onlybooleanNo
jsonbooleanNo
quietbooleanNo
base_dirstringNo

Diagnose state store integrity issues

Input:

ParameterTypeRequiredDescription
fixbooleanNo
dry_runbooleanNo
jsonbooleanNo
quietbooleanNo
base_dirstringNo

Sync internal docs to CLI templates

Input:

ParameterTypeRequiredDescription
dry_runbooleanNo
verbosebooleanNo
check_driftbooleanNo

Kernel runtime task lifecycle tools.

Block a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
task_idstringYes
reasonstringYes
timestampstringNo

Claim a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
task_idstringYes
bystringYes
session_idstringYes
timestampstringNo
domain_dataobjectNo

Complete a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
task_idstringYes
run_idstringNo
timestampstringNo
evidence_refsstring[]No

Create a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
idstringYes
workspace_idstringYes
lane_idstringYes
domainstringYes
titlestringYes
descriptionstringYes
acceptancearray | objectYes
declared_scopesarrayYes
expected_artifactsstring[]No
risk”low” | “medium” | “high” | “critical”Yes
blocksstring[]No
blocked_bystring[]No
extensionsobjectNo
typestringYes
priority”P0” | “P1” | “P2” | “P3”Yes
createdstringYes
labelsstring[]No

Inspect a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
task_idstringYes

Unblock a task directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
task_idstringYes
timestampstringNo

Execute a tool directly through KernelRuntime (no CLI shell-out).

Input:

ParameterTypeRequiredDescription
tool_namestringYes
tool_inputunknownNo
contextobjectYes