SecondMe Product Requirements Definition

AskUserQuestion

Precondition Check

1. Check if

   .secondme/state.json

   exists
   • Does not exist → Prompt:

     Please run /secondme-init to initialize project configuration first

   • Exists → Proceed
2. Check the stage field

   • stage == "init"

     → Proceed with PRD conversation normally

   • stage == "prd"

     or

     "ready"

     → Ask:

     PRD has already been defined. Do you want to redefine requirements?

     • User confirms → Proceed
     • User cancels → Exit

Conversation Flow

Round 1: Display API Capabilities

modules

state.json

• User login and authorization
• Access Token and Refresh Token management
• User authentication

• Get basic user information (nickname, avatar)
• Get user interest tags (Shades)
• Get user soft memory/knowledge base

• Stream-based conversation with SecondMe AI
• Get historical conversation list
• Get conversation message records

• Structured action judgment: Let AI output valid JSON objects for decision scenarios such as intent classification, sentiment analysis, conditional judgment, etc.
• Define the JSON structure and judgment rules through actionControl

• Add notes/memories to the user's SecondMe

Based on the above capabilities, what type of application do you want to build?

Round 2: Collect Core Requirements

1. Application Goal: What problem does your application mainly solve?
2. Target Users: Who is this application for?

Round 3: Function Refinement

• Do you need to save conversation history to a local database?
• What are your preferences for the conversation interface? (Single-round conversation / Multi-round conversation list)
• Do you need to display the AI's thinking process?

• Which actions need to be judged? (e.g., user intent classification, sentiment tendency, whether a certain condition is met)
• What is the JSON structure of the output? (e.g.,

  {"is_liked": boolean}

  、

  {"intent": "like"|"dislike"|"neutral"}

  )
• What business logic will the judgment result drive? (e.g., automatic like/favorite, route jump, conditional trigger)

• Which user information needs to be displayed? (Avatar, nickname, interest tags, soft memory)
• Where will the user information be displayed? (Personal homepage / Sidebar / Top navigation)

• In what scenarios will users add notes?
• What feedback is needed after adding notes?

Round 4: Design Preferences

1. Interface Style: What visual style do you prefer?
   • Minimalist modern
   • Warm and cute
   • Professional business
   • Other (Please describe)
2. Color Preference: Any favorite colors? (Optional)

Round 5: Requirement Confirmation

📋 Product Requirement Summary

Application Overview: [User-described application goal]

Core Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]

Target Users: [User description]

Design Preference: [Interface style]

Confirm if the above requirements are correct?

Update state.json

.secondme/state.json

{
  "version": "1.0",
  "stage": "prd",
  "modules": ["auth", "chat"],
  "config": { ... },
  "prd": {
    "summary": "Application overview description",
    "features": [
      "Feature 1 description",
      "Feature 2 description",
      "Feature 3 description"
    ],
    "target_users": "Target user description",
    "design_preference": "Minimalist modern"
  }
}

Output Result

✅ Product requirements have been defined!

Summary: [summary]

Feature List:
- [feature 1]
- [feature 2]

Design Preference: [design_preference]

Saved to .secondme/state.json

Next Step: Run /secondme-nextjs to generate the project

Interruption Handling

• Ask whether to save the partially collected information
• If save: Write to the

  prd

  field of

  state.json

  , keep

  stage

  as

  "init"

• When running

  /secondme-prd

  next time, you can continue or restart

Notes

• Conversations should be natural and smooth, not mechanical question-and-answer
• Adjust subsequent questions based on user responses
• If user responses are vague, follow up for clarification
• Maximum 5 rounds of conversation to avoid being too long