agentleFS
Sign inStart free
XORwellXORwell/archeflow/skills/progress/SKILL.md

progress

Skill0 starsChanged 52 days agoMITView on GitHub

Live progress file .archeflow/progress.md for ArcheFlow runs (status, budget, DAG), watchable from a second terminal.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quiz and teach.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • andrewn6Skill

    quiz

    Test understanding with targeted questions — adapts to skill level and researches the stack for relevant questions

    Also in 4 projects that use this

  • GoogleSkill

    teach

    Teach the user a new skill or concept, within this workspace.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Live Progress -- Real-Time Run Visibility

Maintains .archeflow/progress.md, updated after every event during a run.

Progress File Format

# ArcheFlow Run: 2026-04-03-add-auth
**Status:** DO phase -- maker running (3/6 scenes drafted)
**Started:** 14:32 | **Elapsed:** 8 min
**Budget:** $1.45 / $10.00 (14%)

## Progress
- [x] PLAN: Explorer (87s, 21k tok, $0.02)
- [x] PLAN: Creator (167s, 26k tok, $0.08)
- [x] PLAN -> DO transition
- [ ] **DO: Maker** <- running (5 min elapsed)
- [ ] CHECK: Guardian
- [ ] CHECK: Sage
- [ ] ACT: Apply fixes

## Latest Event
#6 agent.start -- maker (do) -- 14:40

Usage

The run skill calls archeflow-progress.sh after each event emission:

<archeflow-root>/lib/archeflow-progress.sh <run_id>

From a second terminal:

  • One-shot: cat .archeflow/progress.md
  • Continuous: <archeflow-root>/lib/archeflow-progress.sh <run_id> --watch
  • JSON output: <archeflow-root>/lib/archeflow-progress.sh <run_id> --json

How the Script Works

  1. Read .archeflow/events/<run_id>.jsonl
  2. Determine current phase and active agent
  3. Build checklist from events (only started/completed agents shown)
  4. Calculate budget from agent.complete cost data
  5. Write .archeflow/progress.md

Checklist Construction

Event TypeEntry
agent.complete- [x] PHASE: archetype (duration, tokens, cost)
agent.start (no complete)- [ ] **PHASE: archetype** <- running
phase.transition- [x] PHASE -> PHASE transition
cycle.boundary- [x] Cycle N complete

Pending (not-yet-started) agents are NOT shown to avoid guessing.

Budget Display

Source: run.start event or .archeflow/config.yaml. If no budget configured: show cost only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free