Skip to content
Skills Library
Programming · Building & coding

task

/task

Handle a small, low-risk change end to end - write a short task file in .caddis/projects/active/, make the change, verify, move it to completed and commit. Use when the user asks to create a task, make a quick fix or a small change. Escalates to /caddis:project if the work turns out bigger or riskier.

Repository
Caddis ↗
Licence
MIT
Last repository change
11.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 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Handle a small, low-risk change end to end - write a short task file in .caddis/projects/active/, make the change, verify, move it to completed and commit. Use when the user asks to create a task, make a quick fix or a small change. Escalates to /caddis:project if the work turns out bigger or riskier.

Original author description

Handle a small, low-risk change end to end - write a short task file in .caddis/projects/active/, make the change, verify, move it to completed and commit. Use when the user asks to create a task, make a quick fix or a small change. Escalates to /caddis:project if the work turns out bigger or riskier.

How it works

  1. 1. Qualify
  2. 2. Write the task
  3. 3. Do it
  4. 4. Close
Original SKILL.md headings · 74 lines, 488 words
SKILL.md preview
---
name: task
description: Handle a small, low-risk change end to end - write a short task file in .caddis/projects/active/, make the change, verify, move it to completed and commit. Use when the user asks to create a task, make a quick fix or a small change. Escalates to /caddis:project if the work turns out bigger or riskier.
---

A task is a project with less ceremony: a short record, then the work, in one go.

**Team rules.** If `.caddis/extend/task.md` exists, read it before anything else and follow
it. It adds to or overrides this skill, but it never removes a hard stop, weakens a gate,
silences a check or skips the gate-verifier.

**Too small for a task:** a typo, a copy or config value, a dependency bump with no
behaviour change, a comment or docs fix. Skip the task file: make the change, run the
relevant checks and commit with the `commit` skill, no Caddis trailer. Say so in one line.

## 1. Qualify

Read `.caddis/caddis.md`. It is a task only if **all** hold:
- About 3 files or fewer, in one layer
- Nothing on the Risk list (migrations, auth, payments, secrets, data deletion, public
  API or format changes, new runtime dependencies, anything repo-specific listed there)
- No Invariant touched
- No experiment needed: the right answer is not in doubt
- One commit can revert it

If any fails, say which, and follow the `project` skill instead. If one fails partway
through the work, stop, record what was found in the task file, and convert it to a
project: rename to `project-<name>.md`, fill the missing sections, leave it in `active/`.

## 2. Write the task

`.caddis/projects/active/task-<kebab-name>.md`, 15 to 30 lines:

```markdown
# <Title>

**Status:** In progress
**Type:** Task

## Goal
One sentence.

## Change
- `path/to/file` - what changes (function, line)

## Verify
- The command or check that proves it works

## Summary
One or two plain-language bullets for a non-developer.
```

If caddis.md's Plans section is set, its Tasks line decides the ending: `sections` means the
Required sections in their format, in place of `## Summary` unless Keep Summary is yes or
Product is on; `silent` means no Summary and the
Silent marker where it says.

Use `.caddis/map/STRUCTURE.md` and `python3 .caddis/bin/map.py uses <file>` to confirm nothing else depends on
what changes. If the user only wants it logged, stop here with `**Status:** Pending`. Running this skill
later on that task file picks up at step 3.

## 3. Do it

- Read every file before editing it. Grep before adding anything new; reuse first.
- Make the change. Run the checks from caddis.md's Commands (lint, typecheck, the relevant
  tests). Add or update a test when the change is logic, not copy or styling.
- Fix root causes. Never silence a check.

## 4. Close

- Append `## Outcome`: one or two lines on what was done, and anything unexpected. Check the
  ending from step 2 still matches what was done.
- Set `**Status:** Complete` and move the file to `.caddis/projects/completed/`.
- Use `git mv` when `.caddis/` is tracked, plain `mv` when it is gitignored.
- Commit the change and the task file together with the `commit` skill, with the
  `Caddis-Task: task-<name>` trailer.
- Report in two lines: what changed, the commit hash.

Versions

RepositoryScoreLicence
This page · adivmaimon/Caddis100MIT
SimHacker/moollm100MIT
mdiri-ai/SoduWork100MIT
codeaholicguy/ai-devkit100Apache-2.0
urikanonov/ai-marketplace100MIT
gridconsole/grid-plugins100MIT
editorgit/agentic-delivery100MIT
CipherNovaa/agent-skills100MIT
foxrun-ai/foxrun100MIT

Database snapshot: 13.11.2026 · package version 29e6d52819e7 (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

  • 100project
    Write a project file for a piece of work into .caddis/projects/active/ as project-<name>.md, without implementing it. Use when the user asks to create a project, write a plan or plan out a feature, including from an intent file or a ticket key. Triages small low-risk work to /caddis:task instead.
  • 90quick
    Make one small change (a bug fix, a chore, a tweak to existing behaviour) in a single pass without a spec or plan - reproduce, red/green when behaviour changes, run checks, commit. Hands the task back with a recommendation when it turns out bigger. Use for work under about an…
  • 100brief
    Brief a small change, then implement, review and verify it, with no plan file. Use when someone asks for "a quick fix", "a small change", "can you tweak", "change this text", "fix this bug", "add a button", "update the docs", one clear thing with one obvious approach; also the…
  • 90execute
    Execute one active project end to end - read it, confirm the code matches, implement phase by phase, pass each gate, test, commit each chunk and complete it. Use for a single project; /caddis:build runs this across many.
  • 100fast-small-task
    Deliver a small, low-risk change in an existing codebase with the minimum edit and targeted verification, then hand off to fast-small-review. Use for a single page, component, module, copy, style, config value or simple bug fix ("hide this button", "change this message", "fix…
  • 95wayfare-build-task
    Build one small task through planning, implementation, review, and shipping, or resume the current goal. Use for a low-risk change that fits one PR. Route larger or irreversible work through wayfare-sync-plan.

Feedback and reports

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