Individual skill

re0-plan

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.

skills/coil/re0-plan/SKILL.md

Read pinned source

Source commit 0b1e2c65231b3ce9294844362efae9b3a726e3ed

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,399
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Open `.re0/iteration/<version>-<workname>/` and write into it in the same motion, before a single line of `re0-loop`'s cycle runs.

## Goal

A cycle without a written thesis, gate list, and step plan drifts to whatever framing comes first — and a folder opened with nothing in it tells a resumed session nothing at all. `re0-plan` closes both gaps at once: the folder is never empty from the moment it's created, regardless of which weight the cycle turns out to be. It assumes the full paperthin package installed and names its sibling skills directly. It pairs with `re0-release`, which retires the folder, and `re0-memo`, which extends whatever this skill seeded instead of restarting fresh. It is not a portable planning method — the shape it writes is this repo's own convention.

## Workflow

1. Classify the cycle's weight: a fix or hardening pass with no real design surface is **lightweight**; a cycle with a direction genuinely worth arguing through is **full**.
2. Create `.re0/iteration/<version>-<workname>/` and, in the same step, write its first file — the weight decides which:
   - **lightweight** → `RETRO.local.md`: one paragraph naming the task and why it's lightweight. `re0-memo` extends this same file at the end; it never starts a fresh one. Stop here.
   - **full** → `DESIGN.local.md`: thesis, scope, and quality gates — the same content `re0-loop`'s FRAME turn expects, and enough on its own to survive a session break. When the change touches shippable surface, those gates always include an AGENTS.md/README reflection gate (see Rules). Confirm the read with `readchk`, size the tier with `modelchk`; reach for `macrothink` or another judgment skill only when the direction is genuinely contestable.
3. (full only) Write `WORKFLOW.local.md`: the numbered steps this specific cycle runs through `re0-loop`'s turn order — specific to this build, not a restatement of `re0-loop`'s generic stages.
4. (full only) Write `EVIDENCE.local.md`: the gates from `DESIGN.local.md`, listed as proof surface still to fill — the bar, not results.
Back to top