القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Initialize a repository for Re:ZERO Loop. Use for `/rezero init` in Pi, `/rezero:run init` in Claude Code, or `$rezero:run init` in Codex: detect project type, set up witch evaluation tools, create memory ignore rules, and record unavailable tools.
Orchestrate the Re:ZERO Loop. Use for /rezero requests in Pi: split large work, let Subaru implement, call Seven Witches, send warnings to Rem, reset on fail, and commit on pass.
Run the Re:ZERO Loop. Use for `/rezero:run` in Claude Code or `$rezero:run` in Codex: initialize if needed, plan tasks, let Subaru implement, run Seven Witches review, remember warnings, reset on failures, and commit on pass.
Run the Seven Witches evaluation for a Re:ZERO attempt. Use after Subaru implements and verifies a task to get independent pass/warning/fail verdicts.
Subaru's single-task Re:ZERO implementation loop. Use inside rezero after task splitting: implement, verify, survive witches, reset on fail, commit on pass.
Manage Re:ZERO warning memory. Use when witch warnings pass, when processing .rezero/memory/rem.md, or when resolved warnings should be removed.
| name | rezero-plan |
| description | 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. |
| license | MIT |
Goal → convert a large request into task-sized Re:ZERO attempts.
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>