Personal Corp OS

Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".

This repo holds the open skills for Claude Code and Codex that the framework is built from. Start with the six weekly-rhythm skills; add the rest when you need them.

By Ris — AI development & vibecoding.

Русская версия: README.ru.md.

The problem: you are the bottleneck

Not because you work too little. Because strategy, memory, coordination, execution, and acceptance all sit in one pile — inside your head. While that is true, your department's throughput equals yours.

Hiring does not fix it: a new person takes the work but not the context, so you keep explaining. AI alone does not fix it either: an agent without context is the same new hire, except it does not remember yesterday.

The issue is not model strength. The issue is that context never leaves your head.

The fix: a route, not a toolbox

Personal knowledge becomes company capital only when it travels the whole route.

graph LR
    A["Task<br/>owner + criteria"] --> B["Execution<br/>human or agent"]
    B --> C["Acceptance<br/>good enough or not"]
    C --> D["Pattern<br/>what worked"]
    D --> E["Department memory<br/>rules and decisions"]
    E --> F["Priority<br/>next week"]
    F --> A
    style A fill:#8b5cf6,color:#fff
    style C fill:#f59e0b,color:#fff
    style E fill:#10b981,color:#fff

Three links of that route carry most of the value.

1. Writing the task down. A thought becomes a task once it has an owner, done criteria, and a place to live. Before that it lives in you. After that both a human and an agent can pick it up, because they have the same access to it.

2. Experience accumulating in departments. Artifacts and decisions settle in a department — a separate repository for its own domain. Next time the agent reads the department instead of reading you.

3. Retro with the agent. Once a week you look at what worked and promote it into rules. Whatever you corrected twice becomes a written rule and stops needing you.

The weekly rhythm

Three links on their own are a feature list. The rhythm turns them into a system.

graph LR
    R["weekly-retro<br/>what worked"] --> P["weekly-planning<br/>priorities of the week"]
    P --> T["task-routing<br/>tasks into departments"]
    T --> E["Execution<br/>manager writes the trace back"]
    E --> R
    style R fill:#f59e0b,color:#fff
    style P fill:#3b82f6,color:#fff
    style T fill:#8b5cf6,color:#fff
    style E fill:#10b981,color:#fff

The rhythm answers the question that usually stays unanswered: when exactly does experience turn into a rule. Answer: at the retro, once a week, not "someday".

Departments: where experience lives

A department is a separate repository that owns one domain and accumulates its artifacts, decisions, and rules.

the layer      owns truth
the department owns the artifact
the agent      owns execution
acceptance     owns the "good enough" call

While experience sits in your head, it disappears with your attention. Once it sits in a department, the next agent and the next person both use it.

First step: 30 minutes today

1. Install the plugin (see Install).
2. Run corp-init to set up the loop: where tasks, rules, and weekly plans live.
3. Create your first department with corp-new and put one real task into it with task-routing.
4. End of the week: run weekly-retro. Start of the next: run weekly-planning.

After two such weeks the department has its own memory, and part of the decisions stop going through you.

The six skills of the route

Where this leads

Your job shrinks to three moves: set the goal, pick the next move, accept the result.

Install

Claude Code

Terminal:

claude plugin marketplace add serejaris/personal-corp-os
claude plugin install personal-corp-os@personal-corp-os
claude plugin details personal-corp-os

Claude Code Desktop or interactive /plugin flow:

1. Open Plugins or /plugin.
2. Add marketplace: serejaris/personal-corp-os.
3. Install personal-corp-os.

Codex

This repo includes a Codex plugin manifest at .codex-plugin/plugin.json.
Add the marketplace from GitHub, then install the plugin:

codex plugin marketplace add serejaris/personal-corp-os
codex plugin add personal-corp-os@personal-corp-os

After installation, start a new Codex thread and try:

Use Personal Corp skills to plan my week.

Migrating from personal-corp-skills

The repository was named personal-corp-skills until 2026-08-06. GitHub redirects the old links. The plugin identifier was renamed along with the repository, so remove the installed personal-corp-skills plugin via /plugin in Claude Code and install the new one using the instructions above.

Single Skill

Use this when you want one skill folder instead of the whole plugin:

Install this skill: https://github.com/serejaris/personal-corp-os/tree/main/skills/cc-analytics

Replace cc-analytics with any skill name from the table below.

All skills

Design and Media Skills

Product Management Skills

graph LR
    pmFeedback[pm-feedback] --> pmPrioritize[pm-prioritize]
    pmCompetitive[pm-competitive] --> pmPrioritize
    pmBrainstorm[pm-brainstorm] --> pmPrioritize
    pmPrioritize --> pmPrd[pm-prd]
    pmPrd --> pmUserStories[pm-user-stories]
    pmMetrics[pm-metrics] --> pmRoadmap[pm-roadmap]
    pmRoadmap --> pmPrioritize

Telegram

Other

Statusline

Custom statusline showing costs, context usage, and git branch with color-coded indicators.

Archived Skills

Archived skills are preserved for reference and are not part of the active
plugin skill set.

Manual Installation

Skills are plain folders. Copy the whole skill directory so optional references
and examples are preserved:

cp -r skills/<name> ~/.claude/skills/

Author

• Telegram: @ris_ai — AI development & vibecoding
• YouTube: @serejaris
• vibecoding.phd

License

MIT

Security

Please report secrets, private data exposure, or exploitable behavior privately.
See SECURITY.md.