Todoist Task Creation
Let a user send any app record to their own Todoist with project, label, and due date.
What it adds
A per-user Todoist connection and a send action that creates a personal task carrying a link back to the source record.
What your agent is told to do
5
What your agent is told to do
5-
1
Make this a per-user connection, not a workspace one. The task lands in that person's own account, so the authorisation, the project list, and the disconnect control all belong on their account settings.
-
2
Add a send action to the record types a person would realistically want on a personal list, and let them choose the project, label, priority, and due date at send time with their last choice remembered as the default.
-
3
Send an explicit date or timestamp for the due date, resolved in the user's own time zone before it leaves the app. Do not pass through a phrase like tomorrow and rely on the provider parsing it, because the parse depends on a locale and a clock you do not control.
-
4
Include a link back to the source record in every task, so the person reading it a week later can get to the thing it refers to.
-
5
Store the created task identifier against the source record and the user, so a repeat send updates or refuses rather than stacking duplicates, and so the app can show that this record has already been sent.
Edge cases it handles
8
Edge cases it handles
8- Natural-language due dates are interpreted by the provider against a time zone and a reference clock the app does not own, which turns a local deadline into the wrong day. Resolve to an explicit timestamp in the user's time zone first.
- A project or label chosen months ago can be archived, renamed, or deleted. Re-check the target before sending, and prompt the user to pick again instead of dropping the task into the default inbox without saying so.
- A retried send after a network timeout produces two identical tasks. Guard creation with a stable key derived from the record and the user, and reconcile against the stored task identifier.
- A backlink pointing at a record the recipient cannot open is useless. Link to the canonical record URL and let the app's own access rules handle the rest.
- Personal projects can be shared with other people. Do not put customer names, internal notes, or private context into the task body by default; put the summary in the task and keep the detail behind the backlink.
- The user's authorisation expires or is revoked from Todoist without warning. Detect the failure, mark the connection as disconnected on their settings screen, and stop retrying.
- A person sending several records in a row will hit the rate limit. Queue the sends, back off on the provider's signal, and show each task as pending until it is confirmed.
- When Todoist is unavailable the send must fail visibly and recoverably. Tell the user it did not go through and let them retry, rather than showing a success that never happened.
Definition of done
8
Definition of done
8- Each user connects and disconnects their own Todoist account from their account settings.
- Due dates arrive as explicit timestamps resolved in the user's time zone, with no reliance on provider-side parsing.
- A missing, archived, or renamed project or label prompts the user rather than silently redirecting the task.
- Sending the same record twice does not create two tasks, and the app shows that the record was already sent.
- Every created task contains a working link back to the source record.
- An expired or revoked connection is surfaced on the user's settings screen and stops further retries.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
Assign Ownership
Assign Ownership
Make it obvious who is responsible for each record.
What it does
An assignee on records, with a picker, notifications on change, and a history of who owned what.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/assign-ownership
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.