ce-ship-backloglisted

# Ship Backlog **Invocation input:** Feature id (qualified or unqualified) and optional `--format`: $ARGUMENTS Generate **paste-ready or importable** backlog items from a feature spec. The model reads the spec, builds one neutral `backlog.json`, then runs a stdlib emitter to render the format you pick; the human reviews the output at a material Write gate and pastes/imports it into the tracker — **one-way** (the full rule lives in *Cross-cutting rule — One-Way Sync* below). This is a **bridging utility** — sister to `/ce-ask`, `/ce-ux-audit`, and `/ce-probe-sec`. Sits outside the SDLC pipeline; reads spec artifacts; runs a deterministic emitter; writes a single re-runnable output file. ## Runtime Inputs - **Feature id (required):** e.g. `03-user-profile`, or qualified `<plan-slug>/03-user-profile`. If missing, read `docs/plans/plans.json`, list features with a `specs/<id>/` directory, and ask which to generate. - **`--format` (optional):** one of `ado-md` (default), `ado-csv`, `jira-csv`, `gh-jsonl`. If absent, confirm the target at Stage 0; `ado-md` is the back-compat default. `ado-md` and `ado-csv` target ADO **Agile** work-item types (Story + Task). Other ADO process templates (Scrum / CMMI / Basic) are a documented non-goal — see *Honest Limitations* — not a tunable parameter. ## Preconditions - The feature has a spec — `specs/<id>/ce-spec.md` exists in its plan directory. - `tasks.json` exists in the same `specs/<id>/` directory. ## Execution Contract *Gate loc