ChatStack - App Specs & Costs

Read flow_stage / pending_gate / pending_gate_payload for an interview thread.

get_interview_status

Send one interview / workflow turn. Use this for the user's clarifying answers and for any request to change user stories, requirements, or tech specs — pass their exact words in input_as_text even if next_tool is send_action. Relay the returned pipe-table verbatim before asking them to approve. When interview style is still unset, pass interaction_mode=clarify_first or auto_complete (omit input_as_text for a style-only switch). Do not use send_action/mode_select_* for Review each step / Run it for me. If you send the user's first real message without interaction_mode, clarify_first is accepted by default. Phrases like 'Run it for me' or 'auto-complete' in input_as_text switch the thread to auto_complete even if it was already clarify_first.

send_turn

Start a public interview session (no portal PAT). Call with no arguments: omitting interaction_mode leaves mode unset and returns interaction_mode_question — show the default (Review each step) and the option to change, then wait for the user's pick before send_turn. Do not choose a mode on the user's behalf — wanting an estimate or a fast answer is not a request for auto_complete. Returns thread_id and interview_handle, printed under Session in the text.

start_session

Submit the PRD after the interview has produced user stories, requirements, tech specs, and an estimate (flow_stage estimate / PRD form). Before calling, tell the user that submit emails the pack and creates a ChatStack portal project they can keep managing. A successful submission queues that confirmation email and creates the project/version. Pass any contact fields the user already stated (first_name, last_name, email, country, project_name) as suggestions; the tool will ask you to confirm or fill gaps (confirmed_by_user). Offer optional feedback (scope, questions, notes) and pass it as feedback if they give any — skip is allowed. If you have no contact context, call with none and ask for all five. Never invent contact details. Requires thread_id and interview_handle from start_session. Do not call this tool before estimate artifacts exist.

submit_prd

Submit a pending-gate action from pending_gate_payload.allowed_actions (e.g. clarifying_questions_submit, stories_approve, mode_select_a). Each approve advances one phase: stories_approve → requirements; requirements_approve → technical spec (not the estimate); techspec_approve → estimate. Request-changes actions (stories_reject, requirements_reject, techspec_reject, story_actions_update) do not regenerate the table — wait for the user's edit, then call send_turn with their words and show the new table before asking to approve. mode_select_a/b/c are only for the later How-much-time pick (Normal / Quick estimate / Detailed), never for Review each step / Run it for me (use send_turn.interaction_mode). For clarifying_questions_submit, set payload.answers to { "q1": "A", "q2": "B" } using question ids. Compact replies like "1A, 2B" via send_turn also work. In auto_complete, do not ask the user to pick A/B/C; send_turn auto-answers the first clarifying round, then empty send_action advances one milestone at a time (summary, How-much-time, stories, requirements, tech spec, estimate).

send_action