SRS Wizard – Multi-step

Welcome & Project Name*

Welcome to the wizard. Start by giving your project a clear name and basic metadata.

Project Name*

Example: TeamPulse Notification Chrome Extension

This field is required.

Version

Semantic or internal version label.

Date

Project definition date.

Project Type

Choose the main type of software you want to build.

Predefined types (pick one)

This helps the model apply type-specific best practices.

Custom project type (optional)

Used only when "Custom type" is selected and this field is non-empty. Otherwise, only the chosen predefined type is reflected in the SRS.

What Problem Does This Project Solve?*

Describe the specific issue or need this project addresses.

Problem Description*

Explain the problem or pain point. You may write in English or in any other language.

This field is required.

Key Features Required*

List the main features your system must have.

Key Features* Let model decide

Type your required features, or check "Let model decide" to let the model define a minimal, complete feature set.

This field is required unless delegated to the model.

User Workflow

Describe the typical workflow of a user using your app.

User Workflow Let model decide

Describe the main steps a typical user takes, or check "Let model decide" to let the model infer a realistic workflow.

UX & Usability

Describe any usability goals, tone, or visual style.

UX Guidelines Let model decide

Write your own UX rules, or check "Let model decide" to let the model apply professional minimalist UX best practices.

Do you have a RAW model

Provide example software, screenshots, or websites that represent what you want the app to feel and behave like.

Raw model / inspiration references

You can paste: (1) app or product names, (2) URLs of sites you like, or (3) links to screenshots / mockups. The prompt will tell the model to use these as UX and flow inspiration without copying them verbatim.

Target Users

Who will use this project or extension?

Target Users Let model decide

Describe the audience yourself, or check "Let model decide" to let the model infer a reasonable target audience.

Third-Party Integrations

Any external APIs or services needed?

Third-Party Integrations Let model decide

List APIs/services yourself, or check "Let model decide" to let the model choose minimal, reliable integrations.

System Integration

Will it connect with other apps or databases?

System Integration Let model decide

Describe integration points yourself, or check "Let model decide" to let the model design simple, robust connections.

Performance Requirements

Any speed, memory, or scalability needs?

Performance Requirements Let model decide

Specify performance targets, or check "Let model decide" to let the model apply realistic, efficient defaults.

Security and Compliance Requirements

Any security rules or regulations?

Security and Compliance Let model decide

Write your own security rules, or check "Let model decide" to let the model apply modern security best practices.

Data Storage Needs

Will you store data and roughly how much?

Data Storage Needs Let model decide

Describe data and retention yourself, or check "Let model decide" to let the model choose a minimal, safe storage design.

Architecture & Dependencies

High-level technical design and required components.

Architecture Type Let model decide

Specify an architecture, or check "Let model decide" to let the model pick a simple, robust approach.

Technology Stack Let model decide

Select technologies yourself, or check "Let model decide" to let the model choose a minimal, efficient stack.

Dependencies Let model decide

List required libraries/services yourself, or check "Let model decide" to let the model choose minimal dependencies.