Lo Work

Executes features and tasks. Reads plans from .lo/work/, handles branch isolation and parallel agent dispatch. Creates backlog entries on the fly for ad-hoc tasks. Delegates execution to superpowers. Use when user says "let's build", "work on this", "start working", "execute", or "/lo:work". Stops when complete — does not ship.

職業
カテゴリ: スクリプティング

Executes features and tasks. Handles branch isolation, plan discovery, and progress tracking. Delegates execution patterns to superpowers.

Critical Rules

This skill executes — it does NOT ship. Never push, create PRs, or mark items done in the backlog. When work is complete, suggest /lo:ship.
Task execution NEVER uses subagents or agent teams unless the task has a plan with explicit parallel markers.
Re-read BACKLOG.md from disk on every invocation. Never rely on cached content.
The .lo/ directory must exist. If missing, tell user to run /lo:setup first.

<work-flow> ## Step 1: Find or Create the Work Item

Determine what to work on from the argument provided.

If argument is an ID (f{NNN} or t{NNN}):

Look up the item in BACKLOG.md
Check for a matching directory in .lo/work/

If argument is a description string (not an ID):

Search BACKLOG.md for a fuzzy match on the description
If a match is found, use that existing entry
If no match is found, classify it as a task and create a new backlog entry:

<features-with-plans> **Features with plans:** </features-with-plans> <tasks-without-plans> **Tasks without plans:** <ad-hoc-tasks> **Ad-hoc tasks** (created from a description string in Step 1): <example name="feature-with-subagents"> User: /lo:work f009 <example name="ad-hoc-task"> User: /lo:work fix the dark mode toggle on the settings page <example name="task-direct-execution"> User: /lo:work t015

Lo Work

職業
カテゴリ: スクリプティング

Critical Rules

This skill executes — it does NOT ship. Never push, create PRs, or mark items done in the backlog. When work is complete, suggest /lo:ship.

Task execution NEVER uses subagents or agent teams unless the task has a plan with explicit parallel markers.

Re-read BACKLOG.md from disk on every invocation. Never rely on cached content.

The .lo/ directory must exist. If missing, tell user to run /lo:setup first.

Determine what to work on from the argument provided.

If argument is an ID (f{NNN} or t{NNN}):

Look up the item in BACKLOG.md

Check for a matching directory in .lo/work/

If argument is a description string (not an ID):

Search BACKLOG.md for a fuzzy match on the description

If a match is found, use that existing entry

If no match is found, classify it as a task and create a new backlog entry:

Status	Current Branch	Default Action
explore	any	Stay on current branch (no prompt)
build/open	main	New branch: `feat/f{NNN}-slug` or `fix/t{NNN}-slug`
build/open	release branch	Branch off the release branch
build/open	already on feature branch	Stay on current branch
any	dirty working tree	Warn, offer stash or worktree

Lo Work

Critical Rules

Lo Work

Critical Rules

Step 2: Read Plan and Project Context

Step 3: Set Up Branch Isolation

Step 4: Execute

Step 5: Completion

Error Handling

Prose

Coding Agent (bash-first)

Create Prompt

Strategic Compact

Strategic Compact

Strategic Compact