Menu

Individual skill

jevflow

0upvotes

How to work inside a Jevflow-tracked session. Use when a Jevflow context block or a "[jevflow]" Stop instruction appears, when the user asks to keep a long task on track toward a goal, or when they mention flow.json, phases, or the Jevflow supervisor.

plugin/skills/jevflow/SKILL.md

Read pinned source

Source commit ef6563f6d425de36984f87478c5b6c9ff41cd487

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
12
Repository last updated
Oct 25, 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

# Working with Jevflow

Jevflow tracks a session against a flow in `.jevflow/flow.json`: a goal and ordered phases, each with a `done_when` sentence and often a shell `check`. When you try to stop, a Stop hook runs the checks, asks Jev (a calibrated judgment model) where the work is, and a fixed policy decides whether you may stop.

## When a `[jevflow]` instruction blocks your stop

- Treat it as the next instruction. Do the concrete thing it names for the named phase.
- If it quotes failing check output, fix the cause shown there. Run the check command yourself before claiming the phase is done.
- "You said the work is done, but it is not" means a check still fails. Do not repeat the claim; make the check pass.
- "You are looping" means your last approach is not working. Re-read the goal and change approach, not just parameters.
- "Regression" means a phase that was done now fails its check. Fix that first.
- Never edit `.jevflow/state.json` or `.jevflow/flow.json` to get past a block. Only Jevflow code writes state. Changing the flow is a user decision.

## Starting and checking