docs-imaginelisted

# docs-imagine — Generate conversion-focused docs from a product idea ## Workflow 1. **One question maximum.** If the user already provided a product name or concept in their message, extract it and proceed immediately. Otherwise ask exactly one question: "What is your product? (name + one-liner)". Never ask a second question before generating — infer everything else from the product concept and context. - Infer the product category, likely audience, and tone from the name/description. State what you inferred ("I'm treating this as a SaaS developer tool — generating accordingly. Correct me if I'm off.") and proceed. 2. **Compose the content plan inline** (no `docs-plan.md` file). For the given product, decide on a page set optimised for conversion and clarity: - `README.md` / `index.md` — hero overview: what it is, who it is for, the core promise in one sentence, CTA - `getting-started.md` — quickstart: shortest path to first win (under 5 minutes by convention) - 3–5 feature pages under `features/` — each a benefit-first page: headline = the outcome the user gets, body = how it works + proof, ends with a CTA - `use-cases/` (1–3 pages) — concrete job stories: "X uses this to do Y, getting Z" - `faq.md` — 6–10 frequently asked questions with answers that eliminate objections - `blog/` or `learn/` (optional, 1 page) — one educational or comparison piece if the product category benefits from it 3. **Write `_branding.json`** alongside the docs folder. Sour