---
name: spec-translate
description: Translate a foreign spec (GSD or SpecKit) to IronSpec IR vault nodes. Detects source tool automatically, parses to IR, validates, and files to vault. Use when processing a spec file into the vault.
argument-hint: <source-path> --project <slug> [--dry-run] [--from gsd|speckit]
disable-model-invocation: true
allowed-tools: Bash(ironspec *)
---

## Overview

Translate the spec at the given path to IronSpec IR nodes and file them in the vault.

## Steps

### Step 1 -- Run the translate command

```bash
ironspec translate $ARGUMENTS --vault-path "${IRONSPEC_VAULT_PATH}"
```

`$ARGUMENTS` passes the user's full argument string. The `--vault-path` uses the env var. If the user passed `--vault-path` in their arguments, Click will use the explicit value (last wins).

### Step 2 -- Handle error-severity (LLM escalation)

If the command exits with code 1 and the output contains `ERROR-SEVERITY`, this means the parser found ambiguities in required fields that it could not resolve automatically. In that case:

- Read the crash report from the vault reports directory
- Analyze the error-severity warnings listed in the report
- Use your judgment to resolve the ambiguities (e.g., infer missing required fields from context)
- Re-run the translate command with a corrected source or additional flags

### Step 3 -- Confirm results

If the command exits with code 0 or 2, confirm the session report was filed to the vault and show the terminal summary to the user. If exit code 2, note that warnings were generated and the user should review them.