---

name: flight-validate description: Run domain validation scripts against code - PASS or FAIL with no interpretation. Use after implementing code to verify it meets domain constraints.

⚠️ EXECUTION RULES (MANDATORY)

1. EXECUTE EACH STEP - Do not skip steps based on "prior context"
2. USE TOOLS - You MUST call Read/Bash tools, not recall from memory
3. SHOW WORK - Each step must produce visible tool output
4. NO SHORTCUTS - "I already read this" is NOT acceptable

Anti-Patterns (DO NOT DO THESE)

• ❌ "I already read the domain files earlier"
• ❌ "From earlier analysis..."
• ❌ Summarizing steps without executing them
• ❌ Claiming knowledge from "this conversation"

---

/flight-validate

Run domain validation scripts. Script says PASS or FAIL - no agent interpretation.

Usage

Copy/flight-validate [path]

Arguments

• $ARGUMENTS - Optional path to validate (defaults to detecting files in src/)

---

Process

1. Detect Which Domains Apply

Copy# Check what file types exist
ls src/*.c src/*.h 2>/dev/null && echo "DOMAIN: embedded-c-p10"
ls src/*.js 2>/dev/null && echo "DOMAIN: javascript"  
ls src/*.jsx src/*.tsx 2>/dev/null && echo "DOMAIN: react"

2. Run the Domain Validation Script

Each domain has a .validate.sh script. Run it. Report output. That's it.

Copy# For C code:
.flight/domains/embedded-c-p10.validate.sh src/*.c src/*.h

# For JavaScript:
.flight/domains/javascript.validate.sh src/*.js

# For React:
.flight/domains/react.validate.sh src/*.jsx src/*.tsx

3. Report Results

Do not interpret. Do not add opinion. Just show:

Copy## Validation: [domain]

[paste exact script output]

## Result: PASS or FAIL

If script exits 0 → PASS If script exits non-zero → FAIL

---

Output: Validation Report

Copy## Validation: [domain]

[exact script output]

## Result: PASS or FAIL

---

Critical Rules

1. RUN THE SCRIPT - Do not inspect code manually
2. REPORT OUTPUT - Paste exactly what the script says
3. NO INTERPRETATION - Script decides pass/fail, not the agent
4. IF NO SCRIPT EXISTS - Say "No validation script for [domain]" and stop

---

Example

Copy$ .flight/domains/embedded-c-p10.validate.sh src/*.c

═══════════════════════════════════════════
  P10 Validation: src/ring_buffer.c
═══════════════════════════════════════════

## NEVER Rules
✅ N1: No goto
✅ N2: No setjmp/longjmp
✅ N3: No malloc/free
...

## MUST Rules  
✅ M1: Compile -Wall -Wextra -Werror
✅ M2: Functions ≤60 lines
✅ M3: ≥2 asserts/function
...

═══════════════════════════════════════════
  PASS: 11  FAIL: 0
  RESULT: PASS
═══════════════════════════════════════════

Report: PASS

---

If Validation Fails

Show the failures. Do not fix automatically. User decides:

• Fix the code and re-run /flight-validate
• Or run /flight-tighten if the rule needs adjustment

---

When to Use

---

Next Step

If PASS - Task complete, continue to next task:

Copy/flight-prime tasks/[next-task].md

If FAIL - Fix issues or tighten rules:

Copy[fix code] → /flight-validate
    OR
/flight-tighten  (if rule needs adjustment)

Workflow: /flight-validate → PASS → next task | FAIL → fix → retry