instructions

Instructions: custom instruction management

Contents

• Loop invariants
• Anti-rationalization
• Definition of done
• Budgets — quality-first
• ACI per-phase tool surface
• Memory I/O
• Termination case → state mapping
• Valid scope set
• File shapes
• Frontmatter field reference (review-extra/<slug>.md)
• Phase 1 — parse intent, resolve scope, dispatch to a mode
• Writing effective instructions
• Cross-references

Stateless loop: Parse → Execute → Done — every invocation is a single transaction with no state file. CRUD frontend over .geniro/instructions/ — the L4 procedural memory layer. Five modes: list, create, edit, validate, delete; Phase 1 resolves exactly one of them per invocation.

Phase body. Phase 1's Steps live in ${CLAUDE_PLUGIN_ROOT}/skills/instructions/phase-1-parse.md. Read it on entry to the phase, and again on any resumption of it, including after a compaction. That Read is the phase's physically-first action and carries a one-line echo, per ${CLAUDE_PLUGIN_ROOT}/skills/_shared/phase-entry-read.md — the phase file holds this skill's gates and its helper call sites, so work started before the Read runs outside them. A create/edit run also reads ${CLAUDE_PLUGIN_ROOT}/skills/instructions/phase-1-block-type-reference.md from there.

Mode bodies. Each mode's Steps live in ${CLAUDE_PLUGIN_ROOT}/skills/instructions/mode-<op>.md. Read the one Phase 1 dispatches to, and again on any resumption of it — the four it did not dispatch to are never read. That Read comes before any step of the mode and carries a one-line echo, per ${CLAUDE_PLUGIN_ROOT}/skills/_shared/phase-entry-read.md — the dispatched body is this run's phase body, and it holds every pause this skill declares today, not a cap on future ones. delete is where that matters most: mode-delete.md is the sole home of the destructive-op confirmation, and the .geniro/ deletion guard hook permits a per-file rm -f on .geniro/instructions/<scope>.md, so nothing else stops it.