Product & Planning

meleantonio Bundle

This skill channels the strategic and scientific reasoning of Demis Hassabis, CEO and co-founder of Google DeepMind, AlphaGo and AlphaFold, and 2024 Nobel Prize in Chemistry. Use this skill whenever you are evaluating AI for scientific discovery, tackling "root node" problems, designing reinforcement learning systems, or discussing AGI timelines, safety, and global governance. Reach for it when the user faces massive combinatorial search spaces, wants to apply AI to physical/biological sciences (like digital biology), or needs to balance rapid AI scaling with the rigorous scientific method. Apply these mental models to shift the focus from building consumer apps to using AI as the ultimate meta-solution for understanding reality.

okwinds Bundle

Write comprehensive PRDs for AI Agent products—covering agent identity, capability architecture (skills, tools, memory, RAG, workflows), behavior specifications, safety guardrails, and evaluation frameworks. Use when: designing conversational agents, autonomous agents, copilots, multi-agent systems, or any LLM-powered agentic application. Triggers: 'AI agent PRD', 'agent product requirements', 'design AI agent', 'agent capability spec', 'LLM agent requirements', '智能体PRD', '智能体需求文档', '对话机器人PRD', '多智能体系统需求'. Anti-triggers: '传统PRD（非智能体）', '只润色提示词/只写Prompt', '只写用户故事/验收标准但不涉及工具调用、记忆或RAG'.

xiongxianzhu Bundle

根据用户提问生成专业规范的产品需求文档（PRD）。在用户要求创建 PRD、撰写需求文档、起草产品需求或记录项目需求时使用。

xiongxianzhu Bundle

策划、开发或修改 Cocos Creator 3.8+ 的 2D 微信与抖音小游戏。按请求处理玩法、PRD、广告接入或具体开发任务；仅在用户要求完整新项目时推进全流程。

zhuqingxun Skill

一键启动全自主 agent 团队，自动完成从 PRD 到验证的完整 RPIV 开发流程。brainstorm 完成后使用此命令，无需人工介入。当用户提到"自动开发"、"团队开发"、"全自主"、"biubiubiu"时触发。

zhuqingxun Skill

基于对话上下文创建产品需求文档

lftpadilla Bundle

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

azuread Skill

Create Azure DevOps work items from a feature plan produced by the `feature-planner` skill. Handles ADO metadata discovery (area path, iteration, assignee), work item creation, and dependency linking. Use this skill when PBIs have been planned and approved, and you need to create them in ADO. Triggers include "create the PBIs", "create work items", "push PBIs to ADO", or approval of a feature plan.

1mancompany Skill

Project Brainstorming — Requirements Discovery Before Execution

atman-33 Skill

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

atman-33 Skill

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

b1rdmania Bundle

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

wrm3 Bundle

Create and manage project plans, PRDs, and feature documentation in .fstrent_spec_tasks/ folder. Use when planning projects, creating requirements documents, defining features, conducting scope validation, or gathering requirements. Triggers on requests mentioning plan, PRD, requirements, features, scope, or project planning. ENFORCES feature file creation for multi-task features (see FEATURE_GUIDELINES.md).

daviddwlee84 Bundle

Set up a structured project memory for any software project — TODO.md as priority/effort-tagged index of future work, backlog/ for resume-friendly research/design notes on P? items, and pitfalls/ as a symptom-grep-able knowledge base of past traps. Use when a user wants somewhere to record "maybe later" ideas, freeze troubleshooting state, capture trade-off analysis, or stop re-debugging the same problem.

daviddwlee84 Bundle

Set up and operate a research-experiment memory for ML/DL/Quant projects — LEDGER.md of numbered findings (what we believe, evidence links, overturn protocol), ROADMAP.md experiment queue triaged by expected payoff × cost × category × assumption dependencies, INBOX.md human scratchpad swept into the roadmap via targeted questions, an auto-rendered Mermaid map of how experiments/findings/queued work reference each other, and per-experiment REPORT.md with pre-registration, single-axis ablation contract, results tables and provenance blocks (git SHA, config hash, data window, seeds, MLflow refs). Use when the user wants to track which directions were explored vs not, record which succeeded or failed, avoid re-running dead-end experiments or wasting compute, make results discoverable and comparable, keep experiments reproducible, re-prioritize planned work when a conclusion changes, get a big-picture map of all experiments, jot a raw research idea somewhere, or asks to sweep the experiments inbox.

