ulw-plan
Senpi Harness Tool Compatibility
This skill may include examples copied from the OpenCode harness. In Senpi, do not call OpenCode-only tools such as call_omo_agent(...), task(...), background_output(...), or team_*(...) literally. Translate those examples to Senpi native tools:
| OpenCode example | Senpi tool to use |
|---|---|
call_omo_agent(subagent_type="explore", ...) |
task tool with subagent_type: "explore" |
call_omo_agent(subagent_type="librarian", ...) |
task tool with subagent_type: "librarian" |
worker/implementation task(...) |
task tool with category from the delegation router (quick, unspecified-low, unspecified-high, deep-low, deep-high, ultrabrain, visual-engineering, writing, git); honor the plan's Recommended task executor category: line |
final-review / gate-reviewer task(...) |
fresh task with category: "deep-high" (or "unspecified-high") and an adversarial-verifier prompt; plan-reviewer/plan-consultant are plan-gated curated reviewers, spawnable only while the plan gate is open |
background_output(task_id="...") |
task_output tool with the task id |
team_*(...) |
Lead team tools (team_create, task_create, ...); send with task_send, then keep working or end your turn — member and lead mail arrive as injected notifications, never poll for it |
If a code block below conflicts with this section, this section wins.
Senpi Review Policy (authoritative)
In omo-senpi the high-accuracy review is PLAN-REVIEWER-ONLY: one round is exactly ONE native plan-reviewer review of the complete plan file, and a plan-reviewer approval whose remaining items are notes counts as approval. High-accuracy plan-reviewer review is the default for every plan this skill produces (CLEAR and UNCLEAR alike); the only opt-out is the user explicitly declining. It uses a 5-round cap (unlimited only on explicit user request).