User Stories

[GTyson261]

Frontend User Story issues 1

I want to submit my daily mental health check-in through an easy-to-use interface so that I can track my mood, stress, sleep, and journal entries over time and view my progress visually.

User can enter mood, stress, sleep, notes, triggers, and coping strategies
Form validates required fields before submission
Dashboard displays historical trends in charts/graphs
AI recommendation appears after submission
Risk/support alert is shown when applicable

Backend User Story issues 2

I want to process user mental health check-ins, evaluate risk levels, and generate AI-powered recommendations so that users receive personalized feedback and support resources.

API accepts and validates check-in submissions
Backend stores/retrieves check-in history
Risk assessment logic flags elevated-risk entries
AI recommendation endpoint returns generated suggestion
Support resources endpoint returns appropriate resources

Database User Story issues 3

I want to securely store and manage user mental health check-in data so that the application can retrieve historical records for dashboards, analytics, and personalized recommendations.

Database stores all check-in fields accurately
Data persists between sessions/restarts
CRUD operations work through repository layer
Relationships between users/check-ins are maintained
Database schema supports reporting/trend analysis

[coreyeross25]

Great work on these! You have captured the core functionality of the application across the entire stack. To take these to a professional level, we want to focus on Separation of Concerns and making sure the stories focus on Value rather than just technical tasks.

1. Frontend: The "User Value" Perspective
   Current Status: This is currently an Epic (a story that is too large).

The Issue: You’ve combined data entry, data visualization, and AI feedback into one story. If the charts aren't ready, we can't "finish" the story even if the form works.

Recommendation: Split this into three smaller stories:

Check-in Submission: Focus on the form and validation.

Progress Dashboard: Focus on the charts and historical data.

Real-time Alerts: Focus on the risk/support notifications.

Pro-Tip: Don't forget Accessibility. For a mental health app, we should ensure the interface is usable for people under high stress (e.g., clear labels, high contrast).

2. Backend: The "Logic" Perspective
   Current Status: These read a bit like a "To-Do" list for a developer.

The Issue: Using terms like "API," "Endpoint," and "Logic" describes how you are building it, but a User Story should describe what the user gets.

Recommendation: Reframe the "So That" clauses to focus on the outcome.

Instead of: "API accepts and validates..."

Try: "The system ensures only complete and valid check-ins are processed so that health trends are accurate."

Critical Addition: Since this is mental health data, you should add Acceptance Criteria for Security/Privacy (e.g., data encryption).

3. Database: The "System Foundation" Perspective
   Current Status: These are Technical Tasks rather than User Stories.

The Issue: In a professional setting, we usually don't write "Database User Stories" because the user never sees the database. These requirements are usually folded into the Backend stories as "Non-Functional Requirements."

Recommendation: If you want to keep these as separate stories, focus on Data Integrity and Availability.

Example: "I want my historical data to be encrypted and backed up so that my personal history is never lost or exposed."

[GTyson261]

Issues

Build Daily Check-In Form
1.Create an accessible form for users to submit daily mental health check-ins with validation and confirmation messaging.

Build Progress Dashboard
2.Create charts/dashboard to display historical mental health check-in trends.

Implement Risk Alert Display
3.Show support alerts/resources when elevated-risk responses are detected.

Process Check-Ins & Generate Recommendations
4.Validate submissions, assess risk, and return AI-powered recommendations securely.

Implement Secure Data Storage
5.Store mental health data securely with encryption and reliable retrieval support.