tasks
Skill1 starsChanged 42 days agoMITView on GitHub
Use when the user asks about pipeline tasks — listing open tasks, searching past tasks or bugfixes, reviewing a plan before execution, checking what was delivered in a task, or registering a task retroactively (hotfix done outside the pipeline).
52 other projects use a version of this.
Adopted by
Most recently taken up by
- ArchAstro/archdevtheir own version, first seen Nov 16, 2026
- maribol/overvibetheir own version, first seen Nov 15, 2026
- felipefontoura/claude-sdd-kittheir own version, first seen Nov 15, 2026
- br3eze-code/br3eze-codetheir own version, first seen Nov 11, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- tandregbg/core-claude-skillstheir own version, first seen Nov 4, 2026
Used with
Projects with it also use send-user-message, tinyagi-admin and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Maliot100XSkillsend-user-message
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.
Also in 4 projects that use this
jlia0Skilltinyagi-admin
Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.
Also in 3 projects that use this
ArvorCoSkillconstitution
Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.
Also in 4 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 6 projects that use this
anyprotoSkillskills-manager
Context-aware routing to skills and hooks management. Use when troubleshooting skill activation, fine-tuning keywords, or managing the automated documentation system.
Also in 3 projects that use this
GoogleSkillquality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
Also in 3 projects that use this
- +1 more from ArvorCo
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- jlia0/tinyclaw★ 3.6ksame name
- TinyAGI/tinyagi★ 3.6ksame name
- TinyAGI/tinyclaw★ 3.6ksame name
- me2resh/apexyard★ 542same name
- snarktank/compound-product★ 542same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- ansvisor/ansvisor★ 241same name
- genkovich/sdd★ 187same name
- mp-web3/claude-starter-kit★ 108same name
- ArvorCo/Relentless★ 98same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- init-profileSkill
- pipelineSkill
The file
Files
Task Registry
Local-first registry: fast to search, human-readable plans, no digging through git log. Lives in .claude/pipeline/ of the project. All commands run through the CLI: node <plugin-root>/scripts/task-cli.js <command> — the plugin root is announced at session start by the plugin's SessionStart hook. The CLI finds the project root from any subdirectory.
Commands
| Command | Purpose |
new "<title>" --type=improvement|bugfix --level=N | Create task + plan file, prints TASK-<id> and plan path |
list [--status=planned|in-progress|ready|done] [--type=bypass|...] | Table of tasks |
search "<term>" | Case-insensitive search across titles and plan file contents |
show <id> | Full record: status, level, commit, attempts, plan path |
start <id> | Mark in progress (one active task at a time); records the base commit for the complexity ratchet |
tdd-red <id> [--area=a,b] [--cmd="..."] | Runs the area's tests and records red only if they fail — unblocks the TDD guard for that area |
tdd-skip <id> --reason="..." [--area=a,b] | Justify the absence of tests (all areas by default) — recorded |
ready <id> [--partial --reason="..."] | Refuses while the plan has unticked items; cleared to commit — unblocks the commit gate |
done <id> --commit=<hash> | Close task (the post-commit hook usually does this) |
note <id> "<text>" | Append a timestamped note (decisions, context) |
rework <id> --area=X --reason="..." | Record a review rejection / rework attempt (telemetry + attempt limit) |
usage <id> --collect [--dir=...] | Collect token usage from the session transcripts in the task's time window (the post-commit hook does this automatically) |
usage <id> --json='[{"model":"sonnet","input":N,"output":N}]' | Attach token usage manually (e.g. work done in another machine's sessions) |
bypass --commit=<hash> "<subject>" | Register a commit that skipped the gate (the post-commit hook does this automatically) |
report [--since=YYYY-MM-DD] | Per-task wall time / attempts / est. cost + aggregation per model matrix (the A/B cost-comparison view); bypassed commits listed apart |
debt | Lean debt ledger: lean: / ponytail: comment markers in code (with the task that wrote them, via git blame) and every plan's "Out of scope" items; flags entries with no trigger to revisit |
index | Regenerate INDEX.md (auto-run by mutating commands) |
Layout
tasks.json— the structured registry (ids, status, level, commit hash, attempts, timestamps).plans/TASK-<id>.md— the human file: discovery Q&A, mini-tasks, contract, decisions. This is what the user reads to evaluate a plan before authorizing execution.INDEX.md— generated view, newest first. Never edit by hand.
Retroactive registration
A commit that skipped the gate (PIPELINE_SKIP_GATE=1) is registered automatically by the post-commit hook as a bypass task with its commit hash — fill in its plan file (what changed, why the gate was skipped) as soon as noticed. Work committed entirely outside Claude Code (no hook ran) is registered by hand: new with --type=bugfix, then done --commit=<hash>.
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
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.

