Skip to content
Skills Library
Management & product · Planning

open-task

/open-task

Write one task record: choose delivery or probe, write the action and its acceptance signal, and set the kind, reversibility, and whether a person is needed. Use when a layer is being split into tasks, or when a task has to be written outside a split.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 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.
Content25 / 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 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Write one task record: choose delivery or probe, write the action and its acceptance signal, and set the kind, reversibility, and whether a person is needed. Use when a layer is being split into tasks, or when a task has to be written outside a split.

Original author description

Write one task record: choose delivery or probe, write the action and its acceptance signal, and set the kind, reversibility, and whether a person is needed. Use when a layer is being split into tasks, or when a task has to be written outside a split.

How it works

  1. When it runs
  2. Steps
  3. Hands off
  4. What this skill does not do
Original SKILL.md headings · 31 lines, 376 words
SKILL.md preview
---
name: open-task
description: "Write one task record: choose delivery or probe, write the action and its acceptance signal, and set the kind, reversibility, and whether a person is needed. Use when a layer is being split into tasks, or when a task has to be written outside a split."
family: track
invocation: model
---

# Open task

One task per run: the finest record of the tree, one action that ends at a result someone can hand over and someone else can check. This action writes the record and nothing else: it does not decide how many tasks there are or where they hang. What the record holds is the `task` skill's; which part of the map each serves, and the parent it hangs under, came in with the call.

## When it runs

- `split` decided a layer is tasks, and calls this action once per task, with the action, the acceptance signal, the kind, the part it serves, and the parent map.
- A person has one piece of work to record, and no split is involved; the parent map is named with it.

A task is never a child of a task. The parent is a map, written with `--parent` on the create command.

## Steps

1. **Read the part it comes from.** The parent map's `Target` and `Acceptance direction`, and the decision the caller says this task serves. The action serves a part of the map's direction; if it serves something else, the map is wrong.
2. **Write the body** as `task/res/body.md` requires: `Action` with its result first, `Acceptance signal`, the sections the kind requires, and `Boundaries` when the work could be mistaken for more than it is.
3. **Set the fields** the `task` skill defines: `task_kind`, `reversibility`, and `needs_human`. `waymark/res/fields.md` says when each is written and which values it takes.
4. **Create the record**, hung under the map given with the call. `waymark create --category task --title "<the result>" --owner <name> --parent <map> --field task_kind=… --field reversibility=… --field needs_human=… --body-file <body> --dry-run`, then again without the flag.

If the part turns out to need a child map instead, write nothing and report it: the layer's type is `split`'s decision, and a layer is all one type.

The task exists, and `task/res/body.md` says what it holds.

## Hands off

The task exists, and this action writes nothing after it. `split` started the map on its first split; the task is advanced by `advance-task` when the person asks for it.

## What this skill does not do

- Decide how many parts the layer has; `split` does.

Versions

The database has no other skills named open-task.

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

  • 90task-review
    Judge a finished task against the acceptance signal written before the work started, give each axis its own verdict, and record both with their evidence. Use when a task has a Result and has to close, or when a task comes back after a fix.
  • 81task_select
    Select and rank eligible live tasks from the project backlog. Use when the user asks what task to work on next, asks the agent to pick or prioritize backlog work, rank open tasks, choose from tasks/, or recommend the next task/action without editing task files.
  • 96product-delivery
    Use for idea assessment, requirements, issue triage, prioritization, or delivery planning; do NOT use for ordinary code tasks (those go through task-intake).
  • 100verify-task
    Run verification checks for a task and evaluate results. Use when the user wants to verify a task's acceptance criteria.
  • 100task
    在 SoduWork 里管任务:把聊清楚的事建成任务、顺手派给 AI 执行机或起流程、查自己名下的任务、改状态和验收要点。当人说「帮我建个任务」「这件事交给 AI 去做」「我手上还有什么活」「把这个标成做完了」,或者你们已经把一件事聊明白、该落成一条任务时使用。
  • 100write-acceptance-criteria
    Use when the user asks to define acceptance criteria, write a spec for a task, clarify what "done" looks like, or translate a vague goal into testable requirements. Triggers on "acceptance criteria", "definition of done", "how will we know this works", "spec for".

Feedback and reports

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