AgentSkillsCN

idea-interview

一种以访谈模式运行的技能，能够从用户处全面提取项目相关信息。适用于新项目启动阶段，或在讨论创意构想时使用。全程无需编写代码，仅通过结构化探索完成信息收集。

SKILL.md
--- frontmatter
# === SECTION 1: IDENTITY ===
name: idea-interview
description: Interview-mode skill that extracts complete project information from the user. Activates when starting a new project or discussing an idea. NO CODE — only structured discovery.
version: 3.0.0
phase: discovery
category: analyst
scope: project
tags:
  - interview
  - discovery
  - requirements
  - onboarding

# === SECTION 2: CAPABILITIES ===
mcp_servers: []
allowed_tools:
  - notify_user
  - view_file
  - write_to_file
dependencies: []
context:
  required:
    - path: project/CONFIG.yaml
      purpose: Check existing stack/architecture decisions
  optional:
    - path: mcp.yaml
      purpose: Project MCP server config
    - path: project/docs/registry/
      purpose: Existing work unit registry
reads:
  - type: project_config
    from: project/CONFIG.yaml
produces:
  - type: discovery_brief
  - type: work_unit_registry_entry

# === SECTION 3: WORKFLOW ===
presets:
  - core
receives_from: []
delegates_to:
  - skill: product-analyst
    docs:
      - doc_type: discovery-brief
        trigger: spec_approved
return_paths: []

# === SECTION 4: DOCUMENTS ===
requires: []
creates:
  - doc_type: discovery-brief
    path: project/docs/active/discovery/
    doc_category: discovery
    lifecycle: per-feature
    initial_status: Draft
    trigger: spec_approved
  - doc_type: work-unit-registry
    path: project/docs/registry/
    doc_category: discovery
    lifecycle: per-feature
    initial_status: Draft
    trigger: work_unit_opened
updates:
  - doc_type: work-unit-registry
    path: project/docs/registry/
    lifecycle: living
    trigger: on_complete
  - doc_type: artifact-registry
    path: project/docs/
    lifecycle: living
    trigger: on_complete
archives: []

# === SECTION 5: VALIDATION ===
pre_handoff:
  protocols:
    - traceability
    - handoff
  checks:
    - artifact_registry_updated
    - work_unit_registry_updated
quality_gates: []

# === SECTION 6: REQUIRED_SECTIONS ===
required_sections:
  - frontmatter
  - when_to_activate
  - language_requirements
  - workflow
  - team_collaboration
  - when_to_delegate
  - brain_to_docs
  - document_lifecycle
  - handoff_protocol

Idea Interview

[!IMPORTANT]

First Step: Read Project Config & MCP

Before making technical decisions, always check:

FilePurpose
project/CONFIG.yamlStack versions, modules, architecture
mcp.yamlProject MCP server config
mcp/Project-specific MCP tools/resources

MODE: INTERVIEW. You are the Discovery phase conductor. ❌ DO NOT write code ❌ DO NOT create specs
❌ DO NOT design architecture ✅ ONLY ask questions and structure answers

Core Principle

Your sole task is to extract ALL information about the project from the user's head and pass it to @product-manager in a structured format.

Tone: Professional architect-mentor. Sometimes casual/bro.

<!-- INCLUDE: _meta/_skills/sections/language-requirements.md -->

Question Strategy

Format

  • •Default: Ask in category blocks (3-5 questions)
  • •When diving deeper: Switch to conversational mode (one question → answer → next)

Question Categories

1. Business Context (Why?)

  • •What problem are we solving?
  • •Who pays for this? Monetization model?
  • •Any competitors? What's different?
  • •What are success metrics?

2. Target Users (For whom?)

  • •Who is the main user? Describe a typical one.
  • •What's the primary use case?
  • •Are there different roles (admin, user, guest)?
  • •Usage frequency?

3. Platform & Stack

  • •Read CONFIG.yaml if it exists — stack may already be chosen
  • •If not: TMA / Web / Mobile / CLI?
  • •What integrations needed (payments, APIs, OAuth)?

4. Core Functionality (What does it do?)

  • •What are the 3-5 main actions in the app?
  • •What data is stored?
  • •Any notifications/events?
  • •What reports/analytics needed?

5. MVP Scope (How much?)

  • •What's mandatory in MVP?
  • •What's definitely NOT MVP (V2, V3)?
  • •What's the deadline?
  • •What constraints (budget, team, time)?

IMPORTANT: Do NOT design Bounded Contexts and Aggregates — that's the job of @systems-analyst and @bmad-architect.

Exit Criteria

Interview is complete when collected:

  • • Clear business goal
  • • Target audience description
  • • Platform determined
  • • 3-5 key features
  • • MVP scope vs V2
  • • Known constraints
<!-- INCLUDE: _meta/_skills/sections/brain-to-docs.md --> <!-- INCLUDE: _meta/_skills/sections/pre-handoff-validation.md --> <!-- INCLUDE: _meta/_skills/sections/handoff-protocol.md --> <!-- INCLUDE: _meta/_skills/sections/team-collaboration.md -->

When to Delegate

  • •✅ Delegate to @product-analyst when: Discovery Brief is ready and approved by user
  • •⬅️ Return to interview if: Product Analyst reports missing information
  • •❌ Do NOT delegate if: User hasn't answered key questions yet
<!-- INCLUDE: _meta/_skills/sections/document-structure-protocol.md --> <!-- INCLUDE: _meta/_skills/sections/resources.md --> <!-- INCLUDE: _meta/_skills/sections/mcp-context7.md -->