Input: one process name. This is the loop each terminal runs so a process comes out finished and
self-verified. Uses the two doer skills; load processflow-review/references/guardrails.md for the
done-criteria.
The loop
- Work it — run
processflow-process <name>: transcript-check, rework concept + canvas + diagrams via Chrome-MCP, re-score, sync the helper app — aim for all required guardrails. - Critique it — run
processflow-critic <name>: red-team from the critical lens, walk the Fehlermuster-Register, web-research tools/prices/technique → issue list. - Incorporate immediately — fix every real issue the critic surfaced (back through the Konzept-/ Canvas-Copilot). Re-sync the helper app.
- Repeat 2–3 until the critic returns no blocking issues (or the remaining ones are justified n.a. with a documented reason — e.g. read-only compliance field, arch_diag n.a. for single-tool). Cap at ~3 loops; if still not clean, stop and report what's blocking (don't spin).
Finish
- Re-score the Prozessanalyse if the approach/effort changed (so score matches concept).
- Final helper-app sync: guard flags + notes reflect the true state (verified vs. n.a.-with-reason).
- Report a tight summary: what changed, final guard status, any residual/n.a. items and why.
Parallel-Koordination (WICHTIG — du bist einer von ~10)
Aktuell arbeiten mehrere Agenten gleichzeitig, je Terminal ein anderer Prozess. Ihr teilt euch die
Firma, die Helper-App (review.json), die Tool-Landkarte, das ERP und den Chrome-Login. Deshalb:
- Am Start den Team-Update-Feed lesen:
GET /api/updates?company=<slug>(localhost:8765) — dort stehen Querschnitts-Findings der anderen (z. B. „SAP→IPTOR", „Branche=Schmuck", „Artikel-Matching ist geteiltes Modul", „InboxMate = gemeinsamer Eingang", Preis-Checks). Vor Doppelarbeit/Widerspruch schützt das. - Regelmäßig re-checken (vor jedem Rework-Schritt, mind. zu Beginn + nach dem Critic).
- Eigene Querschnitts-Findings SOFORT teilen:
POST /api/update {company, agent:"<terminal/prozess>", process:"<name>", tags:[…], text:"…"}— alles, was für andere relevant ist: erfundene/echte Tools, Branche, geteilte Module/Eingänge (InboxMate, Artikel-Matching), OS-Konsolidierung, Preis-/Lizenz-Fakten, System-of-Record, wiederkehrende KI-Fehler. Prozess-spezifische Details bleiben inreview.json; der Feed ist NUR für Firmen-/prozessübergreifend Relevantes. - Bleib auf DEINEM Prozess. Andere Prozesse gehören anderen Terminals — nicht mitbearbeiten; wenn du dort etwas siehst, per Feed melden statt selbst ändern.
Hard rules (every terminal)
- NEVER set
approved/HI-freigegeben (that's the human/Martin) or name the presentation date (that's Dominik). Prepare everything up to freigabe-ready; leave the switch to the human. - Writes hit live customer data. In a user-authorized multi-terminal batch, proceed autonomously but stay precise and verify after each write; otherwise confirm each write.
- Fresh Chrome session token when the ~1h JWT expires. If the helper app is down, restart it.
- Stay on your ONE assigned process — don't touch others (parallel terminals own theirs).