requirements-gathering

name	requirements-gathering
description	AskUserQuestion を使用した体系的な要件収集。開発開始時にアプリ仕様を明確化。

Requirements Gathering Skill

AskUserQuestion を使用して開発前に要件を体系的に収集。

Trigger Conditions

• /start-development コマンド実行時
• 新機能・アプリの開発開始時
• 要件が不明確で明確化が必要な時

Gathering Process

Phase 1: Basic Information

Question 1: App Purpose

header: "目的"
options:
- Productivity / Task management
- E-commerce / Shopping
- Social / Communication
- Entertainment / Media

Question 2: Target Users

header: "ユーザー"
options:
- General consumers (B2C)
- Business users (B2B)
- Internal company use
- Specific community / group

Question 3: Platform

header: "プラットフォーム"
options:
- iOS only
- Android only
- Both iOS and Android
- iOS, Android, and Web

Phase 2: Feature Requirements

Question 4: Core Features (multiSelect: true)

header: "コア機能"
options:
- User authentication
- Data listing and detail views
- Create / Edit / Delete operations
- Search and filtering

Question 5: MVP Scope

header: "MVP範囲"
options:
- Core functionality working end-to-end
- Beautiful UI/UX design
- Performance and speed
- Comprehensive feature set

Question 6: Data Storage

header: "データ保存"
options:
- Local only (AsyncStorage)
- Cloud / Server (Firebase, Supabase, etc.)
- Hybrid (local + cloud sync)
- No persistent storage needed

Phase 3: Screen Design

Question 7: Screen Count

header: "画面数"
options:
- 1-3 screens (simple app)
- 4-6 screens (medium complexity)
- 7-10 screens (complex app)
- 10+ screens (large app)

Question 8: Navigation Pattern

header: "ナビゲーション"
options:
- Bottom tab navigation
- Drawer / Side menu
- Stack navigation only
- Mixed (tabs + stack)

Phase 4: Technical Requirements

Question 9: External APIs

header: "外部API"
options:
- No external APIs
- REST APIs
- GraphQL
- Third-party services (maps, payment, etc.)

Question 10: Authentication

header: "認証"
options:
- No authentication needed
- Email / Password
- Social login (Google, Apple, etc.)
- Phone number / OTP

Question 11: State Management

header: "状態管理"
options:
- Zustand (recommended for this template)
- Redux Toolkit
- Context API only

Phase 5: Confirmation

要件サマリーを表示し、ユーザーに確認を求める。

Output: REQUIREMENTS.md

# Project Requirements

## Overview
- **App Name**: [To be determined]
- **Purpose**: [From Question 1]
- **Target Users**: [From Question 2]
- **Platforms**: [From Question 3]

## Features

### Core Features
[From Question 4]

### MVP Scope
[From Question 5]

## Data & Storage
- **Storage Method**: [From Question 6]
- **Offline Support**: [...]

## Screens & Navigation
- **Expected Screens**: [From Question 7]
- **Navigation Pattern**: [From Question 8]

## Technical Requirements

### Authentication
[From Question 10]

### External Integrations
[From Question 9]

### State Management
[From Question 11]

## Next Steps
1. Review and approve this requirements document
2. Enter Plan Mode to design implementation
3. Begin feature-by-feature development

---
Generated on: [Date]

Notes

• 各フェーズで AskUserQuestion を使用
• multiSelect は必要な質問のみ
• "Other" オプションは自動で追加される
• 要件が曖昧な場合は追加の質問で明確化