Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rfc123-skills
Extracts explicit owner+action items from RFC discussions and posts a trackable checklist comment. Useful when commitments are buried in long threads.
npx claudepluginhub twixes/rfc123How this skill is triggered — by the user, by Claude, or both
Slash command
/rfc123-skills:extract-action-itemsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pull explicit action items out of an RFC's discussion and post them as a
Synthesizes long RFC discussions into structured summaries grouped by theme, distinguishing settled and unresolved points, and posts the roll-up as a comment.
Extracts action items, commitments, assignments, and follow-ups from Fireflies meeting transcripts for all attendees (default) or a specific person using parallel subagents and MCP tools.
Extracts action items and assignees from meeting notes or Confluence pages, looks up Jira account IDs, and creates tasks.
Share bugs, ideas, or general feedback.
Pull explicit action items out of an RFC's discussion and post them as a markdown checklist.
The discussion has reached a point where commitments are being made ("I'll do X", "@person to do Y") but nobody has rolled them up. Or the user says "what are the action items?"
Read every comment. Call rfc123_get_rfc_comments.
Find explicit owner+action pairs. An action item has:
@login or an unambiguous "I'll" with author attribution)"@alice can you check?" → not an action item (question). "@alice will check with infra" → action item. "I'll write up the migration steps" by @alice in comment → action item.
Skip near-misses. If there's ambiguity about who owns it or what exactly they'll do, leave it off the list and note it as a follow-up question for the user.
Format the checklist. Use GitHub task-list syntax so reviewers can tick items off:
## Action items
- [ ] @alice — write up the migration steps (from <link or quote>)
- [ ] @bob — confirm with infra whether <thing> is feasible
Include source citations. Link to or quote the comment where each item was committed to. Without this, owners can dispute attribution.
Post it. Call rfc123_post_general_comment.