Wrike

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 the work management I actually need instead of Wrike.

Be honest about scale first: **this product exists for organisations where nobody can hold the whole picture.** If your team is under about twenty people, you want something far smaller and this prompt is the wrong shape. If you genuinely need cross-project resourcing, read on.

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

THE DATA MODEL
- projects: id, name, folder_id, starts_on, ends_on, status, owner_id
- tasks: id, project_id, parent_id, title, assignee_id, estimate_hours, starts_on, due_on, status, position
- dependencies: id, predecessor_id, successor_id, kind, lag_days — finish-to-start and the other three
- allocations: id, person_id, task_id, week, hours — **planned hours per person per week, which is the resourcing model**
- capacity: id, person_id, week, hours — availability, after holidays and part-time contracts
- time_entries: id, task_id, person_id, minutes, on_date
- changes: id, entity, entity_id, field, before, after, actor, at — append-only

SCHEDULING, WHICH IS WHERE THIS GETS DIFFICULT
- Compute the critical path from the dependency graph and the estimates. **Detect cycles and refuse to save one** — a dependency loop makes every date meaningless and it is easy to create by accident
- A change to one task's date proposes the cascade and asks before applying it. Silent cascades across a hundred tasks destroy trust in the plan permanently
- Working days only, honouring the calendar and each person's own non-working days

RESOURCING, THE ACTUAL PRODUCT
- Allocation per person per week against their capacity, with over-allocation shown in red across every project at once
- **The useful screen is one row per person and one column per week**, totalled across all projects. That single view is what an organisation is buying this for
- Capacity from contracted hours minus holiday minus a realistic factor for meetings and interruptions — planning at 100% is planning to be late
- Show planned against actual from time entries, so the estimates improve

REPORTING
- Project status from its tasks, never typed by hand. **A green status somebody set manually is the most expensive lie in project management**
- Slipped dates, tasks with no assignee, tasks overdue with no update
- Burn-up rather than burn-down, so scope added is visible rather than hidden

PERMISSIONS
- Per project and per folder, checked on the server, default deny. Budget and allocation figures visible only to named roles

WHAT MATTERS MOST
The person-by-week allocation grid and derived project status. One is the reason to build it; the other is what keeps the reporting honest.