update-spec SKILL.md skillA
update-spec from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atman-33/workhub/update-spec@git:20260720.f88c2b0Pins git:20260720.f88c2b0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atman-33/workhub
- Path
plugins/team-ops/skills/update-spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260720.f88c2b0, committed Jul 20, 2026
- Size
- 2,127 bytes
- Repository stars
- 3
- License
- MIT
Update the project's living spec (docs/spec/spec.md) from PBI acceptance criteria and diffs newly merged into the dev-main branches. Use in the daily routine after repo sync, or when the user asks to bring the spec up to date with what is implemented.
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
# Update the living spec
`docs/spec/spec.md` answers "what is implemented today, by feature area" —
kept truthful by folding in what actually merged, not what was planned.
## Steps
1. **Check there is anything to do**: compare each repo's
`repo-state.json.lastSyncAt` / new `commits.jsonl` entries against the
spec's last-updated marker (an HTML comment at the top of `spec.md`,
e.g. `<!-- last-updated: 2026-07-20 / app@abc1234 api@def5678 -->`).
**No new merges since the marker → stop and report "no change"** — this
is what keeps the daily routine cheap.
2. **Gather what merged**: new commits per repo grouped by PBI id
(`pbi-activity.json` + `commits.jsonl`), and for each involved PBI its
`## Acceptance Criteria` (satisfied AC = implemented behavior). Inspect
actual diffs in the script-owned mirror
(`git -C <mirrorPath> show <sha>`) only where the commit subject + AC
leave the behavior unclear.
3. **Fold into `spec.md`** (team content language):
- Organized by **feature area** (grow headings as the product grows),
not by sprint or PBI — a newcomer reads it as "how the product works".
…Read the whole file at its exact version.
How to install
mdr add atman-33/workhub/update-spec@sha256:c3769ed33618014cThe line at the top of this page pins the label git:20260720.f88c2b0, 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_wmvpyfp4swrt5noj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 20, 2026.
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 (2127 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
atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wmvpyfp4swrt5noj GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/update-spec GET https://markdownregistry.com/api/v1/blob/c3769ed33618014cf32b4b37433f05c469dc548ed23c065cc2644964ef46dae7
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.