Seven Powers
- 311 installs
- 43 repo stars
- Updated March 7, 2026
- pmprompt/claude-plugin-product-management
seven-powers is a product management skill that analyzes a product or market using Hamilton Helmer's Seven Powers framework to identify durable moats, defensibility gaps, and strategic bets before roadmap lock-in.
About
seven-powers is a pmprompt/claude-plugin-product-management skill applying Hamilton Helmer's 7 Powers framework to reveal economic structures that protect business value from competition. The skill triggers on requests about 7 Powers, competitive moats, defensibility analysis, sustainable advantage, or economic moats. It helps developers and PMs identify which power—such as scale economies, network effects, or switching costs—applies to a product and where gaps remain. Inputs include product context, features, problems, and supporting research or constraints. Outputs are framework-aligned moat assessments and strategic bet recommendations for practical PM use rather than code generation. Reach for seven-powers during strategy reviews before committing to a roadmap or positioning narrative.
- Seven Powers taxonomy
- moat strength scoring
- incumbent vulnerability map
- power-stage timing
- strategy memo outline
Seven Powers by the numbers
- 311 all-time installs (skills.sh)
- +12 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #880 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill seven-powersAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 311 |
|---|---|
| repo stars | ★ 43 |
| Last updated | March 7, 2026 |
| Repository | pmprompt/claude-plugin-product-management ↗ |
How do you analyze product defensibility with Seven Powers?
Analyze a product or market using Hamilton Helmer's Seven Powers to identify durable moats, defensibility gaps, and strategic bets before roadmap lock-in.
Who is it for?
Developers and PMs evaluating strategic defensibility who need Hamilton Helmer's 7 Powers applied before roadmap and positioning decisions.
Skip if: Teams needing tactical sprint planning, dependency CVE scans, or UI implementation instead of economic moat and competitive structure analysis.
When should I use this skill?
The user asks about 7 Powers, competitive moats, defensibility analysis, sustainable advantage, economic moats, or Hamilton Helmer framework.
What you get
Seven Powers assessment, moat gap analysis, defensibility summary, and strategic bet recommendations
- Seven Powers assessment
- moat gap analysis
- strategic bet recommendations
By the numbers
- Implements Hamilton Helmer's 7 Powers competitive strategy framework
Files
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
7 Powers: The Foundations of Business Strategy
What It Is
7 Powers is a framework for understanding sustainable competitive advantage. The core insight: Business value comes from possessing an attribute that produces higher returns than competitors AND a barrier that prevents competitors from arbitraging it away.
Power = Benefit + Barrier
Warren Buffett famously said: "In business, I look for economic castles protected by unbreachable moats." Power is understanding what makes something a castle (the benefit) versus a shack, and what makes the moat unbreachable (the barrier).
The key shift: Move from asking "What's our competitive advantage?" to asking "What economic structure creates durable differential returns?"
When to Use It
Use 7 Powers when you need to:
- Evaluate a business's long-term defensibility (investment decisions, competitive analysis)
- Design a startup for durability (not just product-market fit)
- Understand why incumbents can't respond to your disruptive move
- Prioritize strategic initiatives based on what builds power
- Identify whether you actually have a moat or just operational excellence
- Plan second acts (new business lines that could develop power)
- Win market share battles in high-growth phases
When Not to Use It
- You don't have product-market fit yet
- The business is purely commodity with no differentiation possible
- You want to justify a strategy you've already decided on
- You're optimizing operations (power is about structure, not execution)
Resources
Books:
- 7 Powers by Hamilton Helmer
- Good Strategy Bad Strategy by Richard Rumelt
- Competition Demystified by Bruce Greenwald
Further Reading
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What is the seven-powers framework?
seven-powers applies Hamilton Helmer's 7 Powers, a model of economic structures—like network effects and switching costs—that protect business value from competition and inform strategic bets.
When should teams use seven-powers?
seven-powers fits strategy reviews before roadmap lock-in when defensibility, moats, or sustainable advantage questions arise and product context or research is available for analysis.