re0-workflow
Installation
SKILL.md
Turn one stated intent into an ordered skill graph, show it, and run the steps the session may run.
Goal
Someone who does not know this suite's catalog should be able to say what they want and see every part of it done, with nothing misread or dropped. Read the intent into numbered requirements, select and order the installed skills that serve them, check the plan with the bundled script, show the whole plan before anything runs, run each step the session holds authority for, and stop at the first step that needs the human, with a report of what ran and of every requirement.
Workflow
- Read the human's stated intent and the installed roster from the host catalog or skill directories. If given only live state without a stated intent, ask for the intent rather than infer it. Read each candidate's contract and invocation lane, and
readback's own SKILL.md when it is installed, for the method step 2 applies, and nothing a planned step will read (a draft, a file it edits, data it fetches), since opening that is running the step before approval.disable-model-invocation: truein its SKILL.md, orpolicy.allow_implicit_invocation: falsein itsagents/openai.yaml, means user-only; otherwise it is model-invoked, and when the two disagree it is user-only. - Re-read every request before choosing anything, applying
readback's method yourself, never invoking it: restate the request in your own words, check the restatement against the request and the contracts step 1 read, and ask one specific question only when two readings survive that they cannot settle. Decompose the confirmed read into numbered requirements (r1,r2, ...), one per thing the human asked for, in their order, and one line beginningunderstood as:. The read is the first section of the reply that shows the plan, written in that same message, and it is no step, no action and no tool call; a request for the order alone, a cycle and a no-match open with it too. Skip the restatement only when the intent names one installed skill and its one target and asks nothing else (single-named-step), still writing the requirement and the line. Without readback installed, restate the request the same way and say the read went unchecked. - For each requirement, select the installed skills whose triggers and outputs serve it; add no step the requirements do not need and no orientation skill, and when one skill suffices, use one node and say ordering is trivial. A named skill that is not installed stays as a
skipstep, shown as unavailable. Work no skill covers becomes a step of its own, typed by the table in step 6, only inside a plan that has at least one skill step; a requirement nothing installed serves and no one present could authorize is unmet, with the reason. When no installed skill serves any requirement, the request is a no-match, even if the session could do the work itself: there is no plan and no tool call after the contract reads, and the reply gives the read of step 2, then says plainly that the goal was not done and why. - Close each stretch of the run that writes a file or record with one
sipstep, the suite's taste test for new output, run as one node and never reproduced member by member. Stretches split at each step whose expected type, its first, isuser-handoff; the human's write in that handoff belongs to the stretch after it. When a conditional step resolves to another type, the plan is re-planned and shown again (step 6), so its stretches are drawn anew. A stretch'ssipis its last step and follows every write in it. A stretch that writes nothing gets none, and a pipeline that runssipitself closes its own writes. The closingsipis itself a write, since its cleanup pass edits the changed docs: the approval covers it and nosipfollows it. Show it with the checks its own contract runs listed under its node as its members, each with the condition its contract gives, so no call it makes is unshown. It reports findings and proposes fixes, and any fix or consolidation plan it proposes is a new step shown and approved before it runs. A judgment the run delivers (a verdict or a choice with no file) is tasted by asipthat comes after it in the same stretch; when none does, add one outside read after it:showerfor whether it reads clearly to someone with no context,factchkfor claims about the world, ormandelafor an eval, metric or experiment. An added check serves the requirements of the steps it checks, is shown with its reason, and is no action. When its skill is not installed it stays as askip, and the report says the output it would have checked went untasted. - Order the steps by their contracts' prerequisites: a step depends on another when its firing precondition needs that step's output. List them in run order, and where the prerequisites leave the order free, put the session's steps before a handoff, so the run reaches the human once and as late as it can. Every prerequisite a contract states is an edge, and none is dropped to make the order runnable. Find cycles from those requires-edges before showing anything. A cycle makes the whole result a
reject: the reply gives the read of step 2, then names the cycle along its requires-edges, each step followed by one whose output it needs (skill-a requires skill-b requires skill-a), with no steps, nothing run and no check. Otherwise give the graph one observable stop condition that shows the goal met rather than a step merely returning (a ready verdict, not a report that finds problems), reached after its last step, meaning every requirement was served or no longer applies. - Give every step an identifier, a target (the skill that acts, the work when no skill covers it, or the question for a human decision), its predecessors, the requirements it serves, one type, a firing precondition, its expected output (for a skill, what its own contract promises), a skippable condition, a cost owner, its target's lane, and whether it writes. A step writes when it creates or changes a file or record. Version control that only moves or records content (a commit or its message, a history rewrite, a push, a tag, a publish) is no write for
sip, but a run step that commits or rewrites history is marked"vcs": trueand needs the same approval as a write. Count a contract silent on writing as writing and an unreadable lane as user-only. A frozen pipeline, a skill whose own contract runs a fixed sequence of other skills, is one node whose members are the skills it runs itself; a skill it only hands to the human is no member, and the pipeline writes when a member writes. Type each step by the first row below that applies. A step whose type depends on an earlier result lists the types it can take, the expected one first, with the condition that decides; once that result exists the step is typed, and a type other than the expected one re-plans the rest, which is checked and shown again before it runs.