agentleFS
luckyfoxdesignluckyfoxdesign/llm-settings-template/.agents/skills/complete-task/SKILL.md

complete-task

Skill0 starsChanged 39 days agoMITView on GitHub

Verify, record, commit, and close an implemented task already in docs/wip. Use for task completion or closure; do not start implementation or close unfinished work.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. ModelEngine-Group/fit-framework★ 2.1ksame name
    2. huggingface/paperswithcode★ 315same name
    3. nockawa/Typhon★ 253same name
    4. fitlab-ai/agent-infra★ 87same name
    5. flurdy/agent-skills★ 9same name
    6. alxyrgin/agent-forge★ 4same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read and follow the complete algorithm in docs/workflows/task-lifecycle.md, section /complete-task Equivalent …

    line 11
  2. Distinctive:

    Use the user's arguments to identify the active task when supplied.

    line 12
  3. Distinctive:

    Create the long and short completion records, task-related commits, and final report exactly as the workspace algorithm requires.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Complete Task

Close one active task only after its contract is satisfied.

  1. Resolve this SKILL.md path, including symlinks, to locate its owning workspace with AGENTS.md and docs/workflows/task-lifecycle.md. If these are absent, report missing workspace setup.
  2. Read and follow the complete algorithm in docs/workflows/task-lifecycle.md, section /complete-task Equivalent (docs/workflows/task-lifecycle.md#complete-task-equivalent). Resolve these paths from the workspace root, not from the skill folder. The linked procedure owns lifecycle details.
  3. Use the user's arguments to identify the active task when supplied. Let the workspace algorithm handle a missing or ambiguous selection.
  4. Enforce the stop rule and executable gates. Do not bypass failures, omit required evidence, commit unrelated changes, or close an incomplete task.
  5. Create the long and short completion records, task-related commits, and final report exactly as the workspace algorithm requires.

Finish only when every required completion step succeeds.

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.