plan-backloglisted

# Plan Backlog Turn a product idea into a structured, well-formed backlog in the team's tracker — the **upstream** half of the issue-to-PR workflow, for the product-owner persona. It closes the loop **idea → backlog → ticket → PR** (created stories feed straight into `work-story`). This is the *write* counterpart to `issue-fetch` (which reads). **Nothing is created until you approve the draft.** ## Trigger A request to turn an idea / brief / description / document into tickets, epics, or a backlog — e.g. *"draft stories for this feature"*, *"create Jira tickets from this doc"*, *"break this initiative into a backlog"*. ## Project configuration Read `.claude/dev-kit.json` at the consuming repo root. The `tracker` block names the active adapter and its settings: ```json { "tracker": { "type": "jira" | "linear" | "github" | "azure", ... } } ``` **If the file does not exist (or has no `tracker` block), run `dev-kit-setup` first** — it detects the tracker and persists the config, then returns here. Don't ask for values setup can discover. ## 1. Intake — read the idea in whatever form it arrives - **Pasted text / chat description** → use directly. - **PDF** → read it (page range as needed). - **Word (`.docx`)** → not natively readable; convert first (`textutil -convert txt file.docx -output -` on macOS, or `pandoc file.docx -t markdown`), then read. If neither tool is available, ask the user to paste the text or export a PDF. - **Artifact / Confluence page / URL** → fetch