New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Weekly Planning

by serejaris in serejaris/personal-corp-os

A skill your agent uses 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…

MITAuto-check passedAgent Workflows

Install Weekly Planning

skills CLI
$ npx skills add serejaris/personal-corp-os --skill weekly-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install serejaris/personal-corp-os weekly-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/weekly-planning .claude/skills/weekly-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
weekly-planning
GitHub stars
229
Token cost
~2.4k tokens
SKILL.md length
983 words
Files
6 (incl. scripts, assets)
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 8 steps: Collect all tasks → Map calendar → Group by surface → …
  • The user is transitioning from a completed retro into a weekly plan
  • SKILL.md covers Overview, When to Use, Iron Rule: Planning Is Not… and Process, plus 5 more sections
  • Runs Python scripts from its folder; calls gh and python3

What it does

Weekly Planning is an agent 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.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and assets (for example `README.md`, `README.ru.md` and `scripts/living_week.py`).

It sits in Agent Workflows. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.

When your agent uses it

  • The user is transitioning from a completed retro into a weekly plan
  • Choosing weekly outcomes
  • Scheduling a full ISO week
  • Asking for план на неделю

Example prompts

  • “weekly planning”
  • “/weekly-planning”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Collect all tasks
  2. Map calendar
  3. Group by surface
  4. Eisenhower split with delegation
  5. Choose outcomes
  6. Create issues in CORRECT repos
  7. Add to unified board
  8. Create the living weekly plan

What it can do on your machine

Read from SKILL.md and the folder at commit 95e36c3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Weekly Planning loads about 2.4k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 983 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 983 words, ~2,376 tokens.

Download SKILL.mdSave it as .claude/skills/weekly-planning/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
weekly-planning
description
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.

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"];
  eisenhower [label="4. Eisenhower split"];
  outcomes [label="5. Choose outcomes"];
  issues [label="6. Create issues\nin correct repos"];
  board [label="7. Add to board\nwith W{NN} label"];
  page [label="8. Create living\nweekly plan"];

  collect -> calendar -> group -> eisenhower -> outcomes -> issues -> board -> page;
}
1. Collect all tasks

Sources to scan:

  • Retro backlog (label retro:W{NN-1})
  • Open issues across ALL repos: gh search issues --owner $YOUR_OWNER --state open
  • GitHub Projects for active initiatives
  • Calendar events (meetings, lectures, mentoring)
  • User input (new tasks from interview)
2. Map calendar

Read known sources before asking the user. Use calendar, existing issues, project boards, and planning files to establish:

  • Today's date
  • Planned week start/end
  • Fixed events
  • Known deadlines
  • Available capacity

Ask only for facts that are not recoverable from sources, one question at a time.

IMPORTANT: Verify dates before writing outcomes. Do not create deadlines in the past. If the deadline is today, include a time boundary such as "by EOD".

3. Group by surface

Group tasks by where work happens. Use the repos and task routing defined in AGENTS.md / CLAUDE.md config (set up by corp-init).

Example surfaces:

SurfaceDescription
Product deliveryMain product/service repos
Sales/pipelineCRM, sales tooling
ContentBlog, videos, social media
StrategyPlanning, cross-cutting decisions
InfrastructureInternal tools, automation
4. Eisenhower split with delegation

For each task, classify:

UrgentNot Urgent
ImportantFounder does TODAYFounder schedules this week
Not ImportantAgent does asyncParking lot / drop

Key question per task: "Does this require founder judgment, or can an agent execute it from the issue description?"

5. Choose outcomes

Outcomes = results, not tasks. Format: "By Friday, X is true."

Rules:

  • NOT limited to 3 — as many as realistic
  • Each outcome has a measurable check
  • Include both founder-only and agent-delegated work
  • Include B2B/sales if there are active deals — these are outcomes, not bonuses
  • Outcomes are commitments chosen with the user, not a silent reconstruction from the backlog
  • Use the backlog as input, then ask the user to choose or edit outcome options

Example:

Outcome: New feature launched
Check: deployed to production, 0 critical bugs by Friday
Founder: final UX decisions, announcement copy
Agent: implementation, tests, deploy script
6. Create issues in CORRECT repos

CRITICAL: Issue lives where the work happens. Use the task routing from your CLAUDE.md config.

Issue about backend bug → backend repo
Issue about marketing → marketing repo
Issue about content → content repo
Issue about strategy → main planning repo

Before creating any issue:

  1. VERIFY current state (check existing issues, files, data)
  2. PROPOSE to user
  3. CREATE only after verification

Label every issue: W{NN} + optionally retro:W{NN-1} if from retro.

7. Add to unified board

All W{NN} issues → your GitHub Project (from CLAUDE.md config: project_id and owner).

Create or use view "W{NN}" filtered by label.

