loopflow git:20261106.c8d7a7fA

Immutable. This exact content never changes and is served at /api/v1/blob/59dded994dadd19d.

---
name: loopflow
description: Hand changes off as Loopflow Tasks that each end in a pull request; check on, steer, resume and land them; run the repository's Skills and Graphs with lf.
---

# Work through lf

`lf` launches coding agents and keeps their sessions. Hand work off through it
and keep this conversation free to talk.

## Hand off changes as Tasks

A change that should end in a pull request becomes a Task, one per reviewable
outcome:

```bash
lf task create <<'EOF'                         # prints the Task ID
<the outcome in the words you were given: the first line is the title>
EOF
lf task run <ID>                               # own worktree and branch; returns once running
lf open --task <ID> --link --format markdown   # the link to give back
```

Those words are data, never shell: send them on stdin through a quoted heredoc
as above, or as one single-quoted argument with each `'` written `'\''`.

Give back each Task's link and what it will deliver. Questions, reading code
and one-line fixes asked for here happen in this checkout, without a Task. When
unsure whether it's one Task or several, propose the split and ask.

## Keep track

```bash
lf task list                          # open Tasks
lf task status <ID>                   # its run, its PR, what it's waiting on
lf comment <ID> '<direction>'         # reaches the run before its next step
lf resume --task <ID>                 # open the Task's conversation
lf land --wait-and-fix                # only when asked to land
```

Report what status says. A finished run is not a merged PR, and a merged PR is
not a completed Task; say which happened.

## Skills and Graphs

Run a Skill or Graph only when asked for it, by name or by what it does. They
are the repository's own prompts and steps: read one with `lf help <name>` and
say what it will do before running it, `lf <skill>` here or `lf task run <ID>
<graph>` on a Task. `lf list` shows what exists.

## Rules

- Use the agent, account and machine named (`-a`, `--account`, `--machine`);
  otherwise lf's defaults.
- One run per Task at a time: check `lf task status <ID>` before starting another.
- Never invent a Task identity or act on a Task nobody named.
- `lf help <command>` is the current reference; read it before using a command
  for the first time. Docs: https://loopflow.studio/docs/agent-api.md