agentleFS
Sign inStart free
luckyfoxdesignluckyfoxdesign/llm-settings-template/.agents/skills/start-task/SKILL.md

start-task

Skill0 starsChanged 40 days agoMITView on GitHub

Start or resume implementation of an existing workspace task in docs/backlog/todo or docs/wip, including a partial filename. Do not create a new task or close the lifecycle.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

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 14 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. Distinctive:

    Start one existing backlog task and follow it through implementation.

    line 8
  2. Very specific:

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

    line 11
  3. Distinctive:

    Use the user's arguments as a task filename or substring.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 14 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

Start Task

Start one existing backlog task and follow it through implementation.

  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 /start-task Equivalent (docs/workflows/task-lifecycle.md#start-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 as a task filename or substring. Let the workspace algorithm handle a missing or ambiguous selection.
  4. Present the frozen contract and plan. Reuse authorization already supplied in this conversation; otherwise follow the plan confirmation boundary in the procedure.
  5. Continue following the workspace algorithm after approval. Do not skip verification, expand the frozen contract without external evidence, or complete the task lifecycle on the user's behalf.

Finish with the exact result text required by the workspace algorithm.

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