Update to ChatStack - App Specs & Costs

{
  "description": "Turn an incomplete app idea into requirements, stories, a tech spec, and a development cost estimate. Use when the user asks to estimate an app, get a quote, scope a PRD, or figure out what to build. Do not use for coding, calendars, or general PM advice.",
  "included_files": [],
  "name": "chatstack-interview",
  "skill_md_contents": "---\nname: chatstack-interview\ndescription: \"Turn an incomplete app idea into requirements, stories, a tech spec, and a development cost estimate. Use when the user asks to estimate an app, get a quote, scope a PRD, or figure out what to build. Do not use for coding, calendars, or general PM advice.\"\n---\n\nUse the ChatStack Interview MCP tools. Do not invent a quote, timeline, or contact details.\n\n## Session\n\nCall `start_session` first. Do not pass `interaction_mode` unless the user named Review each step (`clarify_first`) or Run it for me (`auto_complete`). Asking for an estimate is not auto-complete.\n\nRead `thread_id` and `interview_handle` from the Session block in the last tool result. Pass both on every later call. Never invent them. Never re-run `start_session` to recover them.\n\n## Next tool\n\nFollow `next_tool` on the last result:\n\n- `send_turn` — user text, interaction-mode choice, or requested table edits\n- `send_action` — approve or submit a pending gate; use `action_type` from `allowed_actions`\n- `get_interview_status` — recover the current stage only\n- `submit_prd` — only at estimate, after the user confirms contact\n\nRelay Markdown pipe-tables, Assumptions, and Risks verbatim. After a reject or request-changes, call `send_turn` with the user's exact words so they see the regenerated table before approve.\n\n## Do not\n\n- Invent first name, last name, email, country, or project name\n- Call `submit_prd` again after a successful receipt\n- Skip these tools and guess a cost\n"
}