weekly-retro skillA
weekly-retro is agent-read markdown (skill) from serejaris/personal-corp-os: Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week..
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
# Weekly Retro Part of the Personal Corp framework — running a one-person business through AI agents. Structured weekly retrospective. Gather facts from code and project management tools, interview the founder, capture findings into issues and canonical files. ## Setup Before first use, define these in your project's `CLAUDE.md`: ```markdown ## Weekly Retro Config ### Repos to scan List all repos the agent should check for commits: - ~/Projects/main-app - ~/Projects/marketing-site - ~/Projects/docs ### GitHub owner Your GitHub username or org for issue search: - owner: your-github-handle ### GitHub Project ID Project board where retro issues land: - project_id: 7 ### Canonical files (single source of truth) Files that hold authoritative data — agent must check these before writing numbers: - data.md — prices, revenue, historical totals - product.md — current offers - insights.md — strategic conclusions ### Retro log path Where retro artifacts are saved. Two files per retro live here: - `WNN.md` — interview log + final summary - `WNN-outcomes.md` — outcomes scorecard (planned outcomes vs evidence) Example: - retro_log_path: docs/retro/ ### Task routing …
Read the whole file at its exact version.
How to install
mdr add serejaris/personal-corp-os/weekly-retro@git:20260818.4a8a8cfmdr add serejaris/personal-corp-os/weekly-retro@sha256:ade413fbedd313c4Pin 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_2hlisoutfmwj2ps3)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260818.4a8a8cf latest | 2026-08-18 | 4a8a8cf | 22,089 B | A | view · diff |
| git:20260511.17f1df3 | 2026-05-11 | 17f1df3 | 21,072 B | A | view · diff |
| git:20260325.cf09020 | 2026-03-25 | cf09020 | 9,668 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 (22089 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
serejaris/personal-corp-os · 228 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2hlisoutfmwj2ps3 GET https://markdownregistry.com/api/v1/resolve?ref=serejaris/personal-corp-os/weekly-retro GET https://markdownregistry.com/api/v1/blob/ade413fbedd313c43e954b4d280240b316468172247e54bca687103013490223
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.