benoror/obsidianos_work / .agents/skills/followup-todos
followup-todos
VerifiedExtract 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).
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 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 and obsidian-tasks 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 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 Β§ 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):
- 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. [!gemini_todos]callout: Gemini's "Suggested Next Steps" β explicit action items.[!gemini_notes]callout: Summary & Details β scan for implicit commitments ("will do X", "agreed to Y", "plans to Z").- 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:
-
Owner: Who is responsible? See people-resolver for name matching and assignee rules.
-
Relevance: Score as
high,medium, orskip:- 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.
-
Priority (for the proposal table only): Based on urgency and impact (see priorities in obsidian-tasks). When inserting bullets, you may end the line with a single priority emoji (
πΊβ«πΌπ½) as plain text β never as Tasks metadata. -
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:
- 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:
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. 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |