critical-journey-document SKILL.md skillA
critical-journey-document from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/critical-journey-document@git:20261017.2f2e03bPins git:20261017.2f2e03b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/critical-journey-document/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Jul 18, 2026
- Size
- 2,335 bytes
- Repository stars
- 3
- License
- MIT
Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate; not for implemented-system context under docs/context/, which belongs to repo-context-document.
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
# Critical Journey Documentation Create one canonical record of how one actor reaches one goal, and show which steps the product implements today. ## Workflow 1. Establish what makes the journey critical, and its actor, goal, trigger, scope, owner, and risk. Find the repository's established location for product documentation. If there is none, ask the user where the record goes; do not create a new documentation tree. 2. Read the existing requirements, code, contracts, tests, telemetry, and documentation. Reuse the repository's identifiers and terms. 3. Write separate records for several actors or goals only when each record is useful alone. 4. Document the ordered steps, decisions, state changes, success, meaningful failures, recovery, and ownership. Mark each step as implemented, with a link to the code or test that shows it; specified only, with a link to the requirement; or unknown. 5. Record each unresolved fact as an unknown, with its decision owner and the condition that resolves it. Do not fill it with a guess. …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/critical-journey-document@sha256:dcc5cf8f22b84ec8The line at the top of this page pins the label git:20261017.2f2e03b, 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_2bmglncgnllxmyx5)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 18, 2026 and Oct 17, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.2f2e03b latest | 2026-10-17 | 2f2e03b | 2,335 B | A | view · diff |
| git:20260828.116b669 | 2026-08-28 | 116b669 | 1,866 B | A | view · diff |
| git:20260718.d92e66e | 2026-07-18 | d92e66e | 1,901 B | A | view · diff |
| git:20260718.206351f | 2026-07-18 | 206351f | 1,755 B | A | view · diff |
| git:20260718.7cc9d66 | 2026-07-18 | 7cc9d66 | 2,561 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 (2335 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2bmglncgnllxmyx5 GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/critical-journey-document GET https://markdownregistry.com/api/v1/blob/dcc5cf8f22b84ec820aa19d0346c646f1b082fccba749265978c1f2762ed4d0b
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.