Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From astravue
Decomposes goals, features, or epics into structured task trees with dependencies using Astravue. Use when planning, scoping, or breaking down work.
npx claudepluginhub astravueorg/astravue-mcp-server --plugin astravueHow this skill is triggered — by the user, by Claude, or both
Slash command
/astravue:breaking-down-workThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Decompose complex initiatives into manageable work items with clear ownership and milestones. Use when planning large features or multi-team projects.
Decomposes specs into ordered, verifiable tasks with acceptance criteria using vertical slicing and dependency graphs. Use for large tasks, scope estimation, or parallel agent work.
Convert technical designs into actionable, tracked task hierarchies with sizing, dependencies, and acceptance criteria. Invoke whenever task involves any interaction with work decomposition — breaking down features into subtasks, slicing work items, creating task lists, or writing decomposition documents.
Share bugs, ideas, or general feedback.
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.