agentleFS
Sign inStart free
AgiFlowAgiFlow/ai-plugin/skills/refine-task/SKILL.md

refine-task

Skill4 starsChanged 33 days agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. ModelEngine-Group/fit-framework★ 2.1ksame name
    2. b-mendoza/agent-skills★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call get_task for full details and list_task_comments when prior decisions may affect scope.

    line 13
  2. Very specific:

    Call list_project_statuses and list_members only when status or assignment context is relevant.

    line 14
  3. Distinctive:

    Ask focused clarification questions for unresolved decisions.

    line 22
  4. Very specific:

    After approval, call update_task with only the fields that need to change.

    line 25
  5. Very specific:

    Call get_task again to verify the saved result.

    line 26
  6. Distinctive:

    Do not add new product requirements during refinement.

    line 34
  7. Distinctive:

    Do not move the task from Planning to Todo.

    line 35
  8. Distinctive:

    Do not delete the task.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agiflow Refine Task

Make the selected task ready for confident execution while preserving its original intent.

Workflow

  1. Resolve the task with get_current_scope, list_projects, list_tasks, or get_task as needed.
  2. Call get_task for full details and list_task_comments when prior decisions may affect scope.
  3. Call list_project_statuses and list_members only when status or assignment context is relevant.
  4. 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
  5. Ask focused clarification questions for unresolved decisions. Do not invent requirements.
  6. Draft the refined title, description, acceptance criteria, scope boundaries, and dependency notes.
  7. Show the proposed changes and request approval.
  8. After approval, call update_task with only the fields that need to change.
  9. Call get_task again 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free