CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в…
Install Pm Prd
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install serejaris/personal-corp-os pm-prd --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pm-prd .claude/skills/pm-prd && rm -rf skills-srcUse ~/.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/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .claude/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prdType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install serejaris/personal-corp-os pm-prd --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pm-prd .agents/skills/pm-prd && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .agents/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install serejaris/personal-corp-os pm-prd --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pm-prd .cursor/skills/pm-prd && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .cursor/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/serejaris/personal-corp-os.git --path skills/pm-prd--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install serejaris/personal-corp-os pm-prd --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pm-prd .gemini/skills/pm-prd && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .gemini/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install serejaris/personal-corp-os pm-prdInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pm-prd .github/skills/pm-prd && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .github/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-prd -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install serejaris/personal-corp-os pm-prd --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pm-prd .opencode/skills/pm-prd && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pm-prd" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prd into .opencode/skills/pm-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prd", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pm-prd- GitHub stars
- 229
- Token cost
- ~2.2k tokens
- SKILL.md length
- 745 words
- Files
- 4 (incl. assets)
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в…
- Works in 4 steps: Parse input and branch by product type → Structured requirement breakdown → Generate the PRD → …
- Продуктовые требования
- SKILL.md covers Inputs, Step 1 — Parse input and…, Step 2 — Structured… and Step 3 — Generate the PRD, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pm Prd is an agent skill from serejaris/personal-corp-os. Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в Given-When-Then, аналитика и 10-пунктовый чеклист качества. User-invoked only — do NOT auto-trigger. Triggers on /pm-prd, "сделай PRD", "напиши PRD", "продуктовые требования", "make a PRD", "write a PRD", "draft requirements doc".
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `README.md` and `README.ru.md`).
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.
When your agent uses it
- Продуктовые требования
- Draft requirements doc
Example prompts
- “сделай PRD”
- “напиши PRD”
- “make a PRD”
- “/pm-prd”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Pm Prd loads about 2.2k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 745 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 745 words, ~2,167 tokens.
Download SKILL.mdSave it as
.claude/skills/pm-prd/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- pm-prd
- description
- Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в Given-When-Then, аналитика и 10-пунктовый чеклист качества. User-invoked only — do NOT auto-trigger. Triggers on /pm-prd, "сделай PRD", "напиши PRD", "продуктовые требования", "make a PRD", "write a PRD", "draft requirements doc".
pm-prd — Generate a structured PRD
Part of the Personal Corp framework — running a one-person business through AI agents. Generate a delivery-ready Product Requirements Document from a feature description. Branches by product type — B2C, B2B, internal tool, platform — with each type emphasizing different modules. Includes a 10-item quality self-check that runs after generation.
Inputs
| Field | Required | Notes |
|---|---|---|
| Feature description | yes | What the feature does and what problem it solves; one sentence minimum |
| Target user | no | Who it's for; inferred from the feature if not given |
| Business goals | no | Expected business metrics (DAU, conversion, revenue, etc.) |
| Product type | no | B2C / B2B / internal / platform; auto-detected if not given |
| Constraints | no | Tech limits, deadlines, resource limits |
| Depth | no | Outline (for review) / detailed (for development); default detailed |
If the user only says "write a PRD" with no feature, ask for the feature description. If they give feature + user + goals, go straight to generation.
Step 1 — Parse input and branch by product type
| Product type | PRD emphasis | Key differentiators |
|---|---|---|
| B2C | UX flow, growth metrics, A/B test plan | Heavy on interaction, heavy on data, write user journeys |
| B2B | Permission model, multi-tenancy, SLA, integration APIs | Heavy on completeness, security, API contracts |
| Internal tool | Operational efficiency, integration with existing systems, training cost | Heavy on practicality, light on visuals |
| Platform | Multi-role interaction, supply-demand matching, ecosystem rules | Heavy on role separation, rules engine |
Auto-detection rules: mentions of "user / member / loyalty / marketplace" → B2C; "enterprise / SaaS / CRM / admin panel" → B2B; "internal / management system / ticketing" → internal tool; "platform / marketplace / two-sided" → platform.
B2B PRDs must additionally cover:
- Permission matrix (role × feature × data scope)
- Multi-tenant data isolation approach
- Integration interfaces with the customer's existing systems
Platform PRDs must additionally cover:
- Independent feature view per role (supplier / consumer / platform ops)
- Matching rules and ranking strategy
- Commission / take-rate / settlement rules
Step 2 — Structured requirement breakdown
Three-method feature decomposition:
- User journey: trace the user's path from entry to goal completion; each node = one feature point
- Role split: list every role involved (end user, admin, ops); each role's actions = one feature module
- CRUD: for each core data object, walk through create / read / update / delete
For every feature module, fill:
- Feature description (one sentence)
- User story (As a {role}, I want to {action}, so that {value})
- Business rules (exhaustive — no "etc." or "other cases")
- Interaction (entry point → steps → success/failure feedback)
- Exception handling (timeouts, data anomalies, permission denied, edge cases)
Step 3 — Generate the PRD
Use this template. Comments next to each placeholder describe the fill logic.
# PRD: {feature name}
**Version:** v1.0
**Author:** {PM name, or [TBD]}
**Date:** {today}
**Status:** Draft
---
## 1. Background and Goals
### 1.1 Background
<!-- Answer three questions: why now? what happens if we don't? what changes if we do? -->
{problem state + user pain + why this is the right moment}
### 1.2 Target users
<!-- Use [role] + [trait] + [scenario]. Never write "all users". -->
| User role | Trait | Core need | Use scenario |
|---|---|---|---|
### 1.3 Business goals and success metrics
<!-- Each goal must be SMART — specific number + deadline. -->
| Goal | Metric | Target | Tracking method |
|---|---|---|---|
## 2. Requirement Overview
<!-- One paragraph, 30 words max, summarizing the core requirement. -->
## 3. Detailed Feature Design
### 3.1 {Module 1}
**Description:** {what it does}
**User story:** As a {role}, I want {action}, so that {value}
**Priority:** P0 (must launch) / P1 (strongly recommended) / P2 (nice-to-have)
**Business rules:**
1. {rule 1 — clear trigger condition + processing logic}
2. {rule 2}
**Interaction flow:**
<!-- Start at entry point, end at task completion, cover happy path + exception branches. -->
1. User enters from {entry}
2. {steps}
3. Success: {feedback}
4. Failure: {error message and handling}
**Exception handling:**
| Scenario | Handling | User-facing message |
|---|---|---|
(repeat format for each module)
## 4. Non-Functional Requirements
<!-- B2C → emphasize performance and experience; B2B → emphasize security and availability. -->
| Category | Requirement | Acceptance criterion |
|---|---|---|
| Performance | {e.g. page load time} | {e.g. < 2s} |
| Security | {e.g. data encryption} | {e.g. TLS 1.2+ in transit} |
| Compatibility | {browsers / devices} | {Chrome, Safari, mobile webview} |
## 5. Data Requirements (Analytics Events)
<!-- List every event to capture. Format: event name + trigger + attributes + purpose. -->
| Event | Trigger | Key attributes | Purpose |
|---|---|---|---|
## 6. Acceptance Criteria
<!-- At least 3 ACs per feature module, in Given-When-Then format. -->
| ID | Scenario | Given | When | Then |
|---|---|---|---|---|
## 7. Schedule
<!-- Break into design / dev / integration / launch. -->
| Phase | Estimate | Dependency | Risk |
|---|---|---|---|
## 8. Risks and Dependencies
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
## Appendix
- Related documents
- Competitor references
- Design filesShow full SKILL.md (337 more words)Show less
Step 4 — Quality self-check
Run this 10-point checklist after generating. Flag any failed item with a fix suggestion.
| # | Check | Pass criterion |
|---|---|---|
| 1 | Background not vague | Answers "why do this?" not just "we need to do this" |
| 2 | Goals quantified | At least one numeric success metric |
| 3 | Personas concrete | No "all users" / "everyone" |
| 4 | Business rules exhaustive | No "etc.", "other cases", "and so on" |
| 5 | Exception flows covered | Every feature has ≥2 exception scenarios |
| 6 | Acceptance testable | Given-When-Then format used |
| 7 | Analytics complete | All core action paths have events |
| 8 | No tech implementation | PRD describes "what", not "how to build" |
| 9 | Priorities assigned | Every module tagged P0/P1/P2 |
| 10 | Schedule grounded | Estimate covers design + dev + test + integration |
Common PRD anti-patterns
| Anti-pattern | What it looks like | Fix |
|---|---|---|
| Gold-plating | 50 features in v1 | Split MVP / v1.1 / v2; v1 keeps 3-5 core features |
| Fake requirement | "Users might want…" with no data | Tag every requirement with source: feedback / analytics / competitor / hypothesis |
| Design overreach | PRD specifies button color, font size, layout | Describe info hierarchy and interaction logic only; visuals → designer |
| Tech overreach | PRD specifies Redis, MySQL, framework choice | Describe perf requirements (e.g. "<2s") only; implementation → engineering |
| Rule blackhole | "Per business rules" without listing them | Enumerate every rule's trigger, logic, edge values |
Red lines
- PRD does not specify implementation — no DB type, language, framework
- PRD does not replace design specs — no detailed UI layout, colors, sizes
- No fabricated data — for any business data the user didn't provide (DAU, conversion), write
[TBD] - No missing roles — for multi-role features, every role's perspective must be covered
When input is incomplete
- Just "write a PRD" with no requirement → ask for the feature description with an example
- One-sentence requirement ("build a marketplace") → produce an outline-level PRD framework, mark
[needs input]on critical missing pieces - Requirement too large → suggest splitting into multiple PRDs; agree on MVP scope first
Related skills
/pm-user-stories— after PRD review, break features into developable User Stories/pm-competitive— run before PRD to gather competitor references/pm-prioritize— when multiple requirements compete, rank with RICE first
© 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 3 other files (assets) in skills/pm-prd of serejaris/personal-corp-os.
- SKILL.md
- README.md
- README.ru.md
- assets/illustration.png
Open the folder on GitHubat commit 95e36c3
Compare with similar skills
Pm Prd 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pm Prd this skillserejaris/personal-corp-os | 229 | — | ~2.2k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
More from serejaris/personal-corp-os
All 36 skills in this repoWeekly Planning
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…
Gh Issues
serejaris/personal-corp-os
A skill your agent uses when creating, searching, updating, or managing GitHub issues via CLI.
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.
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.
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…
Make Landing
serejaris/personal-corp-os
Создаёт несколько вариантов дизайна 2D-поверхности (лендинг, герой, обложка, слайды): свой визуальный референс и автор на вариант, полный design.md с UTC/SHA-256 до кода, проверка в браузере…
Related
Categories
Questions about Pm Prd
What does Pm Prd do?
Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в…. Pm Prd is an agent skill from serejaris/personal-corp-os. Генерирует структурированный PRD (Product Requirements Document) с шаблонами под тип продукта (B2C / B2B / внутренний инструмент / платформа) — фон, цели, детальный дизайн фич, acceptance criteria в Given-When-Then, аналитика и 10-пунктовый чеклист качества.
When should I use Pm Prd?
Pm Prd fits situations like: Продуктовые требования; draft requirements doc.
How do I install Pm Prd in Claude Code?
Run `npx skills add serejaris/personal-corp-os --skill pm-prd -a claude-code`. Or copy the skill folder (skills/pm-prd in serejaris/personal-corp-os) into .claude/skills/pm-prd in your project. Claude Code loads it when a task matches its description.
How do I install Pm Prd in Codex?
Run `npx skills add serejaris/personal-corp-os --skill pm-prd -a codex`. Or copy the skill folder (skills/pm-prd in serejaris/personal-corp-os) into .agents/skills/pm-prd in your project. Codex loads it when a task matches its description.
Can I use Pm Prd 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 pm-prd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pm-prd, .gemini/skills/pm-prd, .github/skills/pm-prd and .opencode/skills/pm-prd in your project.
What does Pm Prd need to run?
SKILL.md names no scripts, command-line tools or credentials: Pm Prd is instructions for the agent only.
Does Pm Prd access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pm Prd 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. Review the folder before installing.
What licence does Pm Prd use?
Pm Prd 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 Pm Prd use?
About 2.2k tokens (SKILL.md is roughly 8.7k 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 Pm Prd?
Skills that share tags, products or a category with Pm Prd: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pm Prd?
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.