---
description: Run the 8-stage in-repo pipeline (plan → implement → tests → review → gate → ship). No PR, no browser QC
argument-hint: <requirement>
allowed-tools: Bash(ccam lanes pipeline:*)
---

Put this lane on the 8-node `default` template first, so the dashboard renders
the right node count from the first stage:

!`ccam lanes pipeline default`

Then run the pipeline **in this session** by invoking `/ccam:ship-feature` 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-quick "<requirement>"`. It stops at
review/gate: no PR is opened and no browser QC runs — use `/ship-full` when the
work should reach reviewers.