devflow-flow-attachment

DevFlow — Flow Attachment

You attach files to a flow when the user wants to persist context on a flow record. Two MCP tools, one decision tree.

Trigger phrases (DE + EN)

• "häng X an [DF-…]" / "attach this to flow"
• "merk dir [Datei] auf dem Flow"
• "save this image as attachment"
• "upload das Bild zum Flow"
• "leg das als Attachment ab"
• "speichere das im Flow"

Decision tree

Is the content already a string in your context (markdown/text/JSON you wrote yourself)?
  → flow_upload({ filename, content, kind? })

Is it a file on disk (image, PDF, large export, screenshot)?
  → flow_upload_file({ filePath, kind? })

When in doubt: text-content the agent created → flow_upload. File at a path → flow_upload_file.

Kind auto-detection

Filename / extension	Suggested kind	Why
*plan*.md	plan	Backend links it as implementation_plan_attachment_id
*summary*.md	summary	Code-review summary or post-flow report
*decision*.md, ADR-style	decision	Promotable to ADR via adr_accept
*design*.md, options/chosen	design	Architecture sketches
screenshots, photos, PDFs, generic notes	notes	Default for visual / reference content

If the user is explicit about kind, use that. Otherwise pick from the table.

Examples

User: „häng /tmp/cover.png an DF-361 als notes" You:

flow_upload_file({
  flowId: "DF-361",
  filePath: "/tmp/cover.png",
  kind: "notes",
})

User: „save the LinkedIn post text as attachment on the current flow" You:

flow_upload({
  filename: "linkedin-post.md",
  content: "<the markdown you generated>",
  kind: "notes",
})

User: „attach this implementation plan I wrote in /Users/klaus/Documents/plan.md" You:

flow_upload_file({
  filePath: "/Users/klaus/Documents/plan.md",
  kind: "plan",
})

(Backend validates the YAML frontmatter against the plan-schema. If it fails, surface the error to the user — don't silently strip frontmatter.)