long-task
Skill0 starsChanged 45 days agoMITView on GitHub
Loop for work over one sitting or ~7 steps: checked plan, riskiest first, one-line state tracker, iteration budget, stop after the same failure twice. Use when: "long-task", "plan this out", "this is a big one". Small work: small-task.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- mike22890/opencode-skills-entheir own version, first seen Oct 15, 2026
- mike22890/opencode-skills-cntheir own version, first seen Sep 13, 2026
- genomewalker/chittatheir own version, first seen Jan 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- genomewalker/chitta★ 4same name
- mike22890/opencode-skills-cn★ 1same name
- mike22890/opencode-skills-en★ 1same name
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 repository34 other files it gives its agents.
- audit-codeSkill
- audit-docsSkill
- auditSkill
- bisect-driverSkill
- coding-conventionsSkill
- commit-gateSkill
- compact-ioSkill
- cron-task-manageSkill
- cve-auditSkill
- data-integrity-auditSkill
- decision-logSkill
- deck-builderSkill
- determinism-guardSkill
- etl-validateSkill
- experiment-logSkill
- fetch-firstSkill
- flaky-test-detectorSkill
- github-repo-polishSkill
- golden-lockSkill
- history-leak-scanSkill
- landing-checkSkill
- llm-eval-harnessSkill
- local-secrets-manageSkill
- milestone-trackSkill
- opus-workersSkill
- path-quirk-auditSkill
- reorg-proposalSkill
- research-briefSkill
- seed-controlSkill
- shell-portabilitySkill
- skill-vetSkill
- small-taskSkill
- token-squeezeSkill
- venue-fitSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 53
Before declaring the goal done: every step's verify ran and its real output is in the transcript.
≈ “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.
Files
long-task
1. Plan before the first edit
Numbered steps, each one a verifiable unit:
N. <step> → verify: <command or observation that proves it>Riskiest or most uncertain step first — it is the one most likely to change the plan, so learn that before spending on the rest. Set a BUDGET: max tool turns per step (default 25; the user's cap if they gave one). Say the plan before executing it; a plan nobody can read is not a plan.
2. State tracker — first line of every turn while the task is open
[LONG-TASK] step k/N · done: <verified steps> · blocked: <error, or none> · next: <the single step this turn>One line. It exists for the reader at high context, when the plan written 80k tokens ago is no longer in view — the same reason small-task and compact-io are injected per prompt.
3. The loop
Analyze the last result → pick the single next step → execute → verify with real output. Advance only on a passed check. A step that will not pass inside its budget is a finding, not a retry: report it and re-plan.
4. Progress lock
The same command producing the same failure twice in a row means you are
spinning. hooks/no-progress.js injects [NO-PROGRESS] when it sees exactly
that. On it: change the approach — a different command, a different
diagnosis, read the code instead of re-running it — or stop and report a
NO-PROGRESS BLOCK naming the command and the error. Never a third
identical attempt.
5. Done
Before declaring the goal done: every step's verify ran and its real output is in the transcript; the project's own definition of done applies on top. An unmet check means the loop continues with a corrective step, or the shortfall is reported as unmet — never rounded up to done.
Hand-offs
Delegating steps to a cheaper tier → opus-workers. Launch-blocking risks before shipping → pre-mortem. Recording the run → the project's record.
Config
- Off for a session:
NO_PROGRESS_OFF=1. - The repeat threshold and error normalisation live at the top of
hooks/no-progress.js.
node hooks/no-progress.js --canary — MUST print CANARY PASS 14/14 before you trust a result.
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.