Use when analyze competitors using Porter's Five Forces, positioning
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill competitive-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Competitive Strategy?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-competitive-strategy)More formats (shields.io, HTML) on the badges page.
---
name: competitive-strategy
description: Use when analyze competitors using Porter's Five Forces, positioning
maps, and competitive response frameworks. Use when assessing market position or
strategic threats.
domain: mindset
author: oyi77
license: Apache-2.0
subdomain: mindset
tags:
- competitive
- mindset
- personal-development
- soft-skills
- strategy
version: 1.0.0
category: mindset
---
# Competitive Strategy
## Overview
Mindset skill for competitive strategy. Builds capability through deliberate practice and structured frameworks.
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
## When to Use
**Trigger phrases:**
- "competitive strategy"
- "Entering a new market or segment"
- "Responding to competitive threats"
- "Defining product positioning"
- Entering a new market or segment
- Responding to competitive threats
- Defining product positioning
- Investor diligence or board strategy
- **When NOT to use**: Early-stage pre-PMF (focus on customers, not competitors), or hyper-growth (move fast, don't react to every competitor move)
## When NOT to Use
- When the situation requires professional counseling or therapy
- For high-stakes decisions that need expert judgment
- When the skill conflicts with cultural or personal values
## Core Principles
- **Start small** — Begin with manageable competitive strategy practices and build incrementally
- **Be consistent** — Daily practice beats occasional intense effort
- **Track progress** — Measure improvement to maintain motivation
- **Reflect regularly** — Review what's working and adjust your approach
## Daily Practice
1. **Morning intention** — Set a specific competitive strategy goal for the day
2. **Active practice** — Apply competitive strategy techniques during real situations
3. **Evening reflection** — Review the day's competitive strategy moments and lessons learned
4. **Journal entry** — Record insights, wins, and areas for improvement
## Frameworks
- **OODA Loop** — Observe, Orient, Decide, Act — for rapid competitive strategy decision cycles
- **PDCA Cycle** — Plan, Do, Check, Act — for iterative competitive strategy improvement
- **After-Action Review** — What happened? Why? What to improve?
- **Deliberate Practice** — Focused effort on specific competitive strategy weaknesses
## Common Pitfalls
- **Perfectionism** — Waiting for ideal conditions instead of starting now
- **Inconsistency** — Practicing sporadically instead of building a routine
- **Isolation** — Not seeking feedback or accountability partners
- **Overwhelm** — Trying to improve everything at once instead of focusing
## Resources
- Keep a competitive strategy journal for tracking progress
- Find an accountability partner or mentor
- Set weekly competitive strategy challenges with measurable outcomes
- Review and adjust your approach monthly
```markdown
# Daily Practice Template
## Morning (5 min)
- Set intention for the day
- Review top 3 priorities
## During the day
- Practice the skill in real situations
- Note moments of success and struggle
## Evening (5 min)
- Reflect: What worked? What did not?
- Log one lesson learned
```
## Process
1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run competitive strategy workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results
## Verification
- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findingsIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!