weekly-planning skillA
weekly-planning is agent-read markdown (skill) from serejaris/personal-corp-os: Use when the user is transitioning from a completed retro into a weekly plan, choosing weekly outcomes, scheduling a full ISO week, or asking for "план на неделю", "weekly planning", priorities, capacity, or outcomes..
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 Planning
## Overview
Turn retro findings + existing backlog into a prioritized week with clear outcomes, issues in correct repos, and delegation matrix (founder vs agent).
## When to Use
- After weekly retro is complete
- Monday/Tuesday when planning the week
- When user says "план на неделю", "приоритизация", "что делаем"
## Iron Rule: Planning Is Not Execution
Weekly planning creates a plan. It does not execute the plan.
Allowed during planning:
- Gather context needed to choose outcomes
- Read calendars, issues, project boards, CRM/backlog files, and recent notes
- Draft outcomes, issue proposals, and board updates
Not allowed during planning:
- Start implementation work for a chosen outcome
- Create deliverables, briefs, proposals, content, code, or production changes
- Spawn executor agents for work that belongs to the coming week
If the user asks to "do this now" while planning, finish or pause planning first, then handle that as a separate execution task.
## Process
```dot
digraph planning {
rankdir=TB;
node [shape=box];
collect [label="1. Collect all tasks"];
calendar [label="2. Map calendar"];
group [label="3. Group by surface"];
…Read the whole file at its exact version.
How to install
mdr add serejaris/personal-corp-os/weekly-planning@git:20260818.4a8a8cfmdr add serejaris/personal-corp-os/weekly-planning@sha256:6ce8600a55651f3fPin 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_v7zhq4a6oz6xqrbs)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260818.4a8a8cf latest | 2026-08-18 | 4a8a8cf | 9,585 B | A | view · diff |
| git:20260806.9565cf9 | 2026-08-06 | 9565cf9 | 7,613 B | A | view · diff |
| git:20260525.485a46c | 2026-05-25 | 485a46c | 7,586 B | A | view · diff |
| git:20260325.cf09020 | 2026-03-25 | cf09020 | 6,068 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 (9585 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_v7zhq4a6oz6xqrbs GET https://markdownregistry.com/api/v1/resolve?ref=serejaris/personal-corp-os/weekly-planning GET https://markdownregistry.com/api/v1/blob/6ce8600a55651f3ffffa4a330cee622f0504a0a2e32f830d7c61bc13360c6cfd
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.