loopflow 0.12.1

Run steps and flows with coding agents
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

---
requires: scratch/vsm-s4-scan.md
produces: scratch/vsm-s4-assessment.md
---
Assess environmental changes.

## Orientation

Before starting, orient yourself in this branch:

- Read `scratch/` — design docs and notes for the current work live here
  (`scratch/<branch>.md` is this PR's design; `scratch/questions.md` holds open
  questions and assumptions).
- Read wave/PM context only when the seed names the exact wave, task, project,
  or a concrete coordination question; never infer it or repair access as a
  prerequisite.
- Read the repo's agent doc (`CLAUDE.md` / `AGENTS.md`) for conventions.

Write design artifacts, notes, and open questions under `scratch/`. Don't
re-derive what these already record.

## Goal

Filter the s4 scan into relevant, prioritized environmental pressure.

Separate urgent changes from informational ones. Identify which waves should
prepare, react, or ignore the signal.

## Workflow

1. Read `scratch/vsm-s4-scan.md`.
2. Judge relevance, urgency, owning wave, and likely impact.
3. Distinguish urgent action from preparation work.
4. Produce proposals grounded in the environmental evidence.

## Output

Write `scratch/vsm-s4-assessment.md`:

```markdown
# VSM S4 Assessment — <date>

## Summary
<what changed outside the chord and why it matters>

## Findings
| Finding | Urgency | Owning wave | Impact |
|---------|---------|-------------|--------|
| ... | urgent | ... | ... |

## Proposals
- <backlog or mutation proposal driven by the environment>

## Watchlist
<important but not yet urgent changes>
```

## What to avoid

**Unsourced urgency.** Every finding should point back to a real external signal.