Coordinate care for an aging parent with your siblings
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Show all 6Show fewer
Methods
Paste into a general LLM and coordinate care for an aging parent with your siblings.
LLMPrompt
Prompt
Copied 0
Help me set up a care plan for my aging parent that my family can share. **Parent's situation:** [AGE, LIVING ARRANGEMENT, WHAT THEY CAN AND CAN'T DO ALONE] **Health conditions and care needs (as told by their doctors):** [LIST] **Family members and what each can give:** [NAMES, DISTANCE, TIME, MONEY, SKILLS] **Current tasks:** [e.g. "appointments", "medications", "groceries", "bills", "house upkeep", "companionship"] **Parent's wishes:** [WHAT THEY WANT - e.g. "stay at home"] **Tension or gaps:** [e.g. "one sibling does everything", "no one manages finances"] Create: 1. A task table: task | how often | who owns it | backup | notes. 2. A shared calendar structure for appointments and visits. 3. A one-page "care binder" outline: contacts, medications, doctors, insurance, legal documents to look into (e.g. healthcare proxy, power of attorney), and where originals are kept. 4. A monthly family check-in agenda and a fair way to raise imbalance without blame. 5. Signs that more support may be needed and the kinds of local services to research (home care, adult day programs, respite care). 6. Caregiver self-care: how to share load and avoid burnout. Keep my parent's voice central. For legal and financial documents, tell us to confirm requirements with a qualified professional where we live.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/coordinate-care-for-an-aging-parent - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "coordinate-care-for-an-aging-parent",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}