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.
How do I install this agent skill?
npx skills add https://github.com/lilmgenius/paperthin --skill re0-planIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill establishes a structured planning and documentation workflow for development cycles by creating and populating local markdown files. It lacks external network access, sensitive credential usage, or remote code execution. A low-severity finding is noted regarding the attack surface for indirect prompt injection common to tools that process repository-controlled content.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Open .re0/iteration/active/<version>-<workname>/ and write into it in the same motion, before a single line of re0-loop's cycle runs.
Goal
A written thesis, gate list, and step plan keep a cycle from drifting toward its first framing. A seeded folder lets a resumed session recover that context. re0-plan writes real content at creation for either cycle weight. It assumes the full paperthin package installed and names sibling skills directly: re0-release retires the folder, and re0-memo extends its seed instead of starting fresh. This repository's casebook convention is not a portable planning method.
Workflow
- Classify the cycle's weight: a fix or hardening pass with no real design surface is lightweight; a cycle whose direction warrants debate is full.
- Create
.re0/iteration/active/<version>-<workname>/, or.re0/iteration/planned/<version>-<workname>/when the cycle is queued for a later session, and write its first file in the same step, according to weight:- lightweight →
RETRO.local.md: one paragraph naming the task and why it's lightweight.re0-memoextends this same file at the end; it never starts a fresh one. Stop here. - full →
DESIGN.local.md: thesis, scope, and quality gates matchingre0-loop's FRAME turn, sufficient to resume after a session break. Changes to shippable surface always require an AGENTS.md/README reflection gate (see Rules). Call the Skill tool with "readback" to confirm the read. Only for a contestable direction, tell the user to run/macrothinkor another judgment skill.
- lightweight →
- (full only) Write
WORKFLOW.local.md: numbered steps specific to this build, followingre0-loop's turn order without restating its generic stages. - (full only) Write
EVIDENCE.local.md: gates fromDESIGN.local.md, stating the proof still required, not results. - Add the cycle's entry to the repository root's
TODO.local.md, linking the folder's path. - Keep reference material flat as
REF-<topic>.local.md; promote to arefs/subfolder only once it multiplies past a couple of files. - For an
active/cycle, hand off by calling the Skill tool with "re0-loop"; aplanned/cycle stops here. Do not call it withre0-workhere: a from-scratch restart isre0-loop's mid-cycle call, surfaced bynbawhen warranted, never a setup step.
Rules
- The folder is never empty at creation. Both paths write real content as the folder is created, leaving resumable context at any session break.
- Not portable, by design. This skill names paperthin siblings directly and assumes the full package installed, where the others degrade when a sibling is missing. It exists only to pair with
re0-releaseandre0-memo, not to travel alone. - No padding. Lightweight gets no
DESIGN/WORKFLOW/EVIDENCE. ItsRETRO.local.mdseed is a one-paragraph task note, never a disguisedWORKFLOW.local.md. Never force in a judgment skill orre0-workas a precaution. - The folder's
<version>is provisional. Usere0-release's discriminator, kind rather than size: against the artifact's own prior spec, a fix is patch; a new capability a user newly reaches for is minor. Keep the bump contingent on unresolved forks. Never commit to an unearned bump; a fork that could add a skill leaves it undecided until resolved. - Docs stay aligned, like
re0-releaseat ship time. Changes to shippable surface always require an AGENTS.md/README reflection gate: each change lands in the doc whose reader needs it, andre0-readme's audit is the check. This planning gate complementsre0-release's ship-time README step. - negatives-as-corpus: never delete anything this skill or its cycle produces;
re0-releaseretires a cycle that goes wrong rather than discarding it. - Every
EVIDENCE.local.mdgate traces back to a line inDESIGN.local.md; don't invent proof surfaceDESIGNnever asked for.
Verification
Before finishing:
- The folder has real content from creation on either path.
- Full path:
DESIGN.local.mdstates a thesis, scope, and gates;WORKFLOW.local.md's steps are specific to this cycle; everyEVIDENCE.local.mdgate traces toDESIGN.local.md. - Lightweight path:
RETRO.local.mdis seeded with the task and reason, one paragraph. - Reference material stayed flat unless it earned a
refs/subfolder. - Report which path was taken and why.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/lilmgenius/paperthin/re0-plan">View re0-plan on skillZs</a>