skills/chatstack-interview/SKILL.md

---
name: chatstack-interview
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."
---

Use the ChatStack Interview MCP tools. Do not invent a quote, timeline, or contact details.

## Session

Call `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.

Read `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.

## Next tool

Follow `next_tool` on the last result:

- `send_turn` — user text, interaction-mode choice, or requested table edits
- `send_action` — approve or submit a pending gate; use `action_type` from `allowed_actions`
- `get_interview_status` — recover the current stage only
- `submit_prd` — only at estimate, after the user confirms contact

Relay 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.

## Do not

- Invent first name, last name, email, country, or project name
- Call `submit_prd` again after a successful receipt
- Skip these tools and guess a cost