---
description: Run the full 16-stage lane pipeline (implement → gates → e2e → review → QC → senior gate → PR, watched until merged)
argument-hint: <requirement>
allowed-tools: Bash(ccam lanes pipeline:*)
---

Put this lane on the 16-node `ship-feature` template first, so the dashboard
renders the right node count from the first stage rather than after the skill
self-corrects:

!`ccam lanes pipeline ship-feature`

Then run the pipeline **in this session** by invoking `/ccam:ship-feature-lane`
with this requirement:

$ARGUMENTS

- No requirement given → ask for one. Never guess what to build.
- The switch above failed (no lane owns this directory) → say so and stop; the
  skill has no lane to report stages against.

This is the in-session twin of `ccam ship-full "<requirement>"`, which does the
same two steps from a terminal by spawning its own `claude`.