Shift Handoff

What it does

Shift Handoff is a small browser tool for shift leads at small shops. You paste rough end-of-shift notes, one line per item, written the way you talk ("Sam to fix the walk-in cooler tomorrow", "Dana: order napkins by Friday", "@Priya close register tonight"). It proposes a list of tasks and incidents (start a line with "!" or "incident:" for an incident) and fills in the owner and due date from the words in the note, marked "auto" so you can see what was inferred. You fix anything it missed, tick off what is already done, and build the handoff. Incidents come first, then tasks. Anything with no owner or date is flagged "Needs attention" instead of blocking, and overdue items are flagged too.

The next shift opens to a carry-over card: everything not done from the last handoff, ready to add to the new shift with one click.

Who it's for

A shift lead at a small shop, restaurant or clinic who hands off with a text message or a sticky note and loses the "who is doing this, and by when" part.

How it works

One HTML file plus a small JavaScript parser. No server, no account, no network calls and no AI service. The owner and date inference is plain rules (names before "to" or a colon, @mentions, "today", "tomorrow", weekdays, "by Friday", dates), covered by 11 unit tests you can run with node test/parse.test.js. Data stays in the browser (localStorage). Source and demo: https://github.com/edan-ais/shift-handoff-app

How it was built

I started this in a new, empty public repo during the submission period. I set up the Devpost Learn Skill Pack first and used it to write scope.md, prd.md and spec.md before building anything. Then I built to the spec: the parser and its tests first, then the interface, then the carry-over and history.

What I learned

Keeping the scope to one loop (notes in, handoff out) made it easy to finish and easy to show. Simple rules go a long way: most real handoff lines say who and when in plain words, so no AI service was needed. Flagging gaps instead of blocking fits how shift handoffs really go.

What's next

Recurring tasks, a shareable read-only handoff link, and learning a team's own names and shorthand.

Built With

• css
• html
• javascript
• localstorage