agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/task-spec/SKILL.md

task-spec

Skill0 starsChanged 7 days agoMITView on GitHub

Writes a clear task specification before delegating work to a coding agent or starting a non-trivial change. Use when the user describes a feature, bug, refactor or automation loosely; before long-running or unattended agent work; or when the user asks for a spec, plan, ticket, goal or "done when" criteria. Produces Goal / Context / Constraints / Done when, with a verifiable check.

  • Reads credentials

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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:

    Make "done" verifiable: Every item under *Done when* should be checkable by running something, not by opinion.

    line 35
  2. Very specific:

    Move non-negotiable rules out of prose: If a rule must never be broken (don't read .env, don't touch migrations/), recommend enforcing it …

    line 37

“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

Task spec

Most disappointing agent sessions trace back to missing information, no way for the agent to check its own work, or rules nothing enforces. A short spec fixes the first two.

Steps

  1. Gather facts, but don't stall. If you can read the code, docs or data, read the relevant parts first so the spec refers to real files and behavior (don't change anything yet). If you can't access them, or the user only wants the instructions written, write the spec now from what you were told: put unknowns in angle brackets (<file?>, <current p95 latency?>) and list the questions or measurements needed to fill them.
  2. Write the spec:

    ## Goal
    What changes and why, in one or two sentences.
    
    ## Context
    - Relevant files: ...
    - Current behavior / symptom (exact error, reproduction steps): ...
    - Existing pattern to follow: ...
    
    ## Constraints
    - Out of scope / don't touch: ...
    - No new dependencies without asking.
    
    ## Done when
    - [ ] A check that can be run and returns pass/fail (test, build, script, screenshot comparison)
    - [ ] ...
    - [ ] Report: what changed, the commands run and their output, remaining risks
  3. Make "done" verifiable. Every item under Done when should be checkable by running something, not by opinion. For bugs, the first item is a failing test that reproduces the bug (red), which must pass afterwards (green).
  4. Size the process to the task. A small bug needs a paragraph; a large feature may need a plan the user approves before any code is written.
  5. Move non-negotiable rules out of prose. If a rule must never be broken (don't read .env, don't touch migrations/), recommend enforcing it with permission rules, hooks or CI rather than the spec alone.

Evidence

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.