bash
# Add to project (use project_id and owner from your config)
gh project item-add $PROJECT_ID --owner $YOUR_OWNER --url $ISSUE_URL

# Verify
gh search issues --owner $YOUR_OWNER --label "W{NN}" --state open
Show full SKILL.md (475 more words)Show less
8. Create the living weekly plan

Resolve the ISO week from the current local date. Never hardcode W34 or copy the previous filename.

bash
python3 skills/weekly-planning/scripts/living_week.py context --workspace . --json
python3 skills/weekly-planning/scripts/living_week.py create --workspace .

The generator creates reports/WNN-plan.html. Before presenting it:

  1. Remove every element with data-placeholder="true".
  2. Populate all seven day columns with accepted work; every task card has one data-area.
  3. Keep exactly one pair of daily:updated, daily:kanban, and hidden daily:day-slice markers. The local daily skill may replace only these marked regions.
  4. Mark past days as closed with the tasks and facts that actually happened. Highlight the current day. Keep future days as plan.
  5. Configure the three display time zones and the seven work Areas in the page script. Card color comes from Area metadata.
  6. Put the goal captured during retro/planning into each Area definition. The Area Explorer derives cards from the weekly board; it never stores a second task list.
  7. Keep Wealth as the recovery Area or rename it in config. Its daily habit checkboxes use a week-scoped localStorage key and must not be overwritten by agents.

The HTML page is a mutable view. Issues/task records and WNN-outcomes.md remain sources of truth. Daily updates preserve the full ISO week and mutate only the marked regions.

Red Flags — STOP

  • Creating all issues in one repo → WRONG, route to correct repo per config
  • Creating issue without checking current state → VERIFY FIRST
  • Claiming status without checking actual data → VERIFY
  • Planning 40h of productive work → budget 60% capacity
  • Skipping calendar mapping → leads to conflicts
  • Mixing "task" with "outcome" → outcome = result by Friday
  • Doing execution work inside planning → finish planning first, execute separately
  • Asking the user for facts that are already available in sources → read sources first
  • Writing deadlines without checking the actual date → verify current date and week range
  • Replacing the entire plan during daily update → mutate only the marker regions and preserve browser habit state
  • Copying last week's filename or localStorage key → resolve the current ISO week with the generator

Common Mistakes

MistakeFix
All issues in one repoRoute to where work happens
Issue created without verificationCheck issues + files + data first
Outcomes = task listRewrite as "by Friday, X is true"
Ignoring B2B as "bonus"Active deals with money = outcomes
Publishing paid content publiclyPaid content stays in paid repos
Assuming data without checkingVerify with gh issue list + actual files
Fixed 3 outcomes limitAs many outcomes as realistic
Executing tasks during planningCapture as outcomes/issues, execute after planning
Asking instead of readingCheck source systems first, ask only for missing facts

Integration with weekly-retro

This skill runs AFTER weekly-retro. Expected inputs:

  • Retro summary with what worked / didn't
  • Issues created during retro (label retro:W{NN-1})
  • Lessons learned and playbook updates
  • New tasks from retro interview

Setup

This skill reads config from your project's AGENTS.md / CLAUDE.md. Run corp-doctor first to generate or repair the config block, or add manually:

markdown
## Agent Operations Config

### Repos (scanned during retro/planning)
repos:
  - owner/repo-1    # what it does
  - owner/repo-2    # what it does

### GitHub Project
project_id: N
owner: your-github-handle

### Task Routing
routing:
  - pattern: "backend, bugs"
    repo: owner/backend-repo
  - pattern: "content, marketing"
    repo: owner/content-repo
  - pattern: "strategy, cross-cutting"
    repo: owner/main-repo

### Living plan
reports_dir: reports
local_timezone: system
display_timezones:
  - Europe/Berlin
  - Europe/Moscow
  - America/Argentina/Buenos_Aires
areas:
  - delivery
  - sales
  - systems
  - content
  - people
  - strategy
  - wealth
wealth_habits:
  - sport
  - reflection

Quick Reference

bash
# All tasks for current week
gh search issues --owner $YOUR_OWNER --label "W{NN}" --state open

# By repo
gh search issues --owner $YOUR_OWNER --label "W{NN}" --state open --json repository,number,title

# Close week (Friday)
gh search issues --owner $YOUR_OWNER --label "W{NN}" --state open --json title,repository
# Review: done / spillover / drop

© serejaris, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, assets) in skills/weekly-planning of serejaris/personal-corp-os.

  • SKILL.md
  • README.md
  • README.ru.md
  • assets/illustration.png
  • assets/living-week-plan.html
  • scripts/living_week.py

Open the folder on GitHubat commit 95e36c3

Compare with similar skills

