菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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".
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 | breaking-down-work |
| description | 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. |
Turns a high-level goal into a complete, well-scoped task tree. The value is in the decomposition and sequencing — not in the tool calls — so spend effort on coverage and structure, then create in one confirmed pass.
Understand the goal and scope
Clarify the deliverable and the target project. Use astravue_list_projects if the project is unclear. If the work hangs off an existing task, note its ID — the new tasks become subtasks of it.
Decompose to full coverage
Break the goal into tasks, then subtasks, then checklist items where useful. Aim for the 100% rule: the children together fully cover the parent's scope with no overlap. A leaf is small enough when one person can finish it in a sitting and you can tell when it's done.
astravue_create_subtask) — steps within a taskastravue_create_checklist_item) — acceptance criteria or fine-grained todosSequence the work
Identify which tasks block others. Capture these as dependencies. Flag anything that can run in parallel so the plan doesn't serialize work that needn't be.
Present the plan and confirm
Show the full tree (task → subtasks → checklist), proposed dependencies, and any estimates, as a structured outline. Ask the user to adjust or approve. Do not create anything before approval — decomposition is cheap to revise on paper and expensive to undo in the workspace.
Create after approval
astravue_bulk_create_tasks — create the top-level tasks in one callastravue_create_subtask — add subtasks under each taskastravue_create_checklist_item — add checklist itemsastravue_add_dependency — wire up the blocking relationshipsReport back what was created with IDs so the user can navigate to it.