progress-log SKILL.md skillA
progress-log from swingerman/engineer is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add swingerman/engineer/progress-log@git:20260710.5dd248aPins git:20260710.5dd248a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- swingerman/engineer
- Path
engineer/skills/progress-log/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260710.5dd248a, committed Jul 10, 2026
- First version recorded
- May 25, 2026
- Size
- 5,806 bytes
- Repository stars
- 162
- License
- MIT
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".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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@sha256:6b899eb187bb9e3dThe line at the top of this page pins the label git:20260710.5dd248a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cofubd47vgrhiq2j)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 25, 2026 and Jul 10, 2026, about one every 11 days.
| 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 · 162 stars · license MIT · pushed 2026-10-27 · 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 AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.