Skip to content
Back to skills

Followup Todos

ASecurity

Extract action items (with confirmation). Inserts plain bullets on most notes; Daily Standup/scrum notes skip body inserts and only set TodosExtracted. Args: <path>. No args = run [/note-status pending --step=todos](../note-status/SKILL.md#pending-mode).

  • 165 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agents

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add benoror/obsidianos_work --skill followup-todos --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Followup Todos?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Followup Todos
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/benoror-followup-todos/badge)](https://www.skillsdirectory.com/skills/benoror-followup-todos)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: followup-todos
description: "Extract action items (with confirmation). Inserts plain bullets on most notes; Daily Standup/scrum notes skip body inserts and only set TodosExtracted. Args: <path>. No args = run [/note-status pending --step=todos](../note-status/SKILL.md#pending-mode)."
license: MIT
---

# Follow-up Todos

## Usage

- `/followup-todos <path>` — Extract and propose follow-ups from a specific meeting note.
- `/followup-todos` (no args) — Run [/note-status pending --step=todos](../note-status/SKILL.md#pending-mode) to show meetings missing follow-up extraction. The user picks one (or more) to process.

## Output format (mandatory)

When writing follow-ups into a note body (non-scrum only):

- **Never** insert Obsidian **Tasks** / checkbox lines: no `- [ ]`, `- [x]`, `- [-]`, or any `- [?]` pattern.
- **Never** append **Tasks-plugin** inline metadata on inserted lines: no `📅`, `🛫`, `⏳`, or other parsed task tokens. (Optional **priority emoji** at the very end as plain text — e.g. `🔼` — is fine if it reads naturally in prose.)
- **Always** insert **plain list items**: `- Description…` Wikilinks (`[[@Name]]`, `[[+Team]]`) and **bold** are allowed.

**Daily Standup / scrum exception:** `Meetings/*/Scrum/YYYY-MM-DD.md` never gets follow-ups in the note body. Still extract, present for review, and set `TodosExtracted:`.

## Prerequisites

The meeting file should ideally have cached AI transcripts (from `/cache-notes`). If not cached, suggest running `/cache-notes <path>` first. However, the skill also works on notes with only manual content.

## Optional context

For **classification** (owner, urgency, dates in the proposal step), you may still use [people-resolver](../_shared/people-resolver.md) and [obsidian-tasks](../_shared/obsidian-tasks.md) as *reference* — but **do not** copy Tasks checkbox or date-token syntax into the note.

## Workflow

### Step 1: Read the meeting note and gather context

See [vault-context](../_shared/vault-context.md) for vault discovery conventions.

Read the entire file. Cross-reference ticket status via an external tracker when configured (e.g. Jira). Optionally consult a **live** Tracker if present (see [vault-context](../_shared/vault-context.md) § Ticket / sprint status). This helps:
- **Set priority**: Keep known high priorities (external tracker or live Tracker `🔺`) as trailing emoji if you include one.
- **Avoid duplicates**: If a follow-up already exists for the same ticket (note, ToDo's, or live Tracker), flag it in the proposal table (Step 3).
- **Add context**: If the meeting references a ticket ID (e.g. `PROJ-1234`), pull current status and assignee from the external SoR when available.

Extract action items from **all** content sources, skipping lines that are **already captured** as follow-ups (compare meaning, not only exact text):

1. **Manual notes** (between frontmatter `---` and `## 🤖 AI Notes`): Free-text action items (e.g. "- Talk to Alex about X"). Skip lines that are **checkbox** tasks (`- [*]` — any single character between brackets) when **deduplicating**, but note the vault may still contain legacy `- [ ]` lines from older runs.
2. **`[!gemini_todos]` callout**: Gemini's "Suggested Next Steps" — explicit action items.
3. **`[!gemini_notes]` callout**: Summary & Details — scan for implicit commitments ("will do X", "agreed to Y", "plans to Z").
4. **Other provider callouts**, if a vault still has them: same treatment as Gemini.

Also extract:
- Existing **plain** bullets and **checkbox** lines in the follow-up section to avoid duplicates
- `Participants:` from frontmatter (to resolve assignees)
- Meeting date (from filename or `created:` frontmatter)

### Step 2: Classify each action item

For each candidate action item (from manual notes, transcript todos, or implicit commitments in details), determine:

1. **Owner**: Who is responsible? See [people-resolver](../_shared/people-resolver.md) for name matching and assignee rules.

2. **Relevance**: Score as `high`, `medium`, or `skip`:
   - **High**: Action is for the user, has a clear deliverable, or is time-sensitive.
   - **Medium**: Action is for someone else but the user should track it, or it's vague but potentially important.
   - **Skip**: Purely informational, already completed (based on date vs today), or not actionable.

3. **Priority** (for the proposal table only): Based on urgency and impact (see priorities in [obsidian-tasks](../_shared/obsidian-tasks.md)). When inserting bullets, you may end the line with a single priority emoji (`🔺` `⏫` `🔼` `🔽`) as **plain text** — never as Tasks metadata.

4. **Dates**: Note due/start in the **proposal table** when helpful; **do not** put `📅` / `🛫` / `⏳` on inserted lines. If a date matters, write it in words in the bullet (e.g. "by **2026-03-26**").

### Step 3: Present proposals to the user — MANDATORY CONFIRMATION

**⚠️ STOP HERE AND WAIT FOR USER CONFIRMATION. Never skip this step, even during `/meeting wrap` sequences. Do NOT write follow-ups to the file until the user explicitly approves.**

Display a numbered table:

```
| # | Add? | Follow-up | Owner | Priority |
|---|------|-----------|-------|----------|
| 1 | ✅   | Talk with Alex about temp environments | Me | 🔼 |
| 2 | ✅   | Offload data lake work to Jane | Me | ⏫ |
| 3 | ⬜   | Confirm travel plans for Friday | [[@Sam Rivera]] | — |
| 4 | ⬜   | Verify production deploy completed | Me | 🔼 |
```

- Default `✅` for high-relevance items owned by the user.
- Default `⬜` for others' items or skippable ones.
- Let the user toggle by saying numbers (e.g. "1,3,4" or "all" or "none except 2").

### Step 4: Insert confirmed follow-ups

**Only proceed after the user has explicitly confirmed which items to include (Step 3).**

Insert each confirmed item as **one line**:

```markdown
- Clear, self-contained description (optional **bold**, `[[@Name]]`, optional trailing 🔼)
```

**Do not** use `- [ ]`. Placement depends on the note's template:

#### Daily Standup notes (`Meetings/*/Scrum/YYYY-MM-DD.md`)

These follow the [Daily Standup template](../../../Templates/Daily%20Standup.md):

```
Yesterday
- ...
Today
- ...          ← INSERT FOLLOW-UPS HERE (append after existing Today items)
Blockers
- ...
---
Pending/Carry-over Backlog
- ...
```

Insert at the **end of the "Today" section**, just before the `Blockers` line. Use `StrReplace` targeting `Blockers` as the anchor.

#### Other meeting notes

Prefer a dedicated section heading if missing, e.g. `## Follow-ups`, placed after the title / any manual notes and **before** `## 🤖 AI Notes`. If a `## Follow-ups` (or equivalent) section already exists, **append** there. If neither heading exists, append after the frontmatter closing `---` and add `## Follow-ups` first.

#### General rules

- Group by owner if multiple people are involved (optional sub-bullets under a short `**[[@Name]]**` line).
- Preserve existing content — always append, never overwrite.

### Step 5: Mark as processed

After inserting, add a `TodosExtracted: YYYY-MM-DDTHH:MM:SS±HH:MM` frontmatter property to prevent re-processing. This is required — `/meeting wrap pending` relies on it to detect unprocessed meetings.

### Step 6: Offer to commit

See [/commit](../commit/SKILL.md). Skip when called as part of a sequence (e.g. `/meeting wrap`).

## Important Notes

- Always read the file before editing — frontmatter may have changed since your last read.
- Do NOT duplicate follow-ups that already exist in the note body (compare by description similarity).
- When in doubt about relevance, include it as `⬜` in Step 3 and let the user decide.
- If the meeting is old (>2 weeks), flag items that may already be completed and suggest skipping them.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.