菜单
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown structure.
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.
Reviews overdue and at-risk tasks in Astravue, assesses why each is slipping, and proposes reschedule, reassign, deprioritize, or close actions before applying them. Use when the user asks what's overdue, behind schedule, slipping, or at risk, wants to catch up on a project, or clean up late work.
Generates executive project status reports from Astravue data including task progress, budget consumption, and project health. Use when asked for a status update, project summary, executive report, or "how is the project going?".
Creates, configures, and manages custom fields and dropdown options on tasks in Astravue. Use when working with custom fields, adding dropdown options, setting field values on tasks, or asking "what custom fields does this project have?".
Plans sprints by analyzing project backlog, overdue tasks, and dependencies in Astravue. Use when planning a sprint, organizing upcoming work, asking "what should we work on next?", or reviewing the backlog.
| name | capturing-meeting-actions |
| description | Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this". |
Converts unstructured discussion into structured, traceable tasks. Every action item should end up with an owner, a due date, and a link back to where it came from — that traceability is what makes the output trustworthy.
Read the source and extract candidate actions
Pull every commitment, decision-with-follow-up, and "someone should…" out of the notes. For each, capture:
Ignore pure status updates and discussion that produced no commitment.
Resolve owners to workspace members
For each named owner, resolve to a real member with astravue_get_member_by_email (if an email is given) or astravue_get_workspace_members (to match by name). Flag any owner you can't resolve rather than guessing.
Pick the target project
Confirm which project the tasks belong to. Use astravue_list_projects if unclear.
Present the action list and confirm
Show a table: title | owner | due date | source. Mark rows missing an owner or due date so the user can fill them. Ask for approval before creating anything.
Create after approval
astravue_bulk_create_tasks — create the confirmed action items in one callastravue_add_task_comment — optionally attach the source line as a comment for contextReport which tasks were created, and re-list any items that were skipped because they lacked an owner or due date.