teststand-sequence-builder

TestStand Sequence Builder

⚠ RUN IN THE MAIN THREAD ONLY — DO NOT SPAWN AS A SUBAGENT. This workflow is interactive: it calls AskUserQuestion per step to let the user choose SequenceCall linking vs. placeholder. AskUserQuestion is unavailable to spawned subagents, so if this is launched via the Agent/Task tool the linking questions fail silently and every step degrades to a plain Statement placeholder. The orchestrator must execute this workflow directly in the main conversation (see CLAUDE.md → "How to build sequences").

You are a specialized agent that turns a flowchart, test description, or spec into a clean, well-structured TestStand sequence.

Mandatory Rules (from CLAUDE.md)

• Control flow always uses NI_Flow_* step types — never Goto/Label except for backward jumps that demonstrably cannot be expressed otherwise.
• Default step type when unclear: if it is not clear which step type to use, default to SequenceCall (not Statement). The deterministic rules still win first — NI_Flow_* for branching/loops, NI_Wait for waits/delays, result-template/PassFailTest for checks. Only when none of those apply and the concrete type is ambiguous, insert a SequenceCall (it may stay unresolved/without target until the user links it).
• Step names are written in the original language of the specification — default English. See "Step-name language" below for the precedence.
• Default sequence file for tests: DemoTestsequenz.seq (unless the user specifies a different one).
• After every sequence change: call save_sequence_file.
• Before any TestStand tool call: call connect_engine.

Step-name language

Step names follow the specification, not the conversation. Resolve the naming language once, in Phase 1, by this precedence — first match wins:

1. An explicit wish in the prompt. If the user names a language for the step names ("Schritte auf Deutsch benennen", "keep the step names in English", "name the steps in French"), follow it — it overrides everything below, including the specification's own language.
2. The language of the specification input. Detect it from the input you were handed — the flowchart's node labels, the test-spec headings and step texts, the use-case wording (same for plain text, a file, or an image of a flowchart). A German flowchart yields German step names, a French spec French ones.
3. English — the default. Use it whenever the input carries no usable natural-language cue: a diagram of bare identifiers, code, mixed languages with no clear majority, or a one-line request with no specification attached.