backloglisted

# Backlog Stage 2 of the delivery pipeline. Turn a spec of record into **one reviewed decomposition** — a feature/story/task tree — then dispatch an independent auditor over it. **This skill creates nothing in any tracker.** It emits a markdown tree. Creating work items is the job of `/devops-azure` batch write mode, which consumes the tree this skill emits. **The tree is a registry, not a derived view.** Tree shape, sizing, and dependencies are information that exists in no other artifact, so the tree is hand-editable everywhere and **never regenerated** — re-running the reasoning that produced it would destroy operator edits rather than refresh them. This skill has exactly one write path: create. **It references; it never restates.** A story cites `REQ-nnn` and `<plan_id>#BAR-nnn`. It does not copy the requirement statement or the bar text — a reference cannot drift from its target and a copy can. ## 1. Resolve the spec, the output path, and the run state **The spec path is supplied or asked for — never guessed.** Resolve `spec_dir` from the `- **Spec directory:**` key in `docs/CONVENTIONS.md`, defaulting to `docs/specs`, treating an unfilled `[e.g., ...]` value as unset. Then guard the value as an action rather than a principle: **open `agents/tech-lead.md` now and apply its plan-directory rejection table to the resolved value.** Apply **only** that table — **not** its Naming/collision-suffix section. **Do not reproduce its rows here**: a second copy goes stale the