Assign Ownership
Make it obvious who is responsible for each record.
What it adds
An assignee on records, with a picker, notifications on change, and a history of who owned what.
What your agent is told to do
5
What your agent is told to do
5-
1
Add a nullable assignee to the relevant records. Unassigned is a real, valid state — do not force a default owner just to avoid the null.
-
2
Restrict the picker to users who can actually access the item, and validate that server-side as well as filtering the list.
-
3
Notify the new assignee when they are assigned by someone else, and record every change with the actor and timestamp.
-
4
Show the assignee everywhere the record appears in a list, and let people filter by 'assigned to me'.
-
5
Do NOT notify on self-assignment, and do NOT re-notify when an unrelated field is saved. Those two mistakes are what make assignment features get muted.
Edge cases it handles
6
Edge cases it handles
6- A suspended, removed, or deleted assignee must not silently vanish from the record — surface it as needing reassignment.
- Bulk reassignment across many records must report which ones failed rather than reporting success for a partial run.
- Assignment history must survive the assignee's account being deleted; keep the name, not just the foreign key.
- Reassigning away should notify the outgoing owner too, otherwise they keep working on something that is no longer theirs.
- Rapid back-and-forth reassignment should collapse into one notification rather than several.
- Filtering by assignee must handle the unassigned case explicitly, not treat it as a missing filter.
Definition of done
8
Definition of done
8- Records can be assigned, reassigned, and unassigned.
- Only users with access to the item can be selected, enforced on the server.
- The assignee is visible in list views and filterable, including unassigned.
- Assignment changes notify the incoming and outgoing owners, but never on self-assignment.
- Every change is recorded with actor and timestamp and survives account deletion.
- Bulk reassignment reports per-record failures.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Voice Notes
Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it does
In-app recording of short audio notes attached to a record, comment, or message.
How it works
- 1 Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
- 2 Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
- 3 Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-notes
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Internal Notes
Internal Notes
Give staff a place to write things the customer must never see.
What it does
Notes attached to a record that are readable only by internal roles, and that never appear in any export, feed, or API response.
How it works
- 1 Model an internal note as a distinct visibility state on the server, not a flag the client filters on. Every read path — record view, search, digest emails, exports, webhooks, API serializers — must exclude internal notes for anyone without the internal role.
- 2 Give internal notes a visual treatment that cannot be confused with a public comment: different surface, a persistent label, and a warning that survives collapse or truncation. If a user has to remember which box is which, this feature has failed.
- 3 Decide explicitly what an impersonating admin or a support session sees, and state the rule in the UI. Support staff reading internal notes is usually fine; a support session rendering them inside a screen the customer is watching is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/internal-notes
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.