Directives

Directives are special annotation lines within steps (or sub-steps) that control execution behavior. Each directive must appear on its own line. Directive lines are extracted during parsing and are not included in the prompt text sent to the AI.

@output — Capture Step Output

Captures the AI response from a step as a named variable, making it available to downstream steps and branch conditions.

Syntax

@output(varname)
@output(varname, extract:"field")

Regex

^@output\((\w+)(?:,\s*extract:"(\w+)")?\)$

Basic Capture

Stores the full AI response as a named variable:

## STEP 1: Classify

Classify this issue as "bug", "feature", or "question": {{issue}}

@output(issue_type)

After execution, issue_type contains the full response text from Step 1.

Field Extraction

Instructs the implementation to extract a specific field from a JSON object in the response:

## STEP 1: Analyze

Analyze the severity. Include a JSON object with your assessment:
{"level": "critical", "confidence": 0.9}

@output(severity, extract:"level")

The implementation scans the response (bottom-up) for a JSON object containing the specified field. If extraction fails, the full response is stored as a fallback.

Rules

• One @output per step (last one wins if duplicated)
• Variable name pattern: \w+ (letters, digits, underscores)
• Extract field pattern: \w+
• Named outputs are available to:
  • Branch conditions in subsequent steps
  • {{varname}} interpolation in subsequent steps
  • Directive arguments (e.g., @tool JSON)

---

@elicit — Human-in-the-Loop Input

Pauses execution and collects input from a human operator. This enables review checkpoints, approval gates, and interactive decision points within a workflow.

Syntax

@elicit(input, "prompt text")
@elicit(confirm, "question?")
@elicit(select, "prompt", "option1", "option2", "option3")

Regex

^@elicit\((\w+)(?:,\s*(.+))?\)$

Types

Type	UI Element	Response
input	Free-text field	User-entered text
confirm	Yes/No buttons	"yes" or "no"
select	Dropdown / radio buttons	Selected option string

Type matching is case-insensitive. Unrecognized types produce a warning and the directive is ignored.

Argument Parsing

All arguments after the type must be double-quoted strings. Single quotes are not recognized.

For select: the first quoted string is the prompt, and all subsequent quoted strings are individual options.

# Correct
@elicit(select, "Which framework?", "React", "Vue", "Svelte")

# Wrong — options must be separate quoted strings
@elicit(select, "Which framework?", "React, Vue, Svelte")

Behavior

1. The step enters awaiting_input status
2. Execution pauses until the user responds
3. The response is stored as __elicit_step_N in named outputs (where N is the step number)

Elicit-only steps: If a step contains only @elicit (and optionally @output), the user’s response becomes the step output directly — no AI call is made.

## STEP 3: Choose Direction

@elicit(select, "Which approach?", "Conservative", "Aggressive", "Balanced")
@output(approach)

Mixed steps: If a step has both an @elicit and prompt content, the AI call runs after the user responds. The user’s response is available as context.

Example

## STEP 2: Review Gate

@elicit(confirm, "The analysis above looks correct. Proceed to recommendations?")

## STEP 3: Get Feedback

@elicit(input, "What specific aspects should the revision focus on?")

---

@prompt — External Prompt Reference

References a prompt from an external library or prompt management system. The referenced prompt’s content is prepended to the step content during execution.

Syntax

@prompt(library:ID)

Regex

^@prompt\(library:([a-zA-Z0-9\-]+)\)$

Behavior

• The prompt identified by ID is fetched at execution time (always the latest version)
• Its content is prepended to the step’s prompt text
• If the referenced prompt doesn’t exist, the step executes with its own content only (no error)
• One @prompt per step (last one wins if duplicated)

ID Format

[a-zA-Z0-9\-]+ — letters, digits, and hyphens.

Example

## STEP 1: Security Review

@prompt(library:owasp-review-criteria)

Apply the review criteria above to the following code:
{{code}}

Implementation Note

The @prompt directive assumes an external prompt storage system. Implementations that don’t have a prompt library may ignore this directive or treat the ID as a file path. The spec does not prescribe how prompts are stored or retrieved — only the reference syntax.

---

@tool — External Tool Invocation

Directly invokes an external tool (via MCP or equivalent protocol). When a step has a @tool directive, the AI call is skipped entirely — the tool result becomes the step output.

Syntax

@tool(connection, tool_name)
@tool(connection, tool_name, {"key": "value"})
@tool("Connection Name", tool_name, {"query": "{{variable}}"})

Regex

^@tool\((.+)\)$

Arguments

Position	Required	Description
1	Yes	Connection name — identifies the tool server. Bare identifier or double-quoted string.
2	Yes	Tool name — the specific tool to invoke. Bare identifier.
3	No	JSON arguments — an object passed to the tool. May contain {{variable}} placeholders.

Parsing Rules

• The argument string is split on the first two commas
• Everything after the second comma is treated as JSON (preserving internal commas)
• Connection and tool names can be bare identifiers (letters, digits, underscores, hyphens, dots) or double-quoted strings for names with spaces

Behavior

1. Template variables ({{var}}) in JSON arguments are rendered before execution
2. The implementation connects to the named tool server and invokes the tool
3. The tool result becomes the step output
4. If the step also has @output(varname), the result is stored as a named variable
5. The step does not make an AI call

Combines With

• @output — capture tool result as named variable
• Breakpoints — execution can still pause after tool completion

Does Not Combine With

• @prompt — tool steps skip AI, so prepending prompt content has no effect
• @elicit — tool execution is deterministic; human input before a tool call should be a separate step

Example

## STEP 2: Fetch Data

@tool(analytics_server, get_metrics, {"period": "{{timeframe}}", "metric": "latency"})
@output(metrics_data)

## STEP 3: Analyze

Based on the metrics data, identify trends and anomalies.

Implementation Note

The @tool directive assumes an implementation of the Model Context Protocol (MCP) or equivalent tool execution framework. Implementations without tool support may skip @tool steps or report them as errors. The spec defines the syntax and execution semantics but not the transport protocol for tool invocation.

---

Directive Interaction Summary

Directive	AI Call?	Can combine with
@output	Yes (captures response)	All other directives
@elicit	Only if step has other content	@output
@prompt	Yes (prepends content)	@output, @elicit
@tool	No (tool result is output)	@output

When multiple directives appear in the same step, they are processed in this order:

1. @tool — if present, skip AI call entirely
2. @elicit — if present and no response yet, pause execution
3. @prompt — prepend referenced content to prompt
4. @output — capture the step result (from AI, tool, or elicitation)