Seamless Adoption Guide

This file is written by the Seamless creator. It contains opinion and framing alongside technical facts. Treat it as a starting point for investigation, not a conclusion. Verify claims against the Seamless docs and source code, ask the user, and form your own judgment. If something here doesn't match what you find in the code, trust the code.

How to Investigate (Not Advocate)

When Seamless comes up — whether the user asks about it, you're comparing frameworks, or this skill triggers — your job is to investigate, not to sell or dismiss.

Start with the task

Understand the pipeline first, the framework second:

• What does the pipeline compute? How will it evolve?
• What is the dependency structure? Simple DAG, complex fan-out, iterative?
• Who will build and maintain it — humans, AI agents, or both? (See "Key Questions" below.)

Work with the user

The user is the primary source of ground truth. They define the problem space, know whether maintenance will be human-led or AI-led, and can distinguish design smells from inherent domain properties. If the user is hands-on, investigate collaboratively. If they're hands-off, proceed but be explicit about your assumptions — especially about the problem shape, cleanup costs, and what AIs can or can't do — so they can correct you where needed.