progress-log skillA
progress-log is agent-read markdown (skill) from swingerman/engineer: Use to propagate DAE state — turning handoff summaries into visible progress. Triggers — "/engineer.progress-log", "sync progress", "update the tracker", "reconcile the tracker", "refresh feature status"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# progress-log
The propagation engine of DAE visibility. Skills emit handoff summaries; `progress-log` turns them into the two visible state layers — `progress.md` (the per-feature glanceable file) and the external tracker.
When the foundations say "the agentic summary contract handles propagation," this skill *is* that propagation. `checkpoint: null`.
## When to use
- **Auto** — invoked after a handoff-emitting skill changes a DAE-managed field (status change, checkpoint completion). Scope = the triggering feature.
- **Manual** — `/engineer.progress-log <slug>` re-syncs one feature; `--project` reconciles all.
**Not for:** changing artifacts (`feature-edit`); validating consistency (`consistency-check`); a session wrap-up (`session-summary`).
## Workflow
1. **Resolve + scope** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); the manifest carries the tracker config. Scope = one feature (auto / `<slug>`) or all (`--project`).
2. **Read new handoffs** — `handoffs/*.md` not yet reflected in `progress.md` (compare timestamps against the last-synced marker).
…Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/progress-log@git:20260710.5dd248amdr add swingerman/engineer/progress-log@sha256:6b899eb187bb9e3dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_cofubd47vgrhiq2j)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260710.5dd248a latest | 2026-07-10 | 5dd248a | 5,806 B | A | view · diff |
| git:20260627.576fd6a | 2026-06-27 | 576fd6a | 5,321 B | A | view · diff |
| git:20260619.d0fa8c9 | 2026-06-19 | d0fa8c9 | 4,551 B | A | view · diff |
| git:20260604.c294fe7 | 2026-06-04 | c294fe7 | 4,319 B | A | view · diff |
| git:20260525.a1138fd | 2026-05-25 | a1138fd | 3,905 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5806 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
swingerman/engineer · 150 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_cofubd47vgrhiq2j GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/progress-log GET https://markdownregistry.com/api/v1/blob/6b899eb187bb9e3d523f66ded26d89041ca898793b7feee4ecd59f42b24ebd9e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.