agentleFS
Sign inStart free
grandameniumgrandamenium/cortextos/skills/tasks/SKILL.md

Task System

Skill106 starsChanged 7 months agoMITView on GitHub

Create, manage, and complete tasks in cortextOS. Use when starting significant work, tracking progress, or completing deliverables.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every significant piece of work must have a corresponding task.

    line 8
  2. Distinctive:

    Log KPIs: - when work advances a measurable goal

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 System

Every significant piece of work must have a corresponding task. Tasks enable coordination, accountability, and measurable progress.

Task Types

  • Agent tasks - Work executed autonomously by the assigned agent
  • Human tasks - Requires human decision, input, or approval (assigned_to=human)

Lifecycle

1. Create (BEFORE starting work)

cortextos bus create-task \
  "<title>" "<description>" [assignee] [priority] [project]

2. Mark in progress

cortextos bus update-task <task_id> in_progress

3. Execute the work

4. Complete

cortextos bus complete-task <task_id> "[output summary]"

5. Log KPI (if measurable)

cortextos bus log-event action task_completed info \
  '{"task_id":"ID","kpi_key":"metric_name","value":1}'

The needs_approval Field

true - external actions: sending emails, merging PRs, deploying, public announcements false - internal work: research, drafts, feature branches, testing

Tasks with needs_approval: true create an approval item that must be reviewed before executing external actions.

Script Reference

ActionCommand
Createcortextos bus create-task "<title>" "<desc>" [assignee] [priority] [project]
Listcortextos bus list-tasks [--status S] [--agent A] [--priority P]
Updatecortextos bus update-task <id> <status> [note]
Completecortextos bus complete-task <id> "[summary]"
Log eventcortextos bus log-event <category> <event> <severity> '[json]'

Statuses: pending, in_progress, blocked, completed

Priorities: high, normal, low

Best Practices

  • Always create before starting - ensures tracking and coordination
  • Be specific - clear titles, descriptions with success criteria
  • Complete thoroughly - include what was accomplished and where outputs are
  • Log KPIs - when work advances a measurable goal

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