flowerHR

2026-03-22 ~ 2026-03-31 · 9 days

Solo Burnout

A rapid AI-assisted sprint, ending abruptly after 3 days of intense feature development, leaving 9 dependencies and 0 deployment configurations.

“A rapid bloom, quickly wilted by ambition.”

Death Type

Sprint-to-Silence Syndrome

This project exemplifies 'Sprint-to-Silence Syndrome', characterized by an extremely rapid initial development phase (4 commits in 3 days) fueled by AI assistance (Vibe Score 50/100, Claude Code detected) and intense personal effort (75% weekend commits), followed by an abrupt, unexplained cessation of all activity. The implementation of ambitious features like 'Add 3-step flow, dark Cadence UI, task import/export' was a grand finale, not a beginning.

Cause of Death

1. Hyper-sprint to sudden halt

The project experienced 4 commits in just 3 days of active development, from 2026-03-29 to 2026-03-31. This intense burst of activity then ceased entirely, indicating an abrupt and final stop.

2. Weekend warrior's last stand

75% of the project's total 4 commits occurred on weekends, suggesting a concentrated development effort outside of regular hours. The final commit landed on a Tuesday, followed by complete silence.

3. Feature-rich, infrastructure-poor

Despite adding 1351 lines to `frontend/app/page.tsx` and 410 lines to `backend/app/api/skill_router.py` for a '3-step flow' and 'dark Cadence UI', the project lacked basic development practices like tests, CI/CD, or Docker configurations, a common symptom of projects built for speed, not longevity.

Vibe Score

50/ 100

AI-assisted but human-driven

What They Did

Conceived as an AI-powered HR plugin, flowerHR aimed to process job descriptions into a structured SKILL.md, mapping proficiency levels and tasks. It leveraged FastAPI on the backend with ambitious integrations like `openai`, `anthropic`, `pdfplumber`, and `python-docx` to fulfill its complex vision. The README promised a comprehensive skill profile with agent handoff notes, an aspiration that lasted precisely 3 active development days.

fastapiuvicornpython-dotenvpydantic-settingsopenaianthropicpython-multipartpdfplumberpython-docx

Burnout Analysis

The developer, Manabu Nagaoka, engaged in a concentrated 3-day sprint, delivering 4 commits and adding over 1351 lines to `frontend/app/page.tsx` and 410 lines to `backend/app/api/skill_router.py`. 75% of this activity occurred on weekends, culminating in a final commit on 2026-03-31. Despite a 'low' burnout score (15/100) from the quick stats, the sudden cessation of development after this intense burst suggests a rapid and complete depletion of project-specific motivation.

Dependency Archaeology

The `backend/requirements.txt` boasted 9 Python dependencies, including `openai`, `anthropic` for AI, and `pdfplumber`, `python-docx` for document parsing. These were installed on a project that lived for 9 days and saw active development for only 3. The `frontend/package-lock.json` alone ballooned by 1632 lines, indicating a significant commitment to frontend ambition that, like its backend counterpart, never fully materialized into a deployed product.

Autopsy: File Structure

├──backend/requirements.txt9 dependencies for 9 days of life. An ambitious shopping list.

├──backend/app/main.py17 lines of code, the modest heart of an AI-powered HR plugin.

├──frontend/package-lock.json+1632 lines, the true weight of frontend ambition.

├──frontend/app/page.tsx+1351 lines, a testament to UI dreams that now remain static.

├──backend/app/api/skill_router.py+410 lines, where the AI's skill-mapping magic was meant to unfold.

├──SESSION_NOTES.md84 lines of development notes, more detailed than the project's lifespan.

└──backend/app/services/doc_parser.py105 lines for document parsing. The documents were parsed, the project was not deployed.

Eulogy Stats

Total Commits: 4
Ambitious Adjectives: 5
Deploy Config: No
Estimated Users: 0 (despite 1632 lines of frontend dependencies)

Last Words

“The final message, 'Add 3-step flow, dark Cadence UI, task import/export, and demo sample' on 2026-03-31, reads like a last-ditch effort to achieve product-market fit before the developer's ambition expired.”