agentleFS
ES-92ES-92/esc/skills/track/SKILL.md

track

Skill0 starsChanged 4 months agoMITView on GitHub

Aktualisiert den mitlaufenden Projekt-Tracker esc/docs/TRACKER.md von ESC aus dem aktuellen Zustand — Pipeline-Fortschritt (Mermaid), Artefakt-/Gate-Status, Story-Board und Decision-Log. Use when the user says "tracker aktualisieren", "fortschritt", "esc track", or wird am Ende jeder Phase automatisch von den anderen Skills aufgerufen.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use apply and research.

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.
  • proficientlyjobsSkill

    apply

    Fill out a job application on Greenhouse, Lever, or Workday

    Also in 4 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Files
SKILL.md

esc:track — Projekt-Tracker aktualisieren

Ziel: esc/docs/TRACKER.md mit dem aktuellen Stand aus esc/state.yaml neu erzeugen. Schnell, idempotent.

Lies zuerst

  • ${CLAUDE_PLUGIN_ROOT}/shared/tracking.md — Format & Mermaid-Vorlage für TRACKER.md
  • esc/state.yaml

Ablauf

1. State prüfen

Existiert esc/state.yaml nicht, auf esc:init verweisen und stoppen.

2. Rendern — zwei Wege

  1. Bevorzugt (deterministisch): Versuche das Skript:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/render_tracker.py esc

Meldet es Erfolg („TRACKER.md geschrieben"), bist du fertig mit dem Rendern. 2. Fallback (manuell): Meldet das Skript, dass es übersprungen hat (kein Python/nicht parsebar), oder ist es nicht vorhanden, dann erzeuge esc/docs/TRACKER.md selbst exakt nach der Vorlage in shared/tracking.md:

  • Pipeline-Flowchart: jeden Knoten nach artifacts-Status stylen (done/active/pending), für das Level nicht vorgesehene Phasen als :::skipped.
  • Artefakt-, Gate-, Story-Tabellen + Story-Pie aus state.yaml.
  • Decision-Log aus dem decisions-Array; Risiken/offene Fragen aus den Artefakten.

3. Kurz bestätigen

Eine Zeile: was sich seit dem letzten Stand geändert hat (z. B. „PRD abgeschlossen, Phase → ux").

Definition of Done

  • esc/docs/TRACKER.md spiegelt state.yaml korrekt (Phase, Artefakte, Gates, Stories, Decisions).
  • Mermaid-Pipeline rendert (gültige Syntax, Knoten korrekt gestylt).

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.