Carry out a task from work/tasks/ — the implementer agent writes the change, the reviewer agent checks it, findings go back for fixing; the user gets the summary and commits.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Carry out task $0. You orchestrate; the work is done by two subagents, each in a clean context: implementer and reviewer (.claude/agents/). Talk to the user in Russian.
work/tasks/$0-*.md. None, or its status in work/backlog.md is not todo / in progress — stop and tell the user.git status --short: uncommitted changes that are not this task's are the user's — mention them; the agents must not touch them.work/backlog.md to in progress.Start the implementer agent. Its prompt: the task file's path, and nothing else — the rest it reads itself. Wait for it to finish.
When it returns a question instead of a result: ask the user (with the options it gave), then send the answer to the same agent with SendMessage, so it keeps its context. If resuming fails, write the answer into the task file (a «Решения по ходу» section) and start a new implementer.
When the implementer is done, start the reviewer agent with the task file's path.
[исправить] → send them to the same implementer with SendMessage; when it is done, send "second round" to the same reviewer. At most two rounds. What remains after that goes to the user.[решить] and the implementer's "not agreed" answers do not go back: they go to the user.rm -rf work/runs/$0, run from the repository root, once both agents are finished. Nothing else in work/ is deleted.
In Russian, short:
git log; no Co-Authored-By line.Details are in the task file («Результат», «Ревью»). Do not commit — the user commits.
When the user says the task is committed: delete the task file and its line in work/backlog.md; a decision worth remembering goes into work/decisions.md (what, why, the date).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Prepare a release of HoverTranslate — version, changelog, checks, live YouTube markup, store archives, and what the user uploads where. Uploads nothing itself.
The English summary is being prepared. Showing the original description.
Research an idea for HoverTranslate and write it up as a task file in work/tasks/ for the implementer agent. Changes no code. An agent invokes it only after the user agreed to that very task in this conversation — propose it and ask first, never on its own judgement.
The English summary is being prepared. Showing the original description.