Weekly Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Weekly Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weekly Planning this skillserejaris/personal-corp-os229—~2.4kAutomated safety check: PassMIT
Agentforce GenerateSalesforceAIResearch/agentforce-adlc1141 repos~7.4kAutomated safety check: PassCustom licence
Micropolis Command BusSimHacker/MicropolisCore208—~1.5kAutomated safety check: PassGPL-3.0
Setup Open IndexDrDroidLab/open-index112—~855Automated safety check: PassMIT
Slack Bot Builderdavila7/claude-code-templates33k5 repos~2.2kAutomated safety check: PassMIT
Retro MetaNecmttn/ax115—~1.8kAutomated safety check: PassAGPL-3.0

Similar skills

  • Agentforce Generate

    SalesforceAIResearch/agentforce-adlc

    Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script.

    114 GitHub starsUsed in 1 repo~7.4k tokens
    Agent WorkflowsAuto-check passed

  • Micropolis Command Bus

    SimHacker/MicropolisCore

    Routes all Micropolis UI, CLI, MCP, chat, pie menu, and LLM actions through a safe command bus with preview/proposal/approval.

    208 GitHub stars~1.5k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Setup Open Index

    DrDroidLab/open-index

    Install and configure Open Index as the read/write context layer for a domain-specialized agent.

    112 GitHub stars~855 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Slack Bot Builder

    davila7/claude-code-templates

    Build Slack apps using the Bolt framework across Python, JavaScript, and Java.

    33k GitHub starsUsed in 5 repos~2.2k tokens
    Agent WorkflowsAuto-check passed

  • Retro Meta

    Necmttn/ax

    Deep retro of retros - investigation pass that surfaces improvements across older retros and the current ax setup.

    115 GitHub stars~1.8k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Proactivity

    Prismer-AI/PrismerCloud

    Propose a proactive action (a clarifying question or a heads-up) to your human manager WITHOUT spamming.

    1.6k GitHub stars~987 tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed

More from serejaris/personal-corp-os

All 36 skills in this repo

  • Gh Issues

    serejaris/personal-corp-os

    A skill your agent uses when creating, searching, updating, or managing GitHub issues via CLI.

    229 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

  • Product Data Audit

    serejaris/personal-corp-os

    A skill your agent uses when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours.

    229 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

  • Tg Bot Ops

    serejaris/personal-corp-os

    A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.

    229 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check: notes

  • Audit Agent Rules

    serejaris/personal-corp-os

    Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after…

    229 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed

  • Make Landing

    serejaris/personal-corp-os

    Создаёт несколько вариантов дизайна 2D-поверхности (лендинг, герой, обложка, слайды): свой визуальный референс и автор на вариант, полный design.md с UTC/SHA-256 до кода, проверка в браузере…

    229 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check passed

  • Safe Public Release

    serejaris/personal-corp-os

    A skill your agent uses when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a…

    229 GitHub stars~3.4k tokensUpdated 3 days ago
    Auto-check: notes

Categories

Questions about Weekly Planning

What does Weekly Planning do?

A skill your agent uses 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…. Weekly Planning is an agent 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.

When should I use Weekly Planning?

Weekly Planning fits situations like: the user is transitioning from a completed retro into a weekly plan; choosing weekly outcomes; scheduling a full ISO week; asking for план на неделю.

How do I install Weekly Planning in Claude Code?

Run `npx skills add serejaris/personal-corp-os --skill weekly-planning -a claude-code`. Or copy the skill folder (skills/weekly-planning in serejaris/personal-corp-os) into .claude/skills/weekly-planning in your project. Claude Code loads it when a task matches its description.

How do I install Weekly Planning in Codex?

Run `npx skills add serejaris/personal-corp-os --skill weekly-planning -a codex`. Or copy the skill folder (skills/weekly-planning in serejaris/personal-corp-os) into .agents/skills/weekly-planning in your project. Codex loads it when a task matches its description.

Can I use Weekly Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add serejaris/personal-corp-os --skill weekly-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-planning, .gemini/skills/weekly-planning, .github/skills/weekly-planning and .opencode/skills/weekly-planning in your project.

What does Weekly Planning need to run?

Going by SKILL.md and its folder, Weekly Planning needs Python for the scripts in its folder and the command-line tools its instructions call (gh and python3). Our summary lists: Python 3.

Does Weekly Planning access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Weekly Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Weekly Planning use?

Weekly Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Weekly Planning use?

About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Weekly Planning?

Skills that share tags, products or a category with Weekly Planning: Agentforce Generate (SalesforceAIResearch/agentforce-adlc, 114 stars), Micropolis Command Bus (SimHacker/MicropolisCore, 208 stars), Setup Open Index (DrDroidLab/open-index, 112 stars) and Slack Bot Builder (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weekly Planning?

serejaris (a GitHub user) maintains it in serejaris/personal-corp-os, which has 229 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.

Source: serejaris/personal-corp-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.