Rezero plan
Split a large Re:ZERO request into small ordered tasks with clear done criteria. Use before implementation when the request spans multiple features, files, or risks.From its SKILL.md
npx -y skills add Epsilondelta-ai/rezero --skill rezero-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.0 KB, as published. Nobody here has run it
Re:ZERO Plan
Goal → convert a large request into task-sized Re:ZERO attempts.
Output
Return only:
## Re:ZERO Tasks
1. <task>
- Done: <observable criterion>
- Depends on: <task numbers or none>
- Parallel: <yes/no; safe with task numbers>
2. <task>
- Done: <observable criterion>
- Depends on: <task numbers or none>
- Parallel: <yes/no; safe with task numbers>
Rules
- Keep tasks small enough for one implement → verify → witches → commit loop.
- Preserve dependency order.
- Mark independent tasks that can run in parallel without file/state conflicts.
- Each task must have a clear done criterion.
- Do not implement.
- If the request is already small, return one task.
- Dangerous ambiguity → ask 1 focused question.