requirements-gathering

name	requirements-gathering
description	Systematic requirements gathering through AskUserQuestion. Use when starting development to clarify app specifications.

Requirements Gathering Skill

Systematically gather requirements through AskUserQuestion to ensure clear specifications before implementation.

Trigger Conditions

Apply this skill when:

• User invokes /start-development command
• Starting development of a new feature or app
• Requirements are unclear and need clarification

Gathering Process

Phase 1: Basic Information

Question 1: App Purpose

Header: "Purpose"
Question: "What is the main purpose of this app?"
Options:
- "Productivity/Task management"
- "E-commerce/Shopping"
- "Social/Communication"
- "Entertainment/Media"
(User can also provide custom answer)

Question 2: Target Users

Header: "Users"
Question: "Who are the target users?"
Options:
- "General consumers (B2C)"
- "Business users (B2B)"
- "Internal company use"
- "Specific community/group"

Question 3: Platform

Header: "Platform"
Question: "Which platforms do you want to support?"
Options:
- "iOS only"
- "Android only"
- "Both iOS and Android"
- "iOS, Android, and Web"
multiSelect: true

Phase 2: Feature Requirements

Question 4: Core Features

Header: "Features"
Question: "What are the 3-5 main features you need? (Select all that apply)"
Options:
- "User authentication (login/signup)"
- "Data listing and detail views"
- "Create/Edit/Delete operations"
- "Search and filtering"
multiSelect: true

Question 5: MVP Scope

Header: "MVP"
Question: "For the initial release (MVP), which feature is most critical?"
Options:
- "Core functionality working end-to-end"
- "Beautiful UI/UX design"
- "Performance and speed"
- "Comprehensive feature set"