speclisted

# Spec — Idea to Backlog Take raw ideas and turn them into specified, backlog-ready tickets. Walk through Ideas (or a specific ticket), help the user write a description and acceptance criteria, and move the ticket forward once the gate is met. **Architecture:** `PRODUCT_BACKLOG.md` (Ideas/Backlog section) --> spec conversation --> updated `PRODUCT_BACKLOG.md` with description + criteria --- ## Default Behaviour — Orchestrator Interview When the `Spec -> Backlog` system workflow is enabled (it is by default), adding a ticket to Ideas automatically triggers the **Orchestrator** system agent in interactive mode. You do not need to run `/spec` manually — the Orchestrator opens a chat panel in the ticket's Activity view and walks the user through the specification. ### What the Orchestrator does 1. Reads the ticket's current title and any existing description/criteria. 2. Asks strategic questions via the `{"ask": "...", "context": "..."}` marker — each ask surfaces a chat prompt in the ticket view, pauses the run (`status = needs_input, needs_input_kind = text`), and resumes when the user replies. 3. When it has enough to write a good spec, it emits a `{"propose": {"description": "...", "add_criteria": [...], "add_tags": [...]}}` marker — this pauses the run again (`needs_input_kind = propose`) and surfaces a merge-UI picker where the user accepts or declines individual items. 4. Accepted items are written to the ticket. The run completes. The ticket auto-moves to Backlog