OpenParable
Skip to content
← Back to skills

Organize Task Files

Productivity
organize-task-files

Organize Task Files is an Agent Skill for productivity published in the platonai/Browser4 repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Lists, pairs, deduplicates, and moves task files across the Coworker task state machine (0draft → 6git-pushed). Use when asked to organize, clean up, or audit task files.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/platonai/Browser4/blob/HEAD/coworker/skills/organize-task-files/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/organize-task-files, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Organize Task Files

Manages .full.md (evaluation outputs) and .issues.md (extracted issues) files across the Coworker task state machine pipelines.

When to Use

  • "organize task files"
  • "show me what tasks are in each pipeline stage"
  • "find unpaired .full.md and .issues.md files"
  • "find duplicate task files"
  • "find empty issues files (zero issues found)"
  • "move task files from X to Y"
  • "clean up the issues draft directory"

How It Works

  1. Scans coworker/tasks/ (issues, main) for .md task files
  2. Parses filenames with pattern YYYYMMDD-HHMMSS-taskname.{full,issues}.md or plain taskname.md
  3. Groups by task name, detects pairs/dupes/orphans, classifies by pipeline stage

Usage

Run the bundled script:

python3 coworker/skills/organize-task-files/scripts/organize.py COMMAND [OPTIONS]

Commands

CommandDescription
summaryOverview of all pipelines: file counts per stage, type breakdown
listList all task files with full paths, grouped by pipeline stage
pairsMatch .full.md ↔ .issues.md pairs; flag orphans
dupesFind duplicate task names across directories and stages
emptyFind .issues.md files with "0 issues found"
moveMove matching files between pipeline stages (dry-run by default)

Options

FlagDescription
--dir DIROnly scan a specific directory (default: all task dirs)
--dry-runShow what would happen without making changes (default for move)
--forceActually perform moves (use with move)
--jsonOutput as JSON for scripting

Examples

# Overview of all pipelines
python3 coworker/skills/organize-task-files/scripts/organize.py summary

# Find unpaired files in issues draft
python3 coworker/skills/organize-task-files/scripts/organize.py pairs --dir issues/draft

# List all duplicate task names
python3 coworker/skills/organize-task-files/scripts/organize.py dupes

# Find empty .issues.md files (zero issues)
python3 coworker/skills/organize-task-files/scripts/organize.py empty

# Preview moving empty issues files to a discard directory
python3 coworker/skills/organize-task-files/scripts/organize.py move --dir issues/draft --filter empty --target coworker/tasks/issues/review/done/discard

# Actually perform the move
python3 coworker/skills/organize-task-files/scripts/organize.py move --dir issues/draft --filter empty --target coworker/tasks/issues/review/done/discard --force

Pipeline Stages (for reference)

0draft → 1ready → 2working → 3done → 4review → 5approved → 6git-pushed

Plus parallel pipelines:

  • issues/draft/refine/ (0ready → 1working → 2done → 0error)
  • issues/github/commit/ (ready → done → failed)
  • issues/review/ and issues/review/done/
  • issues/local/done/ and issues/local/wontfix/