refine-task
Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- refine-task
- description
- Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.
03 SKILL.md 正文
Agiflow Refine Task
Make the selected task ready for confident execution while preserving its original intent.
Workflow
- Resolve the task with
get_current_scope,list_projects,list_tasks, orget_taskas needed. - Call
get_taskfor full details andlist_task_commentswhen prior decisions may affect scope. - Call
list_project_statusesandlist_membersonly when status or assignment context is relevant. - Evaluate the task for:
- Clear user or business outcome
- Concrete scope boundaries
- Objective acceptance criteria
- Known dependencies and blockers
- Appropriate priority and assignee
- Enough context to complete without guessing
- Ask focused clarification questions for unresolved decisions. Do not invent requirements.
- Draft the refined title, description, acceptance criteria, scope boundaries, and dependency notes.
- Show the proposed changes and request approval.
- After approval, call
update_taskwith only the fields that need to change. - Call
get_taskagain to verify the saved result.
Quality Test
Acceptance criteria must be specific, measurable, achievable within the task, relevant to its outcome, and directly verifiable. Replace phrases such as "works correctly" or "handles errors" with observable behavior.
Guardrails
- Do not add new product requirements during refinement.
- Do not move the task from Planning to Todo. Backlog grooming owns that transition.
- Do not delete the task.
- Preserve useful existing context and comments.
Response
Summarize what changed, which ambiguities were resolved, and whether the task is ready for backlog-grooming.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.