Skip to content
Skills Library
Management & product · Writing

agent-task

/agent-task

Use when writing or drafting a GitHub issue that an AI coding agent will carry out - an issue finished in one session and one pull request, with the sections Context, Scope, Out of scope, Acceptance criteria, Tests, Depends on and Model, and the model chosen by the rules here.

Repository
fleet ↗
Licence
AGPL-3.0
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Use when writing or drafting a GitHub issue that an AI coding agent will carry out - an issue finished in one session and one pull request, with the sections Context, Scope, Out of scope, Acceptance criteria, Tests, Depends on and Model, and the model chosen by the rules here.

Original author description

Use when writing or drafting a GitHub issue that an AI coding agent will carry out - an issue finished in one session and one pull request, with the sections Context, Scope, Out of scope, Acceptance criteria, Tests, Depends on and Model, and the model chosen by the rules here.

How it works

  1. Size
  2. Sections
  3. The model
  4. Drafts that refer to each other
  5. No personal data
  6. A UI issue
Original SKILL.md headings · 38 lines, 463 words
SKILL.md preview
---
name: agent-task
description: Use when writing or drafting a GitHub issue that an AI coding agent will carry out - an issue finished in one session and one pull request, with the sections Context, Scope, Out of scope, Acceptance criteria, Tests, Depends on and Model, and the model chosen by the rules here.
---

# Writing an agent task

An agent task is an issue one agent finishes in one session and one pull request. It decides everything a user would notice, so the agent never has to choose; anything it leaves open, the agent asks about instead of guessing.

## Size

One session, one pull request. If the work needs two pull requests that land one after the other, or two areas that could be worked on at once, write two issues and say which depends on which.

## Sections

Write them in this order, each as a bold heading line (`**Context**`):

- **Context**: why the work is needed and what exists today, with the real file names, commands and statuses (`src/app/settings.py`, `make verify`, "Merge gate"). Never a made-up or approximate path: check it exists.
- **Scope**: what to build, as a list. Name the files to add or change and the behaviour each must have; settle every decision a user would notice.
- **Out of scope**: what the agent must not do, including the neighbouring work another issue does (name that issue).
- **Acceptance criteria**: checkboxes (`- [ ]`), each one something the pull request can show: a command's output, a test that fails before the change, an image. "Works well" isn't a criterion.
- **Tests**: the test files to add or extend and the checks to run.
- **Depends on**: the issues that must merge first, or "Nothing".
- **Model**: the model to run the session on, and why in a few words.

## The model

- **Opus** by default, at `xhigh` effort (the Agent tool's `effort: xhigh`), including security work, the review workflows, CI secrets, anything that handles untrusted pull request content, and security scanning.
- **Sonnet** only for mechanical copying: renames, typo fixes, moving text without changing it.

## Drafts that refer to each other

While a set of issues is still a draft, refer to one that doesn't exist yet by its key in double curly braces, `{{FLEET-SYNC}}`; replace each with the issue's number once it's created. A key is short, upper case and stable (`PROJECT-PIECE`).

## No personal data

In a public repository, an issue holds nothing personal: no person's name, address, account, email address, host or domain of anyone's own, token, key or anything copied from a real instance of an app. Examples use made-up values. In a private repository, still keep it to what the work needs.

## A UI issue

An issue that changes anything a person sees adds this criterion: the UI matches the signed-off design (name the issue that signed it off), any change to layout, flow or visual style needs the owner's sign-off before merge, and the pull request shows `make verify` images at phone and desktop width. The design-signoff skill says what counts.

Versions

The database has no other skills named agent-task.

Database snapshot: 13.11.2026 · package version eb09e231ea56 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100issue-creation
    Create clear issue drafts with reproducible context, acceptance criteria, and definition of done. Trigger: when the user asks to open a bug report, feature request, chore, or tracking issue.
  • 90issue-plan-slicer
    Convert a spec, roadmap item, or rough plan into independently implementable issue slices with scope, dependencies, acceptance criteria, and validation. Use when the user asks to split work into GitHub issues, local markdown tasks, or agent-ready implementation chunks.
  • 86po
    Product owner phase. Turn a need into clear, confirmed GitHub issues with acceptance criteria. Use when the user says "po", "create an issue", "ticket this", or "write the requirement".
  • 90task-ledger
    Use when turning a plan into trackable tasks and working them to done — a lightweight issue tracker for an orchestrated run. Covers the task format (acceptance criteria, status, dependencies, assigned agent + model) and three backends: local markdown files (default), GitHub…
  • 100charter
    Turn a rough request into a well-formed, fleet-ready GitHub issue — then arm it. charter drafts a structured issue (imperative title, problem/goal, concrete testable acceptance criteria, scope, dependencies, notes) following issue best practices and this repo's house style,…
  • 100dx-implement-issue
    Use when someone wants an existing GitHub issue built, for example "implement issue 142", "pick up this issue", "build the story in issue 98", or when they paste an issue body and ask for the code. Reads the issue, checks it is specific enough to build, plans against its…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.