From pm-strategy
Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-strategy:competitive-intelligence-monitorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
Ask the user for these if not provided:
New Since Last Run: [n signals]
[Competitor]: [Signal] → [Implication] → [Recommended action + owner]
[Competitor]: [Signal] → [Why it matters now]
[Competitors with no new signals this week]
This Week's Strategic Summary: [2 sentences max — what is the overall competitive landscape doing?]
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-strategyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
2plugins reuse this skill
First indexed Jul 8, 2026