Interactive Personal Operating Model (POM) creation - define your strengths, weaknesses, pitfalls, decision system, and execution playbook. Use when user mentions "personal operating model", "create POM", "operating model", "my strengths and weaknesses", or wants to define how they work best.
Guides you through a 60-90 minute interactive interview to create a Personal Operating Model (POM) that defines your value creation loop, strengths, weaknesses, pitfalls, and execution playbook. Triggers when you mention "personal operating model," "create POM," "operating model," "my strengths and weaknesses," or want to define how you work best.
/plugin marketplace add Pitchlab/founder-support-system/plugin install founder-support-system@founder-support-systemThis skill is limited to using the following tools:
Create a comprehensive operating model that describes how you create value, your strengths/weaknesses, failure patterns, and execution playbook.
This skill guides you through an interactive interview to create your Personal Operating Model (POM) - a living document that defines:
Philosophy: "Treat weaknesses as design constraints. The goal is not self-improvement theatre. The goal is a system that works."
Speed: 60-90 minutes Tone: Analytical, honest, design-oriented Output: Notion page update (config.notion.personalOperatingModel)
Configuration: Notion page URLs are loaded in the following order (first found wins):
.claude/config.md or CLAUDE.md - Project-specific configuration (check working directory).claude-plugin/config.json - Plugin default configurationReference Pages (configured in config files, fetch ONCE per session):
Output Page:
Load Configuration:
// Use Read tool to load Notion page URLs from config
// Try in order (first found wins):
// 1. .claude/config.md (check for notion.* URLs in markdown)
// 2. CLAUDE.md (check for notion.* URLs in markdown)
// 3. .claude-plugin/config.json (JSON format)
// Extract all config.notion.* URLs for use below
Fetch context from Notion (using URLs from config):
Analyze for patterns:
For each section:
Pacing: This is 60-90 minutes. Don't rush. Depth > speed.
Purpose: Define your personal "value engine" as Input → Transformation → Output.
Interview Questions (ask using AskUserQuestion):
Inputs: "Think about the last 3 projects where you felt most in flow. What kinds of raw materials were you working with? (problems, data, people, situations, ideas)"
Transformation: "When you take that input, what do you actually DO to it? Not the deliverable, but the steps. Do you simplify? Frame? Systematize? Connect dots? Diagnose? What's your signature move?"
Outputs: "Which of your outputs have kept paying you back over time? What have you created that changed other people's decisions or created a durable asset?"
Avoid: "What kinds of inputs do people bring you that you CAN handle but really SHOULDN'T? What drains you even if you're good at it?"
Synthesize into:
Purpose: Identify strengths that are BOTH high-performing AND energy-positive.
Interview Questions:
Recognition: "What do people consistently thank you for or come to you for help with? What compliments do you hear repeatedly?"
Speed: "What do you do significantly faster than your peers? Where do you see the answer while others are still figuring out the question?"
Energy: "What work feels easy to you but seems hard to others? What could you do all day without getting tired?"
Context: "Pick one of those strengths. In what contexts does it absolutely shine? When does it weaken or backfire?"
Evidence: "For your top strength, give me 2-3 concrete examples with outcomes. Not 'I'm good at X' but 'I did X, which resulted in Y'."
Synthesize into (repeat for top 3-5 strengths):
Purpose: Identify your rare combination that creates unfair advantage.
Interview Questions:
Combination: "What's your unusual combination of skills or experiences? Most people have A or B, but you have both A AND B. What is that for you?"
Domain Bridging: "What do you know deeply that few people around you know? What can you connect across domains that others can't?"
Context Dominance: "In which specific contexts do you absolutely dominate? What kind of problems are 'made for you'?"
Timing: "At what stage or timing is your advantage highest? (0→1, scaling, crisis, research, turnaround, mature optimization)"
Synthesize into:
Purpose: Treat weaknesses as design constraints, not character flaws.
Interview Questions:
Categorize: "Think about your weaknesses. Which are skill gaps you could train? Which are energy drains you should avoid? Which are blind spots you must design around?"
Consistent Underperformance: "What consistently underperforms no matter how hard you try? Where do you reliably fall short?"
Trigger Conditions: "When do these weaknesses show up most? What situations activate them?"
Mitigation: "For your biggest weakness, what's the best mitigation strategy? (Outsource / automate / partner / checklist / timebox / avoid entirely)"
Good Enough: "What's your 'good enough' standard for this weakness? When is it OK to be mediocre here?"
Synthesize into (repeat for top 3-6 weaknesses):
Categorize:
Purpose: Identify failure patterns that require rules and interrupts, not motivation.
Interview Questions:
Pattern Recognition: "What mistake have you made 3+ times in your career? What's your 'here we go again' moment?"
Over-Investment: "Where do you consistently over-invest time, money, or energy for diminishing returns?"
Avoidance: "What do you consistently avoid that you KNOW matters? What important thing do you procrastinate on?"
Early Warnings: "For your biggest pitfall, what are the early warning signals? What's observable BEFORE you fall into it?"
Rationalization: "When you're falling into this pitfall, what do you tell yourself to justify it? What's your typical excuse?"
Synthesize into (repeat for 3-5 pitfalls):
Purpose: Define decision defaults that beat deliberation.
Interview Questions:
Speed Default: "Are you naturally a fast decider or a slow/careful decider? Where does this serve you? Where does it hurt you?"
Confidence Threshold: "What confidence level do you need to act? 60%? 80%? 95%? Does this vary by decision type?"
Reversibility: "How aware are you of reversible vs irreversible decisions? Do you treat them the same or differently?"
Opportunities: "When a new opportunity comes (project, partnership, product idea), what's your decision rule? What minimum info do you need?"
Success Metrics: "How do you know if something is working? What are your leading indicators vs lagging indicators?"
Synthesize into:
Decision Defaults:
Decision Rules by Type:
A) Opportunities (new projects, partnerships, ideas):
B) Commitments (long-term contracts, hires, big bets):
C) Daily Execution (what to do today):
Evaluation Function:
Purpose: Constraints protect long-term leverage from short-term motion.
Interview Questions:
Non-Negotiables: "What will you NOT do, even if it pays well? What crosses a line for you?"
Toxic Contexts: "What types of work degrade your output? What clients or contexts are poison for you?"
Capacity Limits: "What's your max parallel projects before quality drops? Max weekly meetings? Max deep work themes per week?"
Default No: "What are the 3 criteria where, if ANY are true, the answer is automatically no?"
Synthesize into:
Non-Negotiables:
Capacity Constraints:
Default "No" Criteria:
Purpose: Design your schedule around your brain, not obligations.
Interview Questions:
Peak Windows: "When during the day do you do your BEST thinking? When are you best at execution? When are you socially strongest?"
Low Energy: "When you're in a low-energy state, what tasks are safe? What tasks are dangerous?"
Burnout Indicators: "What are your first 3 warning signs of burnout? What happens before you crash?"
Recovery: "What reliably restores you? What's your minimum viable recovery protocol?"
Synthesize into:
Peak Windows:
Low-Energy Protocol:
Burnout Indicators & Recovery:
Purpose: Redesign surroundings so good path is default path.
Interview Questions:
Friction: "Where do you need MORE friction to stop bad habits? Where do you need LESS friction to ship more?"
Tools: "What tools genuinely amplify you (not just trendy)? What tools create drag?"
People: "What archetypes of people do you work best with? What kind of people drain you?"
Structures: "What structures keep you honest? (deadlines, public commitments, peer review, dashboards)"
Synthesize into:
Friction & Leverage:
Tools, People, Structures:
Purpose: Define default execution pattern for repeatable outcomes.
Interview Questions:
Phases: "Walk me through how you move from idea to shipped. What are your phases?"
Skips: "What do you consistently skip that you shouldn't? What causes delays?"
Overdoing: "What do you overdo? Where do you over-engineer or over-polish?"
Definition of Done: "How do you define 'done'? What's your minimum quality bar? What's your shipping cadence?"
Anti-Stall: "When progress stalls, what do you do? What's your go-to move to unstick yourself?"
Synthesize into:
Default Project Phases:
Definition of Done:
Anti-Stall Mechanisms:
Purpose: Small experiments that change the system. One variable at a time.
Interview Questions:
Clarity: "What experiment would create 10x clarity in how you work?"
Speed: "What would create 2x shipping speed?"
Pitfall Reduction: "What would reduce your biggest pitfall?"
Hypothesis: "Pick one experiment. What's your hypothesis? What are you testing?"
Metrics: "How will you measure success? How will you know it failed?"
Synthesize into (1-3 experiments):
Experiment: [name]
After all 11 sections:
Update POM page: https://www.notion.so/Your-POM-Page
Format:
# Personal Operating Model (POM)
*Last updated: [date]*
> Use this as a working document. Write short. Be concrete. Prefer examples over abstractions.
---
## 1) Core Loop — How You Create Value
[Section 1 synthesis]
---
## 2) Strengths — Energy-Positive Capabilities
[Section 2 synthesis]
---
[Continue for all 11 sections...]
---
## Appendix: Revision History
- [Date]: Created/Updated via planning-strategy:personal-operating-model
Ask for confirmation before saving (AskUserQuestion):
After saving:
A successful POM session should:
❌ Don't:
✅ Do:
POM feeds into:
POM is updated by:
Cadence:
Philosophy: "You're not optimizing yourself. You're designing a system that works."
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.