propagate SKILL.md skillA
propagate from tercel/spec-forge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tercel/spec-forge/propagate@git:20260719.c80ca98Pins git:20260719.c80ca98 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tercel/spec-forge
- Path
skills/propagate/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260719.c80ca98, committed Jul 19, 2026
- First version recorded
- Apr 9, 2026
- Size
- 17,637 bytes
- Repository stars
- 10
- License
- MIT
Walk an upstream documentation change downstream — when a PRD, SRS, tech-design, or feature spec is edited, find every dependent document, identify which sections are now stale, and interactively update them to keep the entire doc chain consistent. Use after editing any spec-forge document, or run periodically with --since to catch accumulated drift.
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
# Spec Forge — Propagate
## ⚡ Execution Entry Point (READ THIS FIRST)
**Begin executing Step 1 immediately; never fall back to a manual workflow or stop to ask what to do.**
---
Walk a doc change downstream and keep the whole chain consistent.
## Iron Law
**EVERY UPSTREAM CHANGE PROPAGATES OR FAILS LOUDLY. Partial propagation is worse than no propagation — it creates the illusion of consistency where there is none.**
## When to Use
- After editing a PRD / SRS / tech-design / feature-spec — find and update every doc that references the changed concepts
- After running `/spec-forge:prd` or another generator that modified an existing doc in place
- Periodically, with `--since {git-ref}`, to catch accumulated drift across recent commits
- Before a release, to make sure no doc is silently stale relative to its upstream
- When `spec-forge:analyze` or `spec-forge:audit` flags inconsistencies between upstream and downstream docs
…Read the whole file at its exact version.
How to install
mdr add tercel/spec-forge/propagate@sha256:344ffd56de8723abThe line at the top of this page pins the label git:20260719.c80ca98, 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_mkettm26h4sw2qzb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 9, 2026 and Jul 19, 2026, about one every 101 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260719.c80ca98 latest | 2026-07-19 | c80ca98 | 17,637 B | A | view · diff |
| git:20260409.440560b | 2026-04-09 | 440560b | 18,222 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 (17637 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
tercel/spec-forge · 10 stars · license MIT · pushed 2026-09-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mkettm26h4sw2qzb GET https://markdownregistry.com/api/v1/resolve?ref=tercel/spec-forge/propagate GET https://markdownregistry.com/api/v1/blob/344ffd56de8723abf295f0ba0797d488ba1135c2ae0672065d2a8df92439dfaf
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.