Nifty

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the milestone-led project tool that replaces Nifty.

The idea worth copying: **a milestone's progress is computed from its tasks, never typed.** A status somebody sets by hand is a status that is green until the week it is catastrophically not.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode, FTS5 across tasks and docs
- Caddy in front

THE DATA MODEL
- projects: id, name, client_id, starts_on, ends_on
- milestones: id, project_id, name, starts_on, due_on, position
- tasks: id, milestone_id, title, assignee_id, estimate_hours, status, due_on, position
- status_changes: id, task_id, from, to, actor, at — append-only
- docs: id, project_id, title, body_md, updated_at
- shares: id, project_id, token, scope — what a client can see

MILESTONES AND DERIVED TRUTH
- Progress is completed estimate over total estimate, or task count where nobody estimates. **Computed at read time, never stored**
- A milestone is late when its due date has passed and its progress is under 100. Not when somebody says so
- **Show the trend, not just today's figure**: a milestone at 60% that was 55% a fortnight ago is in more trouble than one at 40% that was 10%. That comparison is what a status meeting is for, and it comes free from the change history

THE TIMELINE
- Milestones as bars across weeks, with progress filled in. One screen, readable by somebody who has never used the tool
- Dependencies between milestones, with cycle detection and a refusal to save one — a loop makes every date meaningless
- A change to a date proposes the cascade and asks before applying it

THE CLIENT VIEW, WHICH IS THE SELLING POINT
- A token link showing the timeline, the milestones and the tasks marked visible. **Never the internal comments, never the estimates, never who is late**
- Filtered on the server for every query, default deny, and tested. The day a client sees an internal note is the day the tool is uninstalled
- A single 'what changed this week' summary, generated from the status history, which is the email an account manager writes by hand every Friday

THE REST, DELIBERATELY SMALL
- Tasks with a status, an assignee and a due date. Four statuses
- Docs as markdown in the project, searchable with the tasks
- No chat. Teams already have one, and a second inbox is where projects go quiet

WHAT MATTERS MOST
Derived milestone progress and a server-filtered client view. One keeps the reporting honest; the other keeps it shareable.