Context Modes
0xNyk/lacp
Structured work modes for agent sessions. An agent skill from 0xNyk/lacp.
Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности.
Install Pm Brainstorm
$ npx skills add serejaris/personal-corp-os --skill pm-brainstorm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install serejaris/personal-corp-os pm-brainstorm --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-brainstorm .claude/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .claude/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstormType 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-brainstorm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install serejaris/personal-corp-os pm-brainstorm --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-brainstorm .agents/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .agents/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstorm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install serejaris/personal-corp-os pm-brainstorm --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-brainstorm .cursor/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .cursor/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstorm--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-brainstorm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install serejaris/personal-corp-os pm-brainstorm --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-brainstorm .gemini/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .gemini/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstormInstalls 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-brainstorm -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-brainstorm .github/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .github/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstorm -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-brainstorm --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-brainstorm .opencode/skills/pm-brainstorm && 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-brainstorm" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-brainstorm into .opencode/skills/pm-brainstorm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-brainstorm", 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-brainstorm- GitHub stars
- 229
- Token cost
- ~2.1k tokens
- SKILL.md length
- 972 words
- Files
- 4 (incl. assets)
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности.
- Works in 8 steps: Problem focus → SCAMPER (7 lenses) → 5-Whys root-cause divergence → …
- Идеи для продукта
- SKILL.md covers Inputs, Step 1 — Problem focus, Step 2 — SCAMPER (7 lenses) and Step 3 — 5-Whys root-cause…, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pm Brainstorm is an agent skill from serejaris/personal-corp-os. Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности. Встроены SCAMPER (7 ракурсов), 5 Whys для поиска корневой причины, кросс-доменное вдохновение, ограничивающие инновации, обратный брейншторм и матрица Impact/Effort для отбора. На выходе — ≥10 идей с детально проработанным Top-3. User-invoked only — do NOT auto-trigger. Triggers on /pm-brainstorm, "идеи для продукта", "продуктовый брейншторм", "дивергенция идей", "How Might We", "SCAMPER", "product brainstorm"…
Its SKILL.md is about 2.1k 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 Agent Workflows, covering Brainstorming, Root cause analysis and Prioritization frameworks. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.
When your agent uses it
- Идеи для продукта
- Продуктовый брейншторм
- Дивергенция идей
- Product brainstorm
Example prompts
- “How Might We”
- “SCAMPER”
- “product brainstorm”
- “/pm-brainstorm”
Workflow steps
8 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 Brainstorm loads about 2.1k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 972 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). 972 words, ~2,142 tokens.
Download SKILL.mdSave it as
.claude/skills/pm-brainstorm/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- pm-brainstorm
- description
- Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности. Встроены SCAMPER (7 ракурсов), 5 Whys для поиска корневой причины, кросс-доменное вдохновение, ограничивающие инновации, обратный брейншторм и матрица Impact/Effort для отбора. На выходе — ≥10 идей с детально проработанным Top-3. User-invoked only — do NOT auto-trigger. Triggers on /pm-brainstorm, "идеи для продукта", "продуктовый брейншторм", "дивергенция идей", "How Might We", "SCAMPER", "product brainstorm", "feature ideas".
pm-brainstorm — Structured product brainstorm
Part of the Personal Corp framework — running a one-person business through AI agents. Run a structured creative-divergence session on a specific product problem or opportunity. Not just listing ideas — challenges assumptions, borrows across domains, helps reach options you wouldn't have otherwise. Output is a screened idea list ready for next-step action.
Inputs
| Field | Required | Notes |
|---|---|---|
| Topic | yes | Problem to solve or opportunity to explore — more specific = better |
| Background | no | Persona, current data, known constraints |
| Mode | no | Full divergence / single framework only; default full |
| Constraints | no | Tech, time, resource limits |
Good topic: "How might we make new users feel value within the first 5 minutes of first use?" Bad topic: "How do we improve the product?" (too vague)
Step 1 — Problem focus
Before diverging, sharpen the problem.
Probing checklist:
- Who has this problem? Specific user types and scenarios
- How is it solved today? Current alternative or workaround
- Why does it matter? Consequence of inaction
- What does success look like? What does a good solution look like
- What constraints? Tech / time / resource bounds
Restate as a How Might We:
- "How might we let {target user} more easily {achieve goal} in {scenario}?"
Step 2 — SCAMPER (7 lenses)
Run each lens once; aim for 1-2 ideas per lens.
| Lens | Core question | Direction |
|---|---|---|
| S — Substitute | What component can be substituted? | Different tech / interaction / entry point? |
| C — Combine | Can we merge two features? | Merge steps / contexts / bundle features |
| A — Adapt | What from elsewhere can we borrow? | Method from social apps? From productivity tools? |
| M — Modify | What if we 10×'d or 0.1×'d this? | Minimal version? Maximal version? |
| P — Put to other use | What other context could this serve? | Other personas? Other scenarios? |
| E — Eliminate | What if we remove something? | Cut steps / fields / signup / friction? |
| R — Rearrange | What if we reorder? | Try first / signup later? Reverse order? |
Total: 7-14 initial ideas.
Step 3 — 5-Whys root-cause divergence
From a user pain, descend to the root, then ideate from each layer.
Example:
Pain: new users churn on day 2
- Why 1: They didn't find what they wanted on day 1
- Why 2: Feature entries are too deep
- Why 3: Navigation is structured by product architecture, not user task
- Why 4: No user-task analysis was done
- Why 5 (root): Product design is detached from actual user scenarios
- Idea: Run user-task analysis, restructure navigation by task
- Idea: Add search / smart-recommendations entry point
- Why 4: No user-task analysis was done
- Idea: Onboarding leads users directly to core feature
- Why 3: Navigation is structured by product architecture, not user task
- Idea: Ask intent at signup, personalize home
- Why 2: Feature entries are too deep
Rules:
- Probe to at least Why 3
- Each Why can fork (one symptom may have multiple causes)
- Generate 1-2 solutions per Why layer
Step 4 — Cross-domain inspiration
Don't copy competitors — look at what they do, then think "what could we do that's different".
Cross-domain prompts:
- List 3-5 products that are not direct competitors but solve a similar user need
- Note what's notable about each
- Ask: if we transplanted this approach to our context, what would adapt? What would change?
Differentiation prompts:
- Everyone does X → what if we do Y instead?
- Competitor's X is criticized for Z → could we cut into the pain at Z?
- Need users discuss heavily on social media but no competitor has shipped → opportunity?
Step 5 — Constraint-innovation
Deliberately set constraints to spark creativity.
| Constraint | Setup | Stimulus |
|---|---|---|
| Time | "Only 1 week of dev time" | Forces minimum viable approach |
| Tech | "Use only existing stack" | Reveals new uses of existing capabilities |
| Cost | "Zero dev investment" | Ops moves, config changes, copy tweaks |
| Extreme | "Change one line of code" | Find the highest-leverage single point |
| Inversion | "Let users design it" | Switch perspective |
1-2 ideas per constraint. Tighter constraints often produce more elegant ideas.
Show full SKILL.md (362 more words)Show less
Step 6 — Reverse brainstorm
First think "how could we make this worse", then invert each idea.
Steps:
- Restate as the inverse: "How might we make new users uninstall on day 1?"
- List everything that would worsen the problem (often easier than positive ideation)
- Invert each "make-worse" idea into an improvement
Example:
| Make-worse | Inverted |
|---|---|
| Require 20 fields at signup | Phone-only signup, progressive profile fill |
| Home is full of ads | Home shows only goal-relevant content |
| Hide all help entries | Surface guidance proactively at confusion points |
Reverse-brainstorm bypasses the "find the right answer" pressure — the divergence stage gets freer.
Step 7 — Impact / Effort screening
Drop all ideas into a 2×2:
| Quadrant | Impact | Effort | Strategy | Ideas |
|---|---|---|---|---|
| Quick Wins | High | Low | Validate first | {list} |
| Big Bets | High | High | Worth investing, plan carefully | {list} |
| Fill-ins | Low | Low | When idle | {list} |
| Money Pits | Low | High | Drop | {list} |
Scoring:
- Impact: size of pain solved × users affected
- Effort: dev + design + integration test
Step 8 — Output
# Product Brainstorm
**Topic:** {problem}
**HMW:** How might we {restated as HMW}
**Date:** {today}
**Ideas generated:** {N} (kept after screening: {M})
## Idea List
| # | Idea | Pain solved | Source framework | Expected value | Effort | Quadrant | Validation |
|---|---|---|---|---|---|---|---|
| 1 | {desc} | {pain} | SCAMPER-Eliminate | High/Med/Low | High/Med/Low | Quick Win | {validation} |
## Top 3 Recommendations
### Idea 1: {name}
- **Description:** {detail}
- **Pain solved:** {specific pain}
- **Expected impact:** {quantified, e.g. "+5-10% D1 retention"}
- **Implementation path:** {brief tech / design approach}
- **Validation:** {how to validate fast — A/B test, gradual rollout, etc.}
- **Risk:** {risks and mitigation}
### Idea 2: {name}
…
### Idea 3: {name}
…
## Dropped Ideas (archived)
- {idea X}: dropped because — {reason}
- {idea Y}: dropped because — {reason}
## Next Actions
- [ ] {action 1}
- [ ] {action 2}Brainstorm principles
- Diverge before converge — no judgment during divergence; screen during convergence
- Quantity drives quality — first hit 15+ ideas, then screen
- Concrete beats abstract — "add a progress bar at signup step 3" beats "improve signup UX"
- Allow extremes — extreme ideas, refined, often become great
- Challenge assumptions — push back on "impossible" / "we've always done it this way"
Quality bar
- ≥ 10 ideas generated (sufficient divergence)
- Each idea has a concrete description (not vague "optimize X")
- Ideas come from ≥ 3 different frameworks
- Top 3 have explicit validation methods
- Output is decision-ready as input to the next step
Red lines
- No rejection during divergence — never say "can't" / "impossible" while ideating
- No empty advice — "improve UX" is fluff, not an idea
- Doesn't replace decision — outputs options, not the choice
When input is incomplete
- Topic too broad → narrow it (probe scenario and user)
- Missing background → ideate on generic product logic, tag "recommend specific data for sharper output"
- Single framework specified → use only that one, but suggest "more frameworks = more dimensions"
Related skills
/pm-prd— Top idea → PRD/pm-prioritize— Idea list → formal ranking/pm-user-stories— Ideas → developable Stories/pm-feedback— Pain points from feedback → brainstorm fuel/pm-competitive— Validate differentiation level
© 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-brainstorm 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 Brainstorm 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 Brainstorm this skillserejaris/personal-corp-os | 229 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Context Modes0xNyk/lacp | 305 | — | ~313 | Automated safety check: Pass | MIT | |
| StrategyEliasOulkadi/shokunin | 114 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Brainstormingobra/superpowers | 297k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 52 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Strategy
EliasOulkadi/shokunin
Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Brainstorming
obra/superpowers
Makes the agent clarify intent and agree on a design with you before writing any code, scaling the process from a quick spike to a written spec.
Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
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 Brainstorm
What does Pm Brainstorm do?
Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности. Pm Brainstorm is an agent skill from serejaris/personal-corp-os. Проводит структурированный сеанс дивергенции вокруг конкретной продуктовой проблемы или возможности.
When should I use Pm Brainstorm?
Pm Brainstorm fits situations like: Идеи для продукта; Продуктовый брейншторм; Дивергенция идей; product brainstorm.
How do I install Pm Brainstorm in Claude Code?
Run `npx skills add serejaris/personal-corp-os --skill pm-brainstorm -a claude-code`. Or copy the skill folder (skills/pm-brainstorm in serejaris/personal-corp-os) into .claude/skills/pm-brainstorm in your project. Claude Code loads it when a task matches its description.
How do I install Pm Brainstorm in Codex?
Run `npx skills add serejaris/personal-corp-os --skill pm-brainstorm -a codex`. Or copy the skill folder (skills/pm-brainstorm in serejaris/personal-corp-os) into .agents/skills/pm-brainstorm in your project. Codex loads it when a task matches its description.
Can I use Pm Brainstorm 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-brainstorm -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-brainstorm, .gemini/skills/pm-brainstorm, .github/skills/pm-brainstorm and .opencode/skills/pm-brainstorm in your project.
What does Pm Brainstorm need to run?
SKILL.md names no scripts, command-line tools or credentials: Pm Brainstorm is instructions for the agent only.
Does Pm Brainstorm 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 Brainstorm 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 Brainstorm use?
Pm Brainstorm 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 Brainstorm use?
About 2.1k tokens (SKILL.md is roughly 8.6k 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 Brainstorm?
Skills that share tags, products or a category with Pm Brainstorm: Context Modes (0xNyk/lacp, 305 stars), Strategy (EliasOulkadi/shokunin, 114 stars), Diagnosing Superpowers Sessions (obra/superpowers, 297k stars) and Brainstorming (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pm Brainstorm?
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.