validate-pipelinelisted

# Validate Pipeline Skill Walks the full contract chain of an ICM pipeline and validates that stages connect correctly. Finds broken handoffs, mixed reference/working files, and structural anti-patterns. ## Trigger Use this skill when: - The user asks to validate, verify, or check a pipeline's structure - The user says "validate pipeline", "check contracts", "verify handoffs", "are my stages connected?" - The user just ran `/pipeline-scaffold` and wants to verify the result - A `/run-stage` execution failed because of missing inputs ## Procedure ### Step 1: Discover Stages Find all numbered stage folders: ```bash ls -d [0-9][0-9]_*/ 2>/dev/null || ls -d stages/[0-9][0-9]_*/ 2>/dev/null ``` Sort by numeric prefix. If no stages found, halt: "No pipeline stages found. This skill validates ICM pipelines with numbered stage folders (`01_name/`, `02_name/`, etc.)." Record: - Total stage count - Stage names and paths - Whether `_config/` or `shared/` directories exist ### Step 2: Read All Contracts For each stage, read its `CONTEXT.md`. Parse and record: - **Inputs table** — file names, source paths, Layer designations - **Process section** — present/absent, instruction count - **Outputs table** — file names, destination paths, formats - **Review Checkpoint** — present/absent Flag any stage missing a CONTEXT.md entirely. ### Step 3: Validate Contract Chain For each consecutive pair of stages (N, N+1): **3a: Output-to-Input matching** - For every file in stage N+1's In