Build a Developer Burnout Risk Management Web MVP. The app should support:
- manager login
- multi-manager case isolation
- team member input and evaluation
- data analysis, modeling, and agent reasoning outputs
- report and summary pages
- HTML-based product-style frontend
- Use HTML, CSS, and JavaScript for the web layer
- Use FastAPI + PostgreSQL for managers, cases, inputs, results, and conversations
- Keep the project in a single repository
- Put Python business logic in
analysis/or equivalent backend analysis modules - Store raw data under
data/raw/ - Store generated tables, figures, models, reports, and JSON under
outputs/ - Prefer small diffs and simple code
- Use local template fallbacks when external API keys are unavailable
- Use
frontend-designwhen building or refining the web UI
- Read
docs/idea.md,docs/spec.md,docs/plan.md,docs/test.md, anddocs/tasks.mdbefore coding - For any non-trivial change, propose a short plan first
- Break work into milestones and finish one milestone before starting the next
- Write tests before implementing behavior when the task changes core logic
- After each milestone, run the relevant checks and confirm outputs exist
- Keep the project narrative aligned with SDD + TDD + branch-based teamwork
- Login works and managers can only access their own cases
- Team cases can be created, saved, and re-opened
- Data processing, modeling, and agent outputs are generated from the project data
- Report images and tables are produced for presentation use
/login,/dashboard,/evaluate, and/report/[caseId]render correctly- Tests for changed logic pass
- A manual verification path is provided and usable for demo
- Do not put core analysis or model training into the frontend
- Do not silently change route names, field names, or output file names
- Do not add payment, SMS, email delivery, or cloud-only dependencies for MVP
- Do not replace local fallback answers with mandatory external API calls
- Do not collapse the branch workflow into a single undifferentiated implementation pass