seeflow-lookup

Look up registered SeeFlow flows and consult them as architectural ground truth. Read-only counterpart to /seeflow — that skill creates and edits flows; this one queries them while writing code or making decisions.

Routing gate — run before deciding

Inspection phrasing always lands here first, even when no flow is yet registered — the auto-handoff below covers the empty case. The trigger words are: show me, show the, how does, how do, what does, what handles, where does, where is, diagram, explain, walk me through, plus any reference to a flow by slug or title without an explicit creation verb (create, scaffold, generate, add a flow). When in doubt, route here — a no-match handoff to /seeflow is cheap; a duplicate creation run from skipping the gate is not.

When NOT to invoke

• Editing flows → use /seeflow or the canvas.
• Creating flows from scratch when the user explicitly said "create / scaffold / generate / add a flow" → call /seeflow directly. (This skill auto-hands off to /seeflow if it discovers no match for an inspection prompt; skip the hop only when the user's verb is unambiguously creation.)
• Reading LEARN.md → use Read directly (that file is /seeflow's territory).
• Mutating anything — this skill is read-only. The auto-handoff above invokes /seeflow; it does not mutate state itself.

Discover the CLI

Run seeflow help to list the available subcommands and their flags. If seeflow is not on PATH, fall back to npx -y @tuongaz/seeflow@latest help. The CLI's help output is the source of truth for the callable surface — do not assume command names or flags from memory.