Plan & spec
10,724 rows, by stacks then stars
2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid
whatsuppiyush/god-of-skills/seo/seo-cluster-builder Skill
1★ repoTurn ONE seed keyword into a full hub-and-spoke content plan grouped by real SERP overlap, not string similarity. Use whenever the user says "build a topic cluster", "content cluster", "pillar page", "hub and spoke", "content architecture", "group my keywords", "what pages should I write around X", or hands over a seed keyword and wants a content plan. Reach for it before anyone starts writing a batch of articles, when a blog has lots of overlapping posts cannibalizing each other, or when planning a new topic section from scratch. Returns a pillar page plus supporting spokes, each with intent and a target keyword, and a ready internal-link matrix.
whatsuppiyush/god-of-skills/seo/seo-content-brief Skill
1★ repoTurn a target keyword into a fill-in brief a writer can execute: search intent, target and per-section word counts, the H2/H3 outline, entities and questions to cover, internal and external link suggestions, and a title tag plus meta description set. Use whenever the user says "write a content brief", "content brief for X", "SEO brief", "outline for this keyword", "what should this article cover", or is about to commission or write a page and wants it built to outrank the current top 10. Reach for it before drafting any SEO article or landing page. Output is a ready-to-hand-off brief template.
whatsuppiyush/god-of-skills/seo/seo-content Skill
1★ repoThe full content-led SEO discipline: technical foundation, keyword research, SERP-driven page types, writing pages that outrank competitors, internal linking, distribution and link building, auditing/refreshing what you already published, and programmatic/product-led page generation. Use whenever the user wants organic search traffic, is planning or writing blog/SEO content, mentions keyword research, SERP analysis, page types (comparison, use-case, resource, hub), internal links, content pruning or refreshes, "why isn't my page ranking", "what should I write", programmatic pages, free-tool SEO, or getting backlinks. Reach for it even when the user just says "help me rank", "grow organic traffic", "plan our blog", "audit our content", or "get more SEO traffic".
jeremyinthebay/relay-skills/skills/two-claude-relay Skill
1★ repoSet up a two-agent autonomous loop where a planning agent writes briefs, an executing agent builds and opens PRs, and the planner independently verifies and merges — running unattended for hours. Use this whenever the user wants an agent to work autonomously, run overnight, keep working while they're away, self-review its own code, build a multi-agent or planner/executor setup, or asks how to let Claude Code run without supervision. Also use when someone asks "can I have an agent just keep going on its own" or wants to automate a build/review/merge cycle.
nathan8823/fairbill/.claude/skills/strategy Skill
1★ repoChoose the negotiation play and write the game plan — target number, sequence, escalation ladder, deadlines. Use once evidence is gathered (bill audited, prices benchmarked, assistance screened).
Chevis-Zhou/agent-skills/skills/plan-pipeline Skill
1★ repoDismantle work into phased plans with model+effort routing, or execute the next phase of an existing plan. Two modes — "/plan-pipeline dismantle <topic>" and "/plan-pipeline run <plan-path>".
Conduct stakeholder interviews
dineshrevunuru/SuperSkills/conduct-stakeholder-interviews Skill
1★ repoPlans and runs stakeholder interviews for a new project or client engagement: identifies who to interview, builds a business-goals discussion guide (success metrics, definitions of failure, political context), maps stakeholders on a Mendelow power-interest matrix with an attitude overlay, and produces a communication plan. Use when starting a discovery or freelance client engagement — 'kick off with the client', 'who should I talk to before designing', 'interview the stakeholders', 'what does the business actually want', 'map the stakeholders', 'the client and their team want different things', or before writing any research plan or proposal. NOT for interviewing users (conduct-user-interview) or writing user-facing question guides (write-interview-guide).
dineshrevunuru/SuperSkills/identify-business-problems Skill
1★ repoRanks candidate business problems and decides which ONE deserves work now — bottom-up opportunity sizing, risk-reward quadrant placement, milestone anchoring (nothing floats), and an explicit feasibility/capacity check before anything enters a roadmap. Use when the user says 'identify business problems', 'which problem should we solve first', 'is this worth doing', 'size this opportunity', 'prioritize these ideas/problems', 'what should we work on next quarter', or whenever multiple problems, asks, or projects compete for limited time or budget and someone must choose. Runs BEFORE write-problem-statement: this skill picks the problem; that skill frames it.
dineshrevunuru/SuperSkills/implement-spec Skill
1★ repoDrive a spec or set of tickets to shipped, committed code — the conductor of the SHIP-wing rigor path. Agrees the test seams up front, builds in vertical slices (red→green via `test-shipped-code` at each seam), runs `review-shipped-code` as an AND-gate before commit, and routes surprise breakage to `diagnose-bugs`. Use when asked to 'implement this spec', 'build this ticket', 'build out the feature', 'work through the tickets', 'implement what the spec says', 'build the booking flow', or before committing a shipped Next/React/TypeScript feature. Solo-first: the 'tickets' are a workpack BUILD-SPEC / tasks.json / a plain checklist, NOT an assumed Jira board — mode-switches UP to a tracker only when Dinesh actually has one. NOT for prototypes (build-coded-prototypes owns those — no tests, no review gate).
dineshrevunuru/SuperSkills/moderate-usability-session Skill
1★ repoModerates a live usability-test session the NN/g way: think-aloud intro script, neutral re-prompts, echo/boomerang/Columbo probes, intentional silence, the no-premature-rescue rule, atomic note capture, and observer ground rules with a post-session debrief. Use when running or preparing to run a session with a real participant — 'moderate the session', 'run the usability test', 'facilitator script', 'think-aloud instructions', 'the participant is stuck / asks for help / went quiet — what do I say?', 'brief my observers', 'debrief after the session'. NOT for planning the study (plan-usability-test), writing the tasks (write-task-scenarios), or analyzing results afterward (analyze-usability-data).
dineshrevunuru/SuperSkills/plan-large-work Skill
1★ repoPlan work too big for one agent session as a running MAP of investigation tickets — name the destination, chart the unknowns, resolve them ONE ticket per session until the build order is clear — instead of charging at a linear plan that collapses on the first unknown. SOLO DEFAULT: a local markdown investigation log, not a team tracker; mode-switch UP to GitHub Issues / Linear only when a real tracker already exists. Use for a big migration, refactor, or spec that won't fit one session, or when 'this is too big to plan', 'I don't know where to start', 'map out this migration', 'break down this epic', 'what do we need to figure out first', or a decision hangs on unknowns that must be resolved before committing an order. NOT for slicing an already-committed plan/spec into buildable build tickets — that is `plan-work-tickets`, the downstream step (a map produces the order; it slices the order). Cousin of `handoff-context`: the map persists across sessions; each session ends with a handoff.
dineshrevunuru/SuperSkills/plan-refactor Skill
1★ repoPlan a behavior-preserving refactor BEFORE touching it: fix the target shape, name the regression risk, pin behavior at the seam, then sequence it into small **always-green** steps that avoid a **big-bang rewrite**. Use when 'just clean this up', 'refactor X', 'this file is a mess', 'untangle this module', 'restructure this before I add to it', or before reshaping a risky area you don't want to break. SOLO DEFAULT: presents the plan / writes a local `refactor-plan.md` — mode-switches UP to a tracker issue only when Dinesh runs one. NOT for finding WHERE to refactor across an app (improve-code-architecture), the target module shape itself (codebase-design), or slicing NEW feature work (plan-work-tickets).
dineshrevunuru/SuperSkills/plan-usability-test Skill
1★ repoPlans a usability test end-to-end the NN/g way: study goals → qual/quant fork → sample size (5-user rule and exactly when it fails) → moderated/unmoderated × remote/in-person mode choice → recruiting numbers → mandatory pilot with fix-then-freeze. Use when asked to 'plan a usability test', 'set up user testing', 'test this prototype/app/flow', 'how many users do I need', 'is 5 users enough', 'moderated or unmoderated?', 'remote or in-person?', or when a stakeholder wants metrics from a small study. Produces a complete test plan document.
dineshrevunuru/SuperSkills/plan-work-tickets Skill
1★ repoSlices a plan or spec into small **tracer-bullet** tickets, each declaring its **blocking edges** (what must ship before it can start), then sequences them so you always build a ready one. Use when turning a plan, spec, or PRD into buildable work — 'break this into tickets', 'slice this spec', 'turn this into tasks', 'what should I build first', 'sequence this work', 'what depends on what', 'why did this task stall halfway'. SOLO DEFAULT: writes plain text files in a local `tickets/` folder — mode-switches UP to a real tracker's native blocking-links only when Dinesh actually runs one. NOT for framing the problem itself (write-problem-statement), for work still too big to order (plan-large-work), or for a throwaway spike (build-coded-prototypes).
dineshrevunuru/SuperSkills/triage-issues Skill
1★ repoAdvance incoming issues, bug reports, and external PRs through a lightweight state machine — categorize (bug vs enhancement), VERIFY the claim actually holds, then write an agent-ready brief a fresh AFK agent can build from cold. Use when a client/beta backlog, a pile of bug reports or feature asks, or an external PR needs sorting — 'triage this', 'triage my backlog', 'what needs my attention', 'is this a real bug', 'turn this issue into a brief', 'move this to ready-for-agent', 'write an agent brief for this'. SOLO DEFAULT: a short local list (client messages, beta feedback, a notes pile) triaged without labels or tracker ceremony; mode-switches UP to a GitHub issue-tracker + external-PR + out-of-scope-KB flow only when he explicitly has one. NOT the bug hunt itself (diagnose-bugs) or a PR's code review (review-shipped-code) — triage decides WHETHER to act and writes the spec; those do the work.
dineshrevunuru/SuperSkills/write-client-proposal Skill
1★ repoWrites freelance client proposals with tiered scope, value-anchored pricing, feasibility-checked timelines, and explicit assumptions + change control. Use when the user says 'write a proposal', 'scope this project', 'how much should I charge for this', 'the client asked for a quote', 'draft an SOW / statement of work', 'they want a price by Friday', or whenever a prospective or existing client needs a written offer of work for money. Also use to review a proposal before it goes out. Runs AFTER the problem is understood — if the client's problem is unsized or undefined, this skill routes to a paid discovery proposal instead.
dineshrevunuru/SuperSkills/write-problem-statement Skill
1★ repoWrites a single, solution-free problem statement and derives a scoped, timeboxed discovery plan from it (discovery goals + research questions + solution icebox). Use at the START of any project, feature, or client engagement — when the user says 'write a problem statement', 'frame this problem', 'what problem are we actually solving', 'kick off this project', 'scope the discovery', or when someone arrives holding a SOLUTION ('we need a chatbot / an app / a redesign') and the underlying problem is unstated. This is the entry gate for every project: if no problem statement exists yet, load this skill before any research, design, or build skill.
dineshrevunuru/SuperSkills/write-research-plan Skill
1★ repoWrites a complete one-page UX research plan using NN/g's 5-section structure (Purpose & Goals, Participants, Method & Procedure, Logistics, Relevant Documents) — with method-agnostic research questions, a saturation-based sample size, and a mandatory feasibility gate. Use when preparing ANY user research: 'write a research plan', 'plan this study', 'prepare user research', 'set up user interviews', 'how many participants do we need', 'what should our research questions be', or when a stakeholder asks for research and no plan document exists yet. NOT for choosing the method itself (choose-research-method) or writing the questions asked to participants (write-interview-guide).
dineshrevunuru/SuperSkills/write-task-scenarios Skill
1★ repoConverts research goals into unbiased, realistic usability-test task scenarios via NN/g's 7-step goal→question→activity→scenario chain, then lints them against the 10 task-writing mistakes and forks them for quant vs qual studies. Use when preparing what participants will DO in a usability test — 'write test tasks', 'task scenarios', 'what should we ask users to do', 'draft tasks for the usability study', 'are these tasks leading?'. NOT for interview questions (write-interview-guide) or overall study planning (plan-usability-test).
scullxbones/armature/internal/skillsembed/skills/armature-planner Skill
no license1★ repoUse when creating a new story or epic — translates objectives into a well-structured DAG of actionable work. Covers dag apply (with dry-run), dag transition, source registration, dependency linking, and validation before releasing work to workers.
mblauberg/provenant/skills/grill-me Skill
1★ repoUse when the user asks to be grilled or wants one-question-at-a-time stress testing of a plan or design. Not for writing the final spec or implementing it; use scope or implement.
furkangonel/cowrangler/bundled_skills/software-development/plan Skill
1★ repoStructured technical planning before implementation — architecture and task breakdown.
vishuwa2004/cskill-agents/agents/claude-code/skills/plan-mode-permission-gating Skill
1★ repoGate plan mode entry with permission updates so complex tasks run in a controlled, reviewable state.
The same file is in 1 other repository
vishuwa2004/cskill-agents/agents/codex/skills/plan-mode-permission-gating Skill
1★ repoGate plan mode entry with permission updates so complex tasks run in a controlled, reviewable state.
The same file is in 1 other repository
vishuwa2004/cskill-agents/skills/plan-mode-permission-gating Skill
1★ repoGate plan mode entry with permission updates so complex tasks run in a controlled, reviewable state.
The same file is in 1 other repository
Bandersnatch0x/design-playbook/packages/design-playbook/skills/ux-spec Skill
no license1★ repoDesign I/O plugin for Claude Code & coding agents — declarations + contracts that make UI generation constrained, reviewable, and recirculatable. Not a style pack; composes with ui-ux-pro-max + frontend-design.
OC-NeuralSense/reader-first-writing-skills/skills/frame-the-brief Skill
1★ repoDiagnostic. Activate when the writer has not yet settled who the document is for, why it exists, or what type it is. Common phrasings: "Who am I writing this for and what do they already know?", "Help me pin down the reader / audience / situation", "What kind of document is this and what must it do?". Expected inputs: a brief or topic, any audience hints, and an optional draft. Produces a reader-frame that every later stage reads from. Do NOT activate when a settled reader profile already exists and the writer wants structure (use build-argument), when they want an existing structure's logic checked (use test-argument), or when they want sentence-level fixes (use revise-prose). This skill only frames; it never outlines, argues, drafts, or edits prose.
jesse-black/docgarden/.agents/skills/planner-execplan Skill
1★ repoCreate, update, revise, reopen, or rescope a plan or ExecPlan using `PLANS.md`. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.
dingdawg/dingdawg-agent-1/io.github.dingdawg/dingdawg-planning-agent MCP server
1★ repoPlanning AI. Sprint estimation, task breakdown, risk analysis. Learns your velocity.
erenisci/acta/skills/legal-brief Skill
0★ repoConsolidate the separate legal briefs into ONE document to hand to a lawyer — never legal advice. Trigger on /acta:legal-brief, "brief for the lawyer", "prepare for legal counsel".
mukul-mschauhan/praxis-agent-suite/skills/strategy_synthesis Skill
no license0★ repoAgentic AI system built on Claude Skills
puretechnyc/purebrain-skills/skills/marketing/viral-comment-strategy Skill
0★ repoProven LinkedIn comment frameworks for virality. Three-part structure, human voice rules, reaction selection guide. Tested at 185,000+ profile appearances in 7 days from comments alone.
giovicordova/skills-gc/skills/interactive-qa Skill
no license0★ repoInteractive Q&A that collects the user's decisions when agents present multiple options or when multiple agents disagree. Produces a short plain-language brief the user can hand to Plan Mode, a specialized agent, or keep in context. Use this skill whenever any agent (or a board-meeting, brainstorming, or pre-plan session) comes back with 2+ reasonable options, trade-offs, or conflicting recommendations that need a human call — the user is not a developer, so options must be in non-technical plain English with the agent's recommendation flagged and any disagreement between agents surfaced. Also trigger on 'ask me', 'Q&A me', 'let me decide', 'collect my decisions', 'interactive Q&A', 'I need to decide', or any moment the current step is blocked waiting on a human decision. Do not guess the user's preference — ask.
giovicordova/skills-gc/skills/plan-challenger Skill
no license0★ repoStress-test and improve implementation plans before execution. Researches alternatives, challenges complexity, checks modularity and feasibility, then delivers a full revised plan. Use whenever the user has a plan — any format (PLAN.md, inline, pasted, attached) — and wants it reviewed before starting. Trigger on 'review this plan', 'challenge this plan', 'stress test', 'is this plan good', 'before we start', 'check the plan', or any request to validate or improve an implementation plan. Also use when the user seems hesitant about a plan or asks 'does this make sense'. Even if the user just says 'plan-challenger' or 'challenge it', invoke this skill.
tomaszstaniak/pm-ai-skills/first-90-days Skill
0★ repoLeadership transition framework based on Michael D. Watkins' "The First 90 Days". Use this skill whenever the user is discussing a role change, onboarding, new team, new boss, promotion, or stepping into leadership — even if they do not explicitly say "transition" or "90 days". Triggers include: (1) planning onboarding for a new leadership or management role, (2) building a 30-60-90 day plan, (3) diagnosing the business situation being entered (STARS model: Start-up, Turnaround, Accelerated growth, Realignment, Sustaining success), (4) planning critical early conversations with a new boss, peers, or team, (5) identifying and avoiding common transition traps, (6) accelerating time to value in a new role, (7) feeling overwhelmed or under pressure in the first weeks/months of a new job, (8) inheriting a team and unsure where to start, (9) being promoted and needing to "let go" of the old role, (10) joining a company in a new industry, function, or geography and needing to adapt fast.
tomaszstaniak/pm-ai-skills/good-strategy Skill
0★ repoStrategy evaluation and design framework based on Richard Rumelt's "Good Strategy Bad Strategy" and Michael Porter's "What Is Strategy?". Use this skill whenever the user is discussing strategy, plans, priorities, vision, roadmaps, OKRs, or competitive positioning — even if they do not explicitly say "good strategy", "Rumelt", "Porter", or "strategy kernel". Triggers include: (1) evaluating whether a strategy is good or bad, (2) diagnosing the core challenge before proposing solutions, (3) building a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-testing strategic plans with pre-mortem analysis, (5) diagnosing strategy claims that are actually goals, visions, or budgets dressed up as strategy, (6) reviewing a "strategy doc" or "strategic priorities" for fluff and incoherence, (7) applying Porter's five forces or value chain analysis, (8) deciding what to say "no" to and identifying trade-offs, (9) auditing roadmaps or resource allocation for strategic coherence.
tomaszstaniak/pm-ai-skills/positioning-and-pitch Skill
0★ repoFramework based on April Dunford's "Obviously Awesome" and "Sales Pitch". Use this skill whenever the user is discussing how to describe, frame, differentiate, sell, or talk about their product — even if they do not explicitly say "positioning," "pitch," or "messaging." Triggers include: (1) defining or evaluating product positioning using the five-component framework, (2) translating positioning into a compelling pitch for execs, boards, partners, or buyers, (3) choosing a market category strategy that shapes what you build and how you compete, (4) developing differentiated value claims, (5) diagnosing why your product story isn't landing with customers or stakeholders, (6) aligning teams around a shared positioning narrative and connecting it to roadmap priorities, (7) writing a launch announcement, website headline, or tagline, (8) deciding which features to highlight in marketing copy, demos, or sales decks, (9) responding when a buyer says "you sound like everyone else."
thinkyou0714/claude-lab-skills/lab-communication-translation/skills/stakeholder-translation Skill
0★ repo技術的な実装内容・判断・リスクを、非エンジニアのステークホルダーが理解できる言葉に変換する。「何が起きているか」「何が必要か」「何を決めてほしいか」を明確に伝える。非エンジニアへ報告・説明するときに使う。
thinkyou0714/claude-lab-skills/lab-implementation-flow/skills/rollback-plan Skill
0★ repo実装・デプロイ・マイグレーションが失敗した場合に元の状態に戻すための手順を設計する。何を・どの順序で・誰が・どこまで戻すかを事前に定義する。
thinkyou0714/claude-lab-skills/lab-strategy-design/skills/strategy-assessment Skill
0★ repo実行中の戦略・施策を、当初前提と実績の差分から査定し、継続・転換・撤退を判断する材料を整える。定期レビューや想定外の結果が出たときに使う。
Clinical-Quality-Artifical-Intelligence/nhs-clinical-safety-skills/skills/plan-clinical-review Skill
no license0★ repoClinical product direction review from a UK nursing perspective. The CQAI equivalent of /plan-ceo-review — asks the hard clinical questions before any technical planning. Reviews NMC Standards alignment, patient safety classification, health equity impact, and the "Ward Test". Use this INSTEAD of /plan-ceo-review for any nursing or clinical tool.
alexe-ev/product-plugins/business-commercial/skills/align-revenue-strategy Skill
0★ repoEnsure product decisions are aligned with the revenue model, pricing strategy, and commercial goals. Use this skill when a team needs to check or strengthen alignment between product direction and revenue outcomes.
alexe-ev/product-plugins/data-analytics/skills/plan-event-instrumentation Skill
0★ repoPlan the event tracking and instrumentation needed to measure product behavior and support analytics. Use this skill when a feature is being built and the analytics implementation needs to be defined before development.
alexe-ev/product-plugins/experimentation/skills/design-experiment-plan Skill
0★ repoBuild a complete product experiment plan from a validated hypothesis, metrics, and testing assumptions. Use this skill when the user is ready to prepare an A/B test or structured product experiment for execution.
alexe-ev/product-plugins/gtm/skills/plan-product-launch Skill
0★ repoBuild a launch plan including readiness criteria, timeline, channels, and stakeholder coordination. Use this skill when a team is preparing to launch a product, feature, or major update.
alexe-ev/product-plugins/leadership-communication/skills/map-stakeholder-influence Skill
0★ repoMap key stakeholders, their interests and influence, and develop strategies to align and engage them. Use this skill when a team needs to navigate stakeholder dynamics for a product initiative.
alexe-ev/product-plugins/leadership-communication/skills/run-stakeholder-alignment Skill
0★ repoPlan and execute a stakeholder alignment process for a product decision or initiative. Use this skill when a team needs to build genuine alignment — not just sign-off — across multiple stakeholders.
alexe-ev/product-plugins/leadership-communication/skills/write-product-strategy-doc Skill
0★ repoWrite a clear, concise product strategy document that aligns teams on direction, priorities, and trade-offs. Use this skill when a team needs a written strategy artifact that can serve as a decision-making anchor.
alexe-ev/product-plugins/marketing-growth/skills/plan-lifecycle-engagement Skill
0★ repoDesign a lifecycle engagement strategy including onboarding, nurture, and re-engagement flows. Use this skill when a team needs to systematically improve how they engage users across their lifecycle.
alexe-ev/product-plugins/product-ops/skills/design-planning-process Skill
0★ repoDesign a product planning process that connects strategy to execution through a repeatable cycle of goal setting, roadmapping, and delivery. Use this skill when a team's planning is ad-hoc, inconsistent, or disconnected from strategy.
alexe-ev/product-plugins/product-planning/skills/align-goals-to-strategy Skill
0★ repoCheck and strengthen the alignment between team-level goals (OKRs, KPIs) and company strategy. Use this skill when goals have been set but their connection to strategy is unclear, inconsistent, or contested.
Apply prioritization framework
alexe-ev/product-plugins/product-planning/skills/apply-prioritization-framework Skill
0★ repoApply a structured prioritization framework (RICE, MoSCoW, ICE, opportunity scoring, etc.) to rank initiatives or features. Use this skill when a team needs to move from a backlog of ideas to a prioritized, rationale-backed list.
alexe-ev/product-plugins/product-planning/skills/build-roadmap-prioritization Skill
0★ repoBuild and prioritize a feature or initiative roadmap using structured frameworks. Use this skill when a team has a backlog or list of initiatives and needs a coherent, prioritized plan.
alexe-ev/product-plugins/product-planning/skills/plan-delivery-collaboration Skill
0★ repoStructure delivery planning, cross-functional alignment, and sprint or milestone planning. Use this skill when a team needs to coordinate execution across product, engineering, and design.
alexe-ev/product-plugins/product-planning/skills/write-requirements-prd Skill
0★ repoWrite clear, complete product requirements documents and user stories. Use this skill when a team is ready to define what needs to be built for a prioritized initiative.
alexe-ev/product-plugins/product-planning/skills/write-user-stories Skill
0★ repoWrite well-formed user stories with clear acceptance criteria ready for development. Use this skill when a team needs to break down a feature or initiative into development-ready stories.
Build portfolio roadmap strategy
alexe-ev/product-plugins/product-strategy/skills/build-portfolio-roadmap-strategy Skill
0★ repoStructure product portfolio decisions and translate strategy into a prioritized roadmap. Use this skill when a team needs to align investment decisions with strategic goals and build a coherent roadmap.
alexe-ev/product-plugins/product-strategy/skills/define-strategic-positioning Skill
0★ repoDefine a clear strategic positioning statement that articulates where the product plays, who it serves best, and what makes it the right choice for that segment. Use this skill when the team needs to anchor strategy in a specific market position.
alexe-ev/product-plugins/product-strategy/skills/prioritize-strategic-bets Skill
0★ repoEvaluate and prioritize strategic bets — high-uncertainty, high-potential initiatives — against business goals and risk tolerance. Use this skill when a team needs to decide which big bets to pursue, pause, or stop.
alexe-ev/product-plugins/risk-compliance/skills/plan-risk-mitigation Skill
0★ repoIdentify product risks and develop mitigation plans with owners, triggers, and contingencies. Use this skill when a team needs to proactively manage risks for a product initiative.