Product & Planning

mqmalagris Bundle

Turn the current conversation context into a PRD and publish it to GitHub Issues, also persisting it to docs/prds/NNNN-<slug>.md for downstream skills (heist, maestro). Use when user wants to create a PRD from the current context. Triggers on /to-prd, "write a PRD", "draft a PRD", "spec this out", "feature spec", or after /grill-me when scope and Glossary are settled.

mqmalagris Bundle

Route a dev task through the right subset of the canonical skill chain (adhd → grill-me → to-prd → compass → heist → maestro → code → review-pass → pr-craft), matching ceremony to stakes. Detects the task tier (bug / feature / architecture / client), shows the exact chain it will run and what it skips, confirms, then drives the sub-skills in order — pausing where each needs user input. Use when the user says "start a feature", "new feature", "kickoff", "route this through the workflow", "run the chain", "which skills for this", or /dev-flow. NOT for tasks already mid-chain (a PRD/plan exists) — invoke the specific next skill instead.

mqmalagris Bundle

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree, then emitting a Design Notes + Glossary + edge-case block and persisting it to docs/intent/NNNN-<slug>.md for handoff to /to-prd. Use when user wants to stress-test a plan, get grilled on their design, do a pre-PRD design review, challenge an idea before writing it up, or mentions "grill me" or runs /grill-me.

mqmalagris Bundle

Apply Marty Cagan product principles (Inspired, Empowered, Transformed) plus Teresa Torres' Continuous Discovery to a software dev's workflow from the Product Trio's engineering seat. Runs structured reviews for feature kickoff, sprint planning/estimation, client discovery calls, and pull requests — checking problem framing, outcome metrics, the five big risks (value/usability/feasibility/viability/ethical), feature-factory smells (incl. Cutler 2025 updates: high WIP, Team Tetris, success theater), prototyping fit, instrumentation, customer touchpoint cadence. Outputs green/yellow/red flags per dimension with concrete next actions. Use when user says /cagan-check, "starting a feature", "vou começar feature", "kickoff", "planning", "estimativa", "estimation", "discovery", "review this PR" with feature context, or asks to apply Cagan/SVPG/Torres/product-trio thinking. Adapts to the reader's employment context — in-house product team, or client-services work (agency, consultancy, contractor) where a paying stake

ninehills Skill

将当前对话上下文转化为 PRD 并发布到项目 issue 跟踪器。当用户想从当前上下文创建 PRD 时使用。 (Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.)

ninehills Skill

从一个固定点（提交、分支、标签或 merge-base）沿两个轴审查变更 —— 标准（代码是否遵循本仓库记录的编码规范？）和规格（代码是否符合原始 issue/PRD 的要求？）。以并行子 agent 运行两个审查并并排报告。当用户想要审查分支、PR、进行中的工作变更或要求"review since X"时使用。 (Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".)

ninehills Skill

使用曳光弹垂直切片将计划、规格或 PRD 拆分为项目 issue 跟踪器上可独立认领的 issue。当用户想将计划转换为 issue、创建实现工单、或将工作拆分为 issue 时使用。 (Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.)

ninehills Bundle

在 AGENTS.md/CLAUDE.md 中设置 `## Agent skills` 块和 `docs/agents/`，以便工程技能了解此仓库的 issue 跟踪器（GitHub 或本地 markdown）、分诊标签词汇和领域文档布局。在首次使用 `to-issues`、`to-prd`、`triage`、`diagnose`、`tdd`、`improve-codebase-architecture` 或 `zoom-out` 之前运行——或当这些技能似乎缺少关于 issue 跟踪器、分诊标签或领域文档的上下文时运行。 (Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.)

october-academy Bundle

Signal-Driven Navigator for indie hackers. Guides users through problem discovery, customer interviews, spec writing, and tool comparison to reach their first paid signal in 30 days. Use when the user asks to start, discover problems, interview customers, write specs, compare tools, or check progress.

orangehrm Skill

Framework-level reference for how OrangeHRM wires up Doctrine ORM 2.20 — the single EntityManager singleton, multi-path entity discovery driven by `ohrm_plugin_paths`, the multi-path `OrangeHRM\Entity\` PSR-4 namespace in `src/composer.json`, the dev/prod cache split (`ArrayAdapter` vs `FilesystemAdapter`), proxy auto-generation strategy, the `enum`-to-`string` platform mapping, registering custom DQL functions like `TIME_DIFF`, and how to access the EntityManager from your code. Use whenever the user is adding a new plugin and needs to register its entity dir, debugging "class not found" / unmapped-entity errors, wondering why Doctrine still uses annotations instead of PHP 8 attributes, configuring cache behavior, regenerating proxies after deployment, or adding a custom DQL function. Companion to the `entities` skill (defining entities) and `daos` skill (querying them).

preset-io Bundle

Use Superset MCP health, instance, list, detail, schema, and chart-type discovery tools. Use only for MCP tool workflows; do not use for direct API work.

preset-io Bundle

Use Superset MCP tools for Explore links, chart configuration discovery, chart previews, saved charts, and chart updates. Use only for MCP tool workflows; do not use for direct API work.

onekeyhq Bundle

OneKey Browser/Discovery development for WebView tabs, bookmarks, history, search, URL risk checks, DApp connections, and JSBridge behavior.

cloudchef Skill

Prometheus monitoring and alerting for cloud-native observability. Use when implementing metrics collection, PromQL queries, alerting rules, service discovery, recording rules, and scrape config.

cloudchef Bundle

Read-only discovery skill. Browse SmartCMP reference data such as service catalogs, business groups, tenant and project scopes, applications, OS templates, images, and generic resource details. Request, apply, create VM, or provisioning intent belongs to the request skill, whose request-projected aliases reuse the same logical-template and image scripts.

cristhianzl Bundle

Author product requirements — PRDs, product specs, one-pagers, PR-FAQs, product briefs — that lead with the problem, define testable success metrics and acceptance criteria, and make non-goals explicit. Use when the user asks to write a PRD, write/define product requirements, write a product spec, write a one-pager, write a PR-FAQ, "write a spec", "define requirements", scope a feature, or draft a product brief. Also use when the request is a half-baked feature idea that needs a problem framed before any solution. Not for engineering design docs / the technical "how" — that is a separate design doc (the PRD owns the what/why, the design doc owns the how).

gszyboy Bundle

Convert Markdown documents (PRD, proposals, reports) into polished PPT presentations and professional PDF proposals. Triggers when user wants to create a presentation from a document, generate PPT+PDF from PRD, or produce a client-ready proposal from Markdown source. Works with any Markdown containing headers, tables, lists, and code blocks.

gszyboy Bundle

Use when automating Chinese social platforms: Douyin (search, video playback, download), WeChat public account article scraping, Xiaohongshu/Weibo content discovery, and bypassing login walls via search-engine indexing. Trigger on 抖音 / Douyin / 微信公众号 / 微信文章 / 小红书 / Xiaohongshu / 微博 / 社交平台 / social platform. For the browser layer, use CloakBrowser via the cloakbrowser-stealth-automation skill when anti-bot is needed.

rahmanef63 Skill

SI-Coder skill discovery and installation workflow. Search installed Agent Skills by keyword, inspect matching slash skills, create a new managed skill, or install a complete skill bundle with scripts/references/assets using sc-skill. Use when the user asks to find a skill for UI, UX, deployment, email, database, automation, or another capability; asks to install/add/create a skill; or invokes /sc-skill --new.

gdm257 Skill

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

involvex Bundle

Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

alsk1992 Bundle

Pump.fun - Complete Solana memecoin launchpad. Discovery, trending, gainers, losers, token data all work without a key. Trading requires SOLANA_PRIVATE_KEY.

pangkaifeng Bundle

方案拷问 / 压力测试：当用户有一个产品方案、架构设计、计划或决策，想被连续追问、反方挑战、 压测取舍和失败模式时使用。可用中文唤起：“拷问我的方案”“压力测试这个设计”“帮我问 hard questions” “这个方案哪里会翻车”“grill me”。目标是一问一答把决策树走清楚，不是直接替用户写最终方案。 跨 Skill 运行时只输出 Challenge/Critic Handoff，并把一个 gap 返回最小责任节点；不重写完整方案。 如果用户还不知道真正问题是什么，先用 ai-collaboration-calibration；如果用户要标准 PRD 交付准备度评审， 用 prd-review。

pangkaifeng Bundle

PRD 评审 / 需求评审：当用户已有 PRD 初稿、handoff、需求文档或产品方案，需要从 PM、研发、测试视角找缺口、 冲突、不可实现点和不可测试点时使用。可用中文唤起：“帮我审 PRD”“从研发和测试视角挑问题” “这个需求文档能不能交付开发”“帮我给 PRD 出修改草案”“检查 PRD 图示是否缺失或不可编辑”。 不用于凭空生成 PRD 初稿、直接写代码，或对 PRD 背后的成熟方案做一问一答压力测试；方案压测用 grill-me。

pangkaifeng Bundle

交付闭环：当用户显式调用 `$delivery-loop`，或明确要求进入“交付闭环”时使用。 面向已有 PRD、UI/HTML、截图或 Product Delivery Package 但仍有 Review 缺口的场景，在独立评审与定点修订之间最多循环三轮，直到 package_ready 或进入 Human Gate；不用于从模糊问题开始。

pangkaifeng Bundle

设计脑暴 / 实现前方案校准：当用户想把已基本成立的想法、功能方向或产品问题，在写 PRD、画 mockup 或进入开发计划前，先比较方案、确认取舍、对齐 UI/视觉约束，并收敛成可执行设计 spec 时使用。 可用中文唤起：“先脑暴一下方案”“先不要写 PRD，帮我设计几种路径”“参考 brainstorming 把这个需求变成设计 spec” “实现前先讨论设计”。问题还没定义清楚时先用 ai-collaboration-calibration；已有方案要压力测试时用 grill-me； 直接写 PRD 时用 prd-architect；grill-me 返回精确设计 gap 时，本 Skill 只输出 Design Delta。

pangkaifeng Bundle

PRD 架构师 / 需求文档起草：当用户要把一个产品想法、需求草稿、脑暴结果或功能说明整理成 PRD 时使用。 可用中文唤起：“帮我写 PRD”“帮我选 PRD 模板”“把这个需求整理成 PRD”“判断该用轻量 PRD 还是标准 PRD” “补一张可编辑 Draw.io 核心流程图”“PRD 里加架构图”。 会在 PRD-lite、PRD-standard、PRD-ai-native 中选择一个模板资产按需加载，并在需要时加载 mockup handoff、 Draw.io 图示或开发 handoff 附录；页面型 PRD 默认联动生成项目 UI 对齐的 HTML、关键截图和正文证据。 不用于直接编码、单纯画 UI，或评审一份已经写好的 PRD。

pangkaifeng Bundle

PRD 到研发 Issue 拆解 / implementation issues：当用户已有 PRD、需求文档、handoff、产品方案或 GitHub PRD issue， 需要拆成可独立领取、可验收、适合 GitHub Issues 承接的开发任务时使用。可用中文唤起： “把 PRD 拆成 issue”“需求文档拆任务”“生成 GitHub issues”“PRD 拆工单”“拆 implementation issues” “按 vertical slice 拆开发票”。不用于从零写 PRD；那类请求用 prd-architect。不用于评审 PRD 是否完整； 那类请求先用 prd-review。

pangkaifeng Bundle

决策调研 / Decision-Driven Research：当用户面对一个具体决策需要找信息时使用——「有没有现成方案」 「怎么接入 X 平台」「这个技术可行吗」「业界怎么做 Y」「选 A 还是 B」「桌面端应该怎么定位」 「高级版和基础版怎么拉开差异」「这个产品方向对不对」。 核心行为：先框定研究层级和问题类型，再锚定决策问题，枚举竞争假设，主动找反对证据， 用排除逻辑给出有立场的结论。支持技术选型、产品策略、商业判断、竞品定位等所有需要做决定的调研。 可用中文唤起：「帮我调研」「有没有现成方案」「这个怎么接」「技术上可行吗」「帮我选一个」 「这个产品方向对不对」「我们应该怎么定位」「行业怎么做」。 与 research-topic-compiler 的边界：需要最终选择、推荐、排除理由、置信度和颠覆条件时用这个； 如果目标是长期学习、候选池沉淀或 Research Project，用 research-topic-compiler，再把 Candidate Backlog 交回本 Skill 做最终决策。 只有发现一个会实质改变结论、可研究且可关闭的证据 gap 时，才向 research-topic-compiler 发出精确 Return Request。 不用于：问题还没定义清楚时（先用 ai-collaboration-calibration L4-fuzzy 脑暴）。

pangkaifeng Bundle

问题到方案 Workflow：当用户显式调用 `$problem-to-solution`，或明确要求运行“问题到方案”完整流程时使用。 把模糊产品问题经过校准、必要的研究/决策、方案生成和挑战，推进为一个可进入 PRD 的已确认方案；不负责 PRD 交付或外部发布。

pangkaifeng Bundle

Use when / 当用户进入一个新项目或跨仓库工作区，需要扫描产品、用户、业务工作流、技术架构、仓库边界、领域语言、阅读入口和历史踩坑，并生成或持续维护全局 PROJECT_CONTEXT.md。适合用户说“先完整看下项目并沉淀上下文”“给这个项目建上下文文档”“把这次踩坑更新到项目上下文”。不用于单个 PRD 起草、纯目录治理或一次性代码实现。

pangkaifeng Bundle

Product Research / 产品研究编译器：当用户要围绕一个产品问题做系统调研、竞品证据、替代方案、行业信号、 用户与市场研究、最佳实践提炼、产品候选池、本地 HTML 研究看板、可视化研究报告或跨职能 Dashboard 时使用。 当用户只有大白话、模糊方向、业务愿望或 Roadmap/PRD 前置材料想法，需要先转成清晰研究目标、研究问题和输出要求时也使用。 适合把研究转成 Research Project、学习报告、证据矩阵、PM 决策看板、候选池、模板、实践任务、业务判断、商业化输入或高门槛应用研究前置。适合“系统研究一个主题” “整理到 Obsidian”“做深度专题”“研究行业最佳实践”“概念解读”“概念源流”“PM 技术评审提问脚本” “行业演进看板”“这个主题对我的产品决策有什么用”“让我系统学会并输出 learning report HTML”。不适合创建 Skill、评审 SKILL.md、普通即时搜索或一次性摘要。 当用户已经要在明确候选项中选一个、需要最终推荐和排除理由时，应使用 decision-research。 当 decision-research 或 grill-me 返回一个可研究、可关闭的精确证据 gap 时，也使用本 Skill 只补 Evidence Delta。

pangkaifeng Bundle

方案到交付 Workflow：当用户显式调用 `$solution-to-delivery`，或明确要求运行“方案到交付”完整流程时使用。 把已确认产品方案转成经过独立 Review 的 PRD、适用的 UI/HTML/截图、版本拆分和 Product Delivery Package；当前 Agent Runtime 只做 Package 发布 dry-run，真实写入保持 authorization_required。

pangkaifeng Bundle

复杂探索资产化 / Complex Exploration：当用户面对复杂、不确定、多轮迭代的产品策略、Roadmap、商业化定价、竞品定位、复杂 PRD 前置探索、项目复盘或方法论沉淀任务时使用。它先判断任务类型，暴露隐含假设，重构真正问题，规划探索路径和中间产物，并在结束后沉淀认知、结构、方法论、工具和影响力资产。不用于简单润色、翻译、摘要、明确执行任务；问题只需早期认知校准时优先用 ai-collaboration-calibration，已有方案要压力测试时用 grill-me，系统专题研究用 research-topic-compiler。

pangkaifeng Bundle

PRD 到高保真 UI 交付对齐 / 桌面工作台 UI mockup：当用户已有 PRD、UI 规范、真实前端项目路径、截图或页面状态清单， 需要先从 PRD 提炼 UI 结构、状态模型和 ASCII 布局，再进入高保真 mockup、项目原生 preview 或开发交付 handoff 时使用。 优先输出项目原生 preview route/component；只有早期概念确认或无法接入真实项目时才输出 standalone HTML。 必须包含结构阶段产物、screen contract、component map、implementation notes、截图/验证结果和 HTML/preview 的迁移边界。

pangkaifeng Bundle

竞品决策分析 / Competitive Decision Brief：当用户要调研竞品、替代方案、新产品、SaaS/AI 产品或市场信号， 并希望把官网、定价、评论、文档、更新日志、登录态走查、截图或浏览器取证转成产品定位、路线图、定价、 功能优先级、差异化、Go/No-Go 或 PRD 输入时使用。核心行为是先锚定产品决策，再选择证据渠道， 最后输出可行动的 Product Decision Brief；不要把它降级成泛泛功能清单、纯 UX 走查或“点完所有按钮”报告。