← ClaudeAtlas

idea-discovery-interviewlisted

Interview a user with a vague product, feature, or application idea before planning implementation. Use when Codex must ask at least ten high-signal questions, capture a durable discovery brief, expose constraints and risks, and produce an evidence-based plan without inventing requirements.
bglglzd/agent-workflows · ★ 1 · AI & Automation · score 70
Install: claude install-skill bglglzd/agent-workflows
# Idea Discovery Interview Turn an initial idea into an agreed, buildable brief before committing to a plan or implementation. ## Interview workflow 1. Inspect existing project docs, issues, briefs, and code first. Do not ask for facts that are already documented. 2. Restate the idea in one sentence and identify the key unknowns. 3. Ask one to three focused questions per turn. Ask at least ten substantive questions before producing a full plan. 4. Cover the problem and user, success metrics, core journey, MVP and non-goals, platforms, data lifecycle, auth/privacy/security, integrations, technical and operating constraints, quality bar, risks, and launch criteria. 5. Ask follow-up questions when an answer affects a decision. Do not silently choose a product requirement, stack, budget, timeline, or compliance posture for the user. 6. Keep a living brief. Reuse existing product-discovery documentation or create `docs/ai/discovery/<idea-slug>.md` when the project is writable. ## Deliverable After sufficient answers, produce a discovery brief with: problem and users; goals and success metrics; core journey; MVP scope; non-goals; requirements and acceptance criteria; data, privacy, and security; integrations and constraints; recommended architecture plus alternatives; milestones and validation; risks, assumptions, and open decisions; and first implementation steps. Clearly label confirmed decisions, assumptions, and unanswered questions. Ask for approval or revision before st