Product & Planning

open-mercato Bundle

Grounded platform gap analysis at engagement scale — turn a folder of client docs into an Epic/Story tree where every coverage verdict is re-run by executable gates against a validated checkout of the platform, scored in atomic commits, license-tier-tagged, and synthesized into a client-facing summary + backlog. Use when the user says "gap analysis", "what does the platform already cover", "coverage report", "analiza luk", "co platforma już pokrywa", "ile z tego już jest w platformie". This skill verifies coverage against the platform's code; it does not author requirements or specs — use the spec-writing skills for that.

open-mercato Bundle

Build a complete standalone business app, module, or CRUD vertical slice using Open Mercato discovery, commands, APIs, ACL/setup, UI, events, search, migrations, and tests. Use for customer management, deal-pipeline changes, CRM lead capture, library/booking/rental systems, "create a module", "add CRUD entity", "stwórz moduł", or another one-shot domain outcome.

x10aix Skill

BluOS CLI (blu) for discovery, playback, grouping, and volume.

k-dense-ai Bundle

Applies the computational biology and AI-driven reasoning of Aviv Regev (computational biologist, Genentech, single-cell genomics). Use this skill whenever the user is dealing with experimental design, high-dimensional data analysis, integrating AI into scientific workflows, scaling biological research, or navigating noisy, complex systems. Trigger this for topics like single-cell genomics, drug discovery, biological atlases, interdisciplinary research strategy, or when deciding between depth vs. breadth in data collection.

k-dense-ai Bundle

Use this skill whenever reasoning about immunology, host-pathogen interactions, innate immunity, Toll-like receptors (TLRs), or experimental design in molecular biology. It is also highly relevant for scientific career strategy, particularly when discussing independence, pivoting research domains, or using reverse genetics (like knockout mice) for discovery. Channel Shizuo Akira, immunologist and pioneer of pattern-recognition receptors, to apply rigorous experimental standards (e.g., demanding chemically synthesized mimics over purified extracts) and to view innate immunity as a highly specific, compartmentalized system rather than a primitive defense.

k-dense-ai Bundle

Use this skill whenever you are reasoning about large-scale scientific projects, genomics, bioethics, data infrastructure, or long-term medical translation. Eric S. Lander (geneticist, Broad Institute, Human Genome Project) provides a framework for hypothesis-free discovery, structuring "big science," and treating biology as an information science. Reach for this when the user is discussing open science, collaborative ecosystems, CRISPR/gene editing ethics, managing massive datasets, or setting realistic timelines for technological breakthroughs. Apply his principles to avoid the "lone genius" myth, prevent overpromising, and build foundational infrastructure that serves the broader community.

ronniepinnell Skill

`/mvp` — MVP Discovery & Initiative Builder

stephenrogan Skill

Structures a CS career progression plan from current role to target role by mapping required skills, identifying gaps, defining development milestones, and building a timeline with specific actions. Covers the full CS career ladder from CSM through VP. Use when asked to plan a career path, build a development roadmap, map skills for promotion, structure a career progression plan, or when a CSM wants to be intentional about moving to the next level. Also triggers for questions about CS career progression, promotion readiness, skills for the next level, career planning in customer success, or what it takes to move from CSM to manager to director to VP.

stephenrogan Skill

Assesses renewal risk for a specific account by scoring across multiple dimensions including health, engagement, value evidence, stakeholder coverage, competitive signals, and commercial factors. Produces a risk classification with the primary risk driver and recommended intervention. Use when asked to assess renewal risk, evaluate whether a renewal is safe, score an account's likelihood of renewing, prepare for a renewal pipeline review, or when a CSM needs an objective assessment of whether a renewal is at risk. Also triggers for questions about renewal likelihood, churn risk assessment, retention risk scoring, or predicting whether a customer will renew.

stephenrogan Skill

Creates a structured customer onboarding plan with phased milestones, success criteria, timeline, and responsibility assignments. Adapts by segment and complexity. Use when asked to build an onboarding plan, structure a customer kickoff, create an implementation timeline, design a go-live plan, or when a new customer needs a clear roadmap from contract signing to value realisation. Also triggers for questions about customer onboarding structure, implementation planning, kickoff preparation, time-to-value planning, or how to set up a new customer for success from day one.

stephenrogan Skill

Builds a structured map of customer stakeholders with roles, influence levels, engagement status, and relationship strategy per contact. Identifies coverage gaps and single-thread risk. Use when asked to map stakeholders, build an org chart, assess relationship coverage, identify single-thread risk, plan stakeholder engagement, or when a CSM needs to understand who matters at an account and where the relationship gaps are. Also triggers for questions about stakeholder mapping, contact assessment, org chart analysis, relationship coverage, multi-threading assessment, or who to engage at a customer account.

stephenrogan Skill

Develops a structured 90-day strategic plan for a key account by defining priorities, setting measurable objectives, mapping stakeholder strategy, and identifying risks and opportunities. Use when asked to build an account strategy, create an account plan, develop a strategic approach for a key account, set quarterly objectives for an account, or when moving from reactive account management to proactive strategic management. Also triggers for questions about account planning, strategic account management, quarterly account objectives, or how to develop a structured plan for a high-value customer.

stephenrogan Skill

Provides a structured approach to expanding relationships beyond a single contact at a customer account. Identifies target contacts, recommends engagement approaches, and builds a multi-threading strategy to reduce single-thread risk. Use when asked to multi-thread an account, expand relationships at a customer, reduce single-thread risk, build broader stakeholder coverage, develop new contacts, or when a CSM realises they are dependent on one person at a key account. Also triggers for questions about relationship breadth, single-thread risk, stakeholder expansion, going wide at an account, or how to build relationships with people beyond the primary contact.

stephenrogan Skill

Provides a structured framework for helping customers drive internal adoption of your product within their organisation. Addresses resistance, stakeholder alignment, communication strategy, and phased rollout planning from the CSM's perspective as an external advisor. Use when asked to help a customer with change management, advise on internal adoption strategy, address resistance to product adoption, plan a team rollout, or when adoption is stalling not because of the product but because of the customer's organisational readiness. Also triggers for questions about customer change resistance, internal adoption blockers, rollout planning, or how to help customers get their teams to actually use the product.

stephenrogan Skill

Prepares structured background research on a customer contact before a first meeting or engagement. Builds a profile including likely priorities, role-specific concerns, engagement approach, and conversation starters based on their title, function, and seniority level. Use when asked to prepare for a first meeting with a new contact, research a stakeholder, build a contact profile, prepare for an executive conversation, or when meeting someone at a customer account for the first time. Also triggers for questions about stakeholder preparation, first meeting research, contact profiling, or executive meeting prep with someone you have not met before.

stephenrogan Skill

Writes the initial outreach email to a senior stakeholder the CSM has not engaged before -- going high for the first time. Calibrates register, framing, and approach to executive communication standards. Use when asked to write an email to a VP, CRO, CFO, or C-suite contact at a customer account, draft an executive outreach, compose a going-high email, engage a new senior stakeholder, or when the CSM needs to establish a relationship at a level above their primary contacts. Also triggers for questions about executive email drafting, going high strategy, senior stakeholder engagement, or first-time executive outreach.

stephenrogan Skill

Scores expansion readiness for a customer account by assessing adoption depth, value realisation, stakeholder alignment, commercial signals, and timing. Produces a readiness classification with the recommended expansion approach and the specific signal that triggered the assessment. Use when asked to assess expansion potential, evaluate upsell readiness, score an account for growth, determine whether a customer is ready for a commercial conversation about expansion, or when a CSM detects expansion signals and needs to decide whether and how to pursue them. Also triggers for questions about expansion timing, upsell assessment, growth readiness, when to start an expansion conversation, or evaluating whether a customer is ready to buy more.

reggiechan74 Bundle

Use when summarizing stakeholder feedback from public meetings, open houses, or Indigenous consultations, categorizing themes and running sentiment analysis (support/opposition/neutral/mixed), generating prioritized response strategies, tracking commitments made during consultation, or preparing briefing notes on consultation outcomes.

rweisssieker-xp Skill

Build a database improvement roadmap from objectives, evidence, and operational constraints.

rweisssieker-xp Skill

Prioritize missing evidence and follow-up experiments from database advisor feedback.

zts212653 Skill

Feature 立项、讨论、完成的全生命周期管理。 Use when: 开个新功能、new feature、F0xx、立项、feature 完成、验收通过、讨论新功能需求，或operator说“先看真页面”要求恢复既有 F083 Design Gate。 Not for: 不涉及 Feature/Design Gate 真相更新的纯代码实现、review、merge（那些有专门的 skill）。 Output: Feature 聚合文件 + BACKLOG 索引 + 真相源同步。

zts212653 Skill

约定图发现方法论：进一个 repo 先识别 repo-specific conventions，再定义 domain/extractor 接 Convention Graph 引擎。Use when: 进入陌生 repo、要画约定图、要找“改 X 影响谁”的约定层关联、 F242/Convention Graph Layer 工作。Not for: 普通符号跳转/LSP、文档索引检索、记忆图谱、直接使用 codegraph/GitNexus。Output: domain 定义 + extractor 计划 + gap/freshness/provenance 报告。 GOTCHA: 沉淀的是“怎么画图”的方法，不是把 cat-cafe 的 extractor 硬搬到所有 repo。

anastasiyaw Skill

Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or chat-only summaries.

anastasiyaw Bundle

Turn captured user-correction signals into durable rules (learn-from-corrections loop). Use when - /distill-feedback, "process feedback queue", "what corrections did I give you", "encode lessons from my corrections", session-feedback-capture queued sessions, "обнови правила по моим поправкам", "разбери очередь обратной связи". Reads ~/.claude/feedback/queue.jsonl, LLM-semantically detects durable corrections, proposes atomic rules, applies human-gated via delta-merge. Do NOT use to act on a single in-session correction (just apply the fix directly) or to hand-edit settings.json behaviors; this only mines the queued feedback backlog into durable rules.

anastasiyaw Bundle

Discover, search, and selectively restore Claude desktop app sessions hidden across multiple accountIds. Use when user mentions "missing sessions after account switch", "lost desktop sessions", "where do my old sessions live", or runs multiple Claude accounts on the same machine. Do NOT use for Claude Code CLI session history or resuming work within one session — this only recovers the native desktop app's per-accountId session files; for in-session continuity use handoffs.

uxcel-lab Skill

Run a structured quality audit on a product spec, PRD, or requirements document. Produces a severity-rated issue list with concrete fixes — catches untestable requirements, happy-path-only flows, missing scope exclusions, absent dependencies/constraints/assumptions, implementation details leaking into functional specs, and unvalidated assumptions presented as facts. Use when reviewing a spec, PRD, or requirements doc, or as the validation step after writing one.

uxcel-lab Skill

Plan or critique a product discovery process — figuring out what to build before building it. Establishes which risk you're de-risking and how much certainty the decision needs, applies the always-true core (continuous not phased, outcomes over output, problem before solution, ask about past behavior, match evidence to risk, generate solutions from validated problems, research ethically) and gates the context-dependent decisions (problem vs. solution research, qual vs. quant, lightweight vs. deep, how much certainty before committing). Trigger when asked to plan discovery, "figure out what to build," set up continuous discovery, design a research plan, do customer/user research, find problems worth solving, or de-risk a product direction before committing.

uxcel-lab Skill

Create or critique a product roadmap — outcome-oriented, theme-based, confidence-aware (Now-Next-Later) roadmaps tied to strategy, instead of dated feature lists. Gates format and detail by audience and planning horizon. Trigger when the user asks to build, write, review, or restructure a product roadmap, quarterly/annual plan, Now-Next-Later view, or roadmap presentation.

uxcel-lab Skill

Orchestrated, idea-to-plan PM workflow. Establishes context once, then composes the PM generative ladder in order — problem → discovery → users → riskiest-assumption test → prioritization → spec → metrics — gating each step, enforcing evidence before the spec, and handing the result to product-review. Trigger when the user wants to go from a raw idea to a build-ready plan ("take me from problem to plan", "I have an app idea, where do I start", "turn this idea into a product plan", "plan a new product end to end") — but NOT when they ask for one specific PM artifact (let that skill trigger directly), and NOT for the strategy/launch arc (vision, competitive analysis, roadmap, GTM — offer those next).

uxcel-lab Skill

Run a structured rigor audit on how a team validated (or plans to validate) its assumptions — for a discovery plan, experiment, test, or any "we validated it" claim. Produces a severity-rated issue list with concrete fixes — catches testing the comfortable assumption instead of the riskiest, untestable phrasing, method fidelity mismatched to decision risk, stated intent mistaken for behavior, success criteria set after the fact, goalpost-moving, and underpowered evidence. Use when reviewing a validation/discovery approach or as the validation step after generating an assumption-test plan.

uxcel-lab Skill

Decide what to build first, or critique a prioritization. Derives criteria from strategy, picks the right framework for the context (RICE/ICE/MoSCoW/Kano/Impact-Effort), scores to expose trade-offs rather than manufacture false precision, sequences for flow, and says no with strategic context. Applies the always-true core and gates context-dependent decisions (which framework, scoring rigor, roadmap horizon, appetite vs. estimate, bets vs. tactical) with trade-offs. Trigger when asked to prioritize features/backlog, rank or sequence work, choose a prioritization framework, decide what to build first or what to cut, run a RICE/ICE/MoSCoW/Kano exercise, or defend a prioritization decision.

uxcel-lab Skill

Orchestrated review of a PM artifact (spec, PRD, OKRs, roadmap, prioritization, strategy). Routes by artifact type to the right audits, auto-runs the always-relevant assumption check, and returns one prioritized report. Trigger when the user asks for a full review of a PM document, "review my spec/roadmap/OKRs", "is this PRD solid", or general PM feedback — but NOT when they name a single specific audit.

uxcel-lab Skill

Write a product requirements document (PRD) or spec anchored to a validated problem, with measurable requirements and surfaced risks — or review an existing one. Trigger when asked to write a PRD, product spec, user stories, technical requirements, or to review/critique an existing spec document.

uxcel-lab Skill

Run a structured validity audit on OKRs, KPIs, North Star Metrics, or any success-metric set. Produces a severity-rated issue list with concrete fixes — catches vanity metrics, unfalsifiable key results, outputs disguised as outcomes, gameable targets without guardrails, and metrics disconnected from business value. Use when reviewing OKRs, goals, KPIs, dashboards, or success metrics, or as a validation step after defining metrics in a spec, roadmap, or strategy doc.

uxcel-lab Skill

Run a structured rigor audit on prioritization decisions, scored backlogs, RICE/ICE/MoSCoW outputs, or roadmap orderings. Produces a severity-rated issue list with concrete fixes — catches invented scores with false precision, priorities unmoored from strategy, feature-factory ordering, everything-is-a-must-have inflation, and trade-offs left implicit. Use when reviewing a prioritized backlog, scoring exercise, roadmap order, or "what should we build first" decision, or as a validation step after any prioritization work.

uxcel-lab Skill

Produce or critique a product vision and/or product strategy — an aspirational destination and the deliberate, trade-off-driven choices to reach it — not a buzzword poster or a feature list. Distinguishes the vision/strategy/roadmap/mission artifacts, ladders product vision up to company vision, forces a focused segment + differentiation + explicit "won't do", and sets the stability rule (stubborn on vision, flexible on strategy). Applies the always-true core and gates context-dependent decisions (which strategy framework, vision communication format, single vs. multi-product, B2B vs. B2C, new vs. existing, depth). Trigger when asked to write/define/critique a product vision, vision statement, product strategy, strategic themes, positioning/where-to-play/how-to-win, or to tell vision from strategy from roadmap.