diff --git a/specs/001-export-telegram-members/checklists/requirements.md b/specs/001-export-telegram-members/checklists/requirements.md
new file mode 100644
index 0000000..ca3d94b
--- /dev/null
+++ b/specs/001-export-telegram-members/checklists/requirements.md
@@ -0,0 +1,34 @@
+# Specification Quality Checklist: Export Telegram Group Members
+
+**Purpose**: Validate specification completeness and quality before proceeding to planning
+**Created**: 2025-12-06
+**Feature**: [Link to spec.md](../spec.md)
+
+## Content Quality
+
+- [x] No implementation details (languages, frameworks, APIs)
+- [x] Focused on user value and business needs
+- [x] Written for non-technical stakeholders
+- [x] All mandatory sections completed
+
+## Requirement Completeness
+
+- [x] No [NEEDS CLARIFICATION] markers remain
+- [x] Requirements are testable and unambiguous
+- [x] Success criteria are measurable
+- [x] Success criteria are technology-agnostic (no implementation details)
+- [x] All acceptance scenarios are defined
+- [x] Edge cases are identified
+- [x] Scope is clearly bounded
+- [x] Dependencies and assumptions identified
+
+## Feature Readiness
+
+- [x] All functional requirements have clear acceptance criteria
+- [x] User scenarios cover primary flows
+- [x] Feature meets measurable outcomes defined in Success Criteria
+- [x] No implementation details leak into specification
+
+## Notes
+
+- Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`
\ No newline at end of file
diff --git a/specs/001-export-telegram-members/spec.md b/specs/001-export-telegram-members/spec.md
new file mode 100644
index 0000000..32e00b8
--- /dev/null
+++ b/specs/001-export-telegram-members/spec.md
@@ -0,0 +1,89 @@
+# Feature Specification: Export Telegram Group Members
+
+**Feature Branch**: `001-export-telegram-members`
+**Created**: 2025-12-06
+**Status**: Draft
+**Input**: User description: "Build an application that can help me export Telegram group members info, into a json file"
+
+## User Scenarios & Testing *(mandatory)*
+
+### User Story 1 - Export Telegram Group Members (Priority: P1)
+
+As a Telegram group administrator or member, I want to export the list of group members to a JSON file so that I can analyze the member data, backup group information, or use it for other purposes outside of Telegram.
+
+**Why this priority**: This is the core functionality of the application - without this primary feature, the application has no value.
+
+**Independent Test**: The application can be tested by connecting to a Telegram group and successfully exporting its members to a JSON file that contains all required member information fields.
+
+**Acceptance Scenarios**:
+
+1. **Given** I have valid Telegram credentials and access to a group, **When** I run the export application targeting that group, **Then** I receive a JSON file containing all member information for that group
+2. **Given** I have a Telegram group with 100 members, **When** I export the member list, **Then** the JSON file contains exactly 100 member entries with their respective details
+
+---
+
+### User Story 2 - Select Specific Group for Export (Priority: P2)
+
+As a user managing multiple Telegram groups, I want to be able to select which specific group I want to export members from so that I can target the right group for my data needs.
+
+**Why this priority**: Users may have multiple groups and need to ensure they're exporting from the correct one.
+
+**Independent Test**: The application presents a list of accessible groups for the user to select from, and exports members from the chosen group.
+
+**Acceptance Scenarios**:
+
+1. **Given** I have access to multiple Telegram groups, **When** I run the export application, **Then** I can select which group to export members from
+
+---
+
+### User Story 3 - Export Custom Member Information Fields (Priority: P3)
+
+As a user, I want to select which specific member information fields to export so that I can customize the output to contain only the data I need.
+
+**Why this priority**: Users may have privacy considerations or only need specific data fields, making the export more efficient and privacy-conscious.
+
+**Independent Test**: The application allows users to select which member attributes to include in the export (e.g., username, user ID, first name, last name).
+
+**Acceptance Scenarios**:
+
+1. **Given** I want to export only specific member information, **When** I configure the export settings, **Then** the JSON file contains only the selected fields
+
+---
+
+## Edge Cases
+
+- What happens when a group has more than 10,000 members that Telegram may limit access to?
+- How does the system handle private groups where the user doesn't have sufficient permissions?
+- What happens when the Telegram API temporarily blocks requests due to rate limiting?
+- How does the system handle groups where some member information is restricted by privacy settings?
+- What happens when internet connection is interrupted during export?
+- How does the system handle users who have deleted their Telegram accounts (ghost users)?
+
+## Requirements *(mandatory)*
+
+### Functional Requirements
+
+- **FR-001**: System MUST allow users to authenticate with Telegram using API credentials or user session
+- **FR-002**: System MUST connect to specified Telegram groups and retrieve member lists
+- **FR-003**: System MUST export member information to a JSON file with standard formatting
+- **FR-004**: System MUST include essential member information such as user ID, username, first name, and last name in the export
+- **FR-005**: System MUST handle pagination for groups with large numbers of members
+- **FR-006**: System MUST provide progress feedback during the export process
+- **FR-007**: System MUST handle errors gracefully and provide informative error messages
+- **FR-008**: System MUST comply with Telegram's terms of service when retrieving member information
+- **FR-009**: System MUST save exported JSON files to an 'out' folder in the current working directory with a filename format of 'groupname_members_YYYYMMDD.json'
+
+### Key Entities *(include if feature involves data)*
+
+- **Group Member**: Represents a Telegram user within a group, including user ID, username, first name, last name, and any other accessible profile information
+- **Export Configuration**: Settings that define which group to export from, which member fields to include, output file location, and export parameters
+- **Export File**: The resulting JSON file containing the member data with appropriate structure and formatting
+
+## Success Criteria *(mandatory)*
+
+### Measurable Outcomes
+
+- **SC-001**: Users can successfully export member information from Telegram groups with 100% of accessible members included
+- **SC-002**: Export process completes within 5 minutes for groups with up to 10,000 members
+- **SC-003**: 95% of users can successfully export a group's member list on their first attempt without technical support
+- **SC-004**: JSON output follows standard formatting that can be consumed by other applications and tools