goodsmileduck Bundle

Operates Cloudflare DNS zones and records via the REST API (curl + jq) — token scoping, zone discovery, record CRUD, batch operations, BIND import/export, proxied vs DNS-only decisions, CNAME flattening at apex, DNSSEC, and DNS-01 ACME challenge wiring with cert-manager. Use when working with Cloudflare DNS, `api.cloudflare.com`, `CLOUDFLARE_API_TOKEN` (or legacy `CF_API_TOKEN`), zone records, DNS-01 challenges, mail records (MX/SPF/DKIM/DMARC), or "orange cloud / grey cloud" proxy decisions.

impertio-studio Bundle

Use when calling OCS endpoints, creating OCS controllers, handling OCS responses, or implementing share operations. Prevents v1/v2 status code confusion, missing OCS-APIRequest header, and incorrect response envelope parsing. Covers OCS REST API endpoint structure, v1 vs v2 versioning, authentication methods, response envelope format, capabilities discovery, user provisioning, share API endpoints, and user status API. Keywords: OCS, OCSController, /ocs/v2.php, OCS-APIRequest, capabilities, share API, user provisioning, REST API, OCS endpoint, share API, user provisioning, capabilities, external client..

juankcadavid Skill

Trigger: kaizen, retrospective, continuous improvement, mejora continua, /akili-archive Kaizen step, apply pending kaizen standardizations, kaizen apply, aplicar estandarizaciones kaizen. Run the bounded two-phase Kaizen loop: Measure → Learn → Standardize → Record on any branch, then apply the pending backlog on the default branch.

juankcadavid Bundle

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development. In AKILI-SPECS projects, follow the AKILI-SPECS Integration section first.

askairo Bundle

Maintain a project's architecture-planning loop through ordered external docs. Use when Codex needs to clarify project goals, boundaries, roadmap, focus docs, decisions, open questions, risks, plans, and task readiness before `p-task`, or when implementation/user feedback should update project state and guide the next planning cycle.

beclab Skill

Manage Home Assistant integrations (config entries) and device discovery with hass-cli: list integrations and their state, reload, enable/disable, delete, update entry options, and inspect discovered/in-progress config flows. Use for 'list my integrations', 'reload the X integration', 'why is this integration failing', 'disable this entry', 'what was discovered on my network' requests.

cabbage2000-lab Bundle

Paper 分段正文共写命令（段落正文初稿共写器）。当用户已有论文大纲（/paper-outline 产物或手写大纲）、要逐段展开正文、起草段落、写论文正文、把大纲要点展开成段，或说"帮我把这段引言写一下""这段正文怎么展开""基于大纲写一段方法""我有大纲了、想写正文"时使用——即使用户只说"帮我想想这段怎么写""这一段写不下去"也应使用。行为铁律：基于大纲要点与 literature/ 文献笔记起草段落初稿、每段尽量挂真实存在的锚点（无文献支撑标「⚠️ 未经文献支撑」、绝不编数据）；段落取舍（接受/改写/自写/删）由用户逐段拍板；模仿用户已有的风格样本（只学风格不抄内容）；确认前零落盘；产物如实披露"成句生成"级辅助（PRD 披露第三级）。不替用户一次性写整章/整篇、不编数据/结果、不抄用户过往论文内容。"直接帮我把整章写完别问""帮我编点数据凑结论"走三段式转化或硬拒绝。

cabbage2000-lab Bundle

Paper 投稿准备命令（投稿材料清单整理器 + 期刊常见投稿要求陈列）。当用户论文写完要投稿、要准备投稿材料、要写 cover letter、要整理投稿 checklist、要查期刊投稿要求、要准备投稿文件包、或说"帮我准备投稿""投稿要交什么""这个期刊要什么材料""投稿清单怎么列""cover letter 怎么写"时使用——即使用户只说"要投稿了""投稿准备""submit 一下""整理投稿材料"也应使用。行为铁律：陈列目标期刊常见投稿要求类目（不替用户选刊、不下"好投/难投/值得投"价值判断）、整理投稿材料 checklist 草案（cover letter 要点骨架、文件清单、格式提示；不替用户写 cover letter 整段正文、归 /paper-draft）、期刊信息不编造（不编影响因子、不编投稿系统截图、不编模板；只陈列"该类期刊官网常见要求类目"）、不做查重降重（指路学校/知网正规渠道）、不做期刊格式模板库（PRD §448 明确不做）、不替用户实际点"Submit"按钮。投稿决策（投哪个期刊、是否上预印本、是否撤稿、出版伦理判断）全部归人。两路输入：用户粘贴目标期刊投稿要求 + 用户已有研究产物（draft 正文、verify/review/revise 产物、disclose AI 使用说明）；确认前零落盘。"帮我替选个期刊""帮我编个影响因子""帮我整段 cover letter 写完""帮我做查重降重"走硬拒绝或让路。

cabbage2000-lab Bundle

Paper 出版链命令（Markdown → LaTeX / DOCX / PDF 转换管线 + GB/T 7714-2015 国标著录）。当用户要把正文转成 Word 投稿、要生成 .tex、要出 PDF、要参考文献按国标格式渲染，或说"投稿要 Word 版""帮我转成 LaTeX""参考文献要国标格式""导出 docx""这个 md 怎么变成能投的稿"时使用——即使用户只说"转个格式""出个 PDF"也应使用。行为铁律：只换容器、绝不改一个字（不"顺手润色"）；转换后对 .tex 做正文汉字序列逐字比对，.docx/.pdf 是二进制、**明说无法字符级校验**、只校验源文件 md5 未变，绝不谎称校验过；环境缺失（pandoc/xelatex/中文字体）一律输出「未生成什么·原因·安装指引·可手工执行的完整命令」四件套，**绝不假装成功、绝不用模型生成一个"看起来像"的产物**；CSL 路径写错报错而非静默跳过（跳过等于产出非国标著录）。不做期刊/高校排版模板库（PRD §448，指路官网）、不改写正文、不做查重降重、不替用户决定投什么格式。由 /paper-submit 主流程引导进入，亦可独立调用。

cabbage2000-lab Bundle

Paper AI 使用说明生成命令（披露汇编器）。当用户要写论文投稿的 AI 使用说明、AI 使用披露、AI 辅助声明、学位论文 AIGC 使用报告,或说"帮我生成 AI 使用说明""要交一份 AI 披露""答辩材料要附 AI 使用情况""AIGC 检测把我误判了要申诉"时使用——即使用户只说"列一下我用了哪些 AI""整理下 AI 使用记录""要交 AI 使用情况说明"也应使用。行为铁律：只读 .paper/ 真实留痕、按 PRD 四级辅助级别（构思讨论 / 大纲结构 / 成句生成 / 语言润色）汇编成可对外披露的 AI 使用说明,绝不编造未发生的留痕;用户可选择隐去某条但顶部强制覆盖声明、不抹除痕迹;不下「AI 占比 X%」价值判断;段落级读者标签服务导师 / 研究生院 / 期刊 / AIGC 检测四类读者;确认前零落盘。不替用户实际跑命令产生留痕（.paper/ 空则让路）、不编造留痕、不下价值结论。"帮我编一份让 AI 看起来用得少的留痕""帮我改 AI 承担字段"走三段式转化。

carinyadigital Bundle

Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic into stories and tasks with Gherkin acceptance criteria, a story into sub-tasks, or an external spec, RFC, or PRD into both in one pass. Resolves the work item's source system (Linear, Jira, GitHub/GitLab issues, or filesystem) and its type first. Writes docs/product/backlog.md and docs/work/{work-id}/tasks.md, or the tracker directly when one is resolved. Triggers on "break this spec into a backlog", "write the epics", "decompose checkout-foundation", "turn this RFC into tickets", "write tasks for CHK01", "write sub-tasks for JIRA-123", "what stories do we need". EARS with --ears. Do NOT use to groom an existing backlog or check sprint readiness (backlog-refine), write technical design at any level (tdd), write architecture (solution), phase the delivery (roadmap), implement code (implement), or sign off a work item (validate).

carinyadigital Bundle

Use when the user wants a product strategy doc, PRD, pitch, vision, personas, or outcomes at docs/product/product.md. Drafts or re-authors the document. Triggers on "write the PRD", "draft a product pitch", "who are our personas". Re-authoring is also how an existing product.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not strategic soundness. Do NOT use for phased delivery plan (roadmap), epics or backlog (tasks), architecture (solution), tasks or Gherkin (tasks), or implementation (implement).

carinyadigital Bundle

Use when the user wants outcome-based delivery phases or exit criteria at docs/product/roadmap.md. Drafts or re-sequences the document. Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria". Requires product.md. Re-authoring is also how an existing roadmap.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not sequencing soundness. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-work-item technical design (tdd), tasks (tasks), or architecture detail (solution).

carinyadigital Bundle

Use when the user wants to write system architecture at docs/architecture/solution.md (stub or full arc42-lite). Drafts or re-authors the document. Triggers on "write the architecture", "solution design", "arc42". Re-authoring is also how an existing solution.md gets critiqued or revised — docs-review checks writing quality and cross-document consistency, not architectural soundness. Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), work-item tdd.md (tdd), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in docs/work/{work-id}/tasks.md.

carinyadigital Bundle

Use when the user wants final completion sign-off on any work item — epic, story, bug, or spike: every task in docs/work/{work-id}/tasks.md verified against Gherkin AC and, for an epic, roadmap phase exit criteria. Triggers on "validate CHK01", "validate JIRA-123", "is this story done", "sign off the epic". Builds an acceptance matrix with evidence, updates task and work-item status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or the technical design (tdd).

carinyadigital Bundle

Use to groom an existing backlog or judge whether a breakdown is ready to commit to — reprioritise, split oversized epics or stories, re-estimate, defer misaligned items, and check sprint readiness of docs/product/backlog.md or docs/work/{work-id}/tasks.md for any work item. Triggers on "groom the backlog", "refine the backlog", "is this sprint-ready", "are these stories ready", "reprioritise", "this epic is too big", "clean up the backlog". Amends in place and reports a verdict. Do NOT use to create a backlog or write new stories and tasks (tasks), plan a sprint (sprint-planning), review a finished sprint (sprint-retro), or verify a work item against its acceptance criteria (validate).

carinyadigital Bundle

Use when the user wants to plan a sprint before it starts — set the sprint goal, pull committed scope from the backlog and epic tasks.md files, account for carry-over and capacity, and record dependencies, risks, and the sprint definition of done at docs/work/sprint-{id}/plan.md. Triggers on "plan sprint 3", "what should we commit to", "set up the next sprint", "sprint planning". Do NOT use to review a finished sprint (sprint-retro), write stories or task Gherkin (tasks), groom the backlog (backlog-refine), re-sequence delivery phases (roadmap), or sign off an epic (validate).

cnife Bundle

Evaluate, compare, recommend, discover, and install AI agent skills. Use whenever the user wants to find, assess, choose, or install skills — even if they don't explicitly say "evaluate". Triggers: "评估/找/对比/安装/推荐 skill", "skill 安全", "哪个 skill 好用", "找个技能", "给 agent 装技能", "safe skill", "evaluate/compare/install skill", or any request involving skill discovery, security assessment, installation, or cross-agent compatibility.

daehounan Skill

NEXUS multi-agent orchestration playbook for end-to-end strategic engagements. Use when the user wants to orchestrate a full agency-style engagement across multiple specialists, run a phased strategic project (discovery → strategy → foundation → build → hardening → launch → operate), execute one of the named scenarios (startup MVP, enterprise feature, marketing campaign, incident response), or apply quality gates and handoff protocols across an entire team of agents. Triggers on NEXUS, multi-agent orchestration, agency engagement, phased strategic project, discovery phase, hardening phase, MVP launch, enterprise feature shipping, agent coordination matrix, quality gate, handoff protocol.

daehounan Skill

Two niche product discovery agents not covered by existing product-management skills — behavioral-nudge engineering (psychology applied to engagement) and the trend researcher persona (market intelligence with persona depth). Use when the user wants behavioral psychology applied to product engagement design, habit-loop architecture, motivational nudges, or wants the trend-researcher persona's narrative-rich market intelligence (distinct from product-management:competitive-brief which is structured). Triggers on behavioral nudge, habit loop, engagement design, motivational design, choice architecture, dark pattern review, nudge audit.

daehounan Skill

B2B sales methodology specialist routing — SPIN, Gap Selling, Sandler, MEDDPICC, discovery, deal qualification, technical pre-sales, proposal craft, pipeline analysis, account expansion, and rep coaching. Use when the user asks about preparing for a discovery call, scoring an opportunity, exposing deal risk, writing a proposal that persuades, qualifying with MEDDPICC, building outbound sequences with personalization, planning account expansion, or coaching a rep. Triggers on MEDDPICC, SPIN, Sandler, Gap Selling, discovery call, deal qualification, pipeline review, forecast accuracy, win plan, RFP response, competitive battlecard, sales coaching, account expansion, QBR, NRR.