Product & Planning

alanpai Skill

引導使用者用「規格驅動開發（Spec-Driven Development, SDD）」方法論，從零規劃一個軟體系統的完整開發路線圖，並產出四份可直接落地的工作檔模板（AI 工作守則、交班板、作業筆記、拍板索引）與獨立對抗審查制度。只要使用者提到「新專案」「想開發一個系統/工具/平台」「幫我規劃開發流程」「架構規劃」「開發路線圖」「從頭開始一個專案」，或帶著一個模糊的產品想法來討論怎麼動工，就啟動這個 skill——即使他們沒有明確說出「路線圖」或「規劃」這些詞。本 skill 特別為「單人（或極小團隊）+ 多 AI 協作開發」情境設計，並內建多視窗同時施工的互撞防護（佔號即開檔、交班板分艙、撞號守門測試、審查佇列一進一出）。

samber Bundle

Before starting any developer-platform, public-API, or integration work - or whenever no other platform skill has been chosen - route the task to the right skill in samber/developer-platform-skills, or say plainly that none fits, then bootstrap or resume the project's shared platform context. Fires at every API or platform project start, at each recurring platform review, and whenever routing is unclear. Use whenever the user mentions a developer platform kickoff, a new public API program, an integration-surface roadmap, "which platform skill do I need", "where do I start with our public API", platform skill routing, or a recurring platform check-in - even if they never name a skill or ask to be routed. It spans REST, GraphQL and gRPC design, webhooks, SDKs, MCP, OAuth and API keys, rate limits, versioning, developer portals, docs, sandboxes, marketplaces, and partner strategy, so an ambiguous platform question belongs here first. Outputs a short-list and an ordered skill chain, never the design itself.

samber Bundle

Decide which integration surfaces a platform offers external developers and AI agents - REST, GraphQL, gRPC, SQL access, bulk data sharing, webhooks, SDKs, CLI, MCP, embedded components - and in what build order, sequenced by reversal cost and audience rather than novelty. Use whenever the user mentions which API to build first, adding a GraphQL or MCP layer, an integration-surface roadmap, API-first vs embedded-first, or a missing surface blocking deals - even if they never say "integration surface". Umbrella strategy only - once a surface is chosen, per-surface design belongs to siblings such as samber/developer-platform-skills@webhook-platform-design and samber/developer-platform-skills@sdk-portfolio-strategy.

samber Bundle

Select which technology partners a B2B SaaS vendor integrates with and how deep each partnership goes - demand-data partner prioritization (deal-attached revenue, retention lift, competitive necessity), the referral-to-OEM depth ladder with graduation gates, joint-roadmap and co-build governance, certification-program joins with budgeted renewals, sourced-vs-influenced pipeline attribution, and where the technology-partnerships function reports. Use whenever the user mentions integration partners, ISV alliances, technology partnerships, partner tiers, certification programs, or partner-pipeline attribution - even if they never say "partnership strategy". Strategy layer only. Do NOT use for ETL-platform listings - use samber/developer-platform-skills@etl-connector-strategy instead.

toolmonsters Bundle

Plans, runs and reviews sales discovery calls (questions, structure, qualifying, uncovering pain) using rules weighted by how many of the 20 most-watched videos repeat each one, and flags where experts disagree so you can A/B test instead of guessing. Use when the user says "prep my discovery call", "what should I ask on a sales call", "qualify this prospect", "review my discovery call", "structure a first sales call" or "how do I uncover pain".

samber Bundle

Designs an issue and pull-request triage system a maintainer team can sustain - response targets sized against real capacity, the label taxonomy, intake cuts through structured forms and off-tracker routing, a separate security-report path, triage duty assignment, and the closing, staleness and volume-gating policy. Use whenever someone says "our issue tracker is out of control", "design an issue triage process", "set up labels for our repo", "we have 900 open issues", "should we run a stale bot", "PR backlog nobody reviews", "triage rotation", or "we are drowning in AI-generated reports" - even if they only say maintenance is overwhelming. Not good-first-issue curation - use samber/developer-relations-skills@oss-contributor-onboarding.

samber Bundle

Maps the developer journey for one audience segment - discovery, trial, adoption, contribution, advocacy - as a stage-by-stage table where each stage carries an exit event, a named owner, cited friction evidence and one signal, and names the single leak worth fixing next. Use whenever someone asks what their developer journey looks like, wants a developer adoption funnel or journey map, asks why developers try the product but never reach production, where adoption drops off, who owns each step of developer experience, or how developers become contributors - even if they only say "we lose people somewhere". Not the metrics framework - use samber/developer-relations-skills@devrel-metrics.

tiangong-ai Bundle

Perform one isolated owner-requested SCI search outside Tiangong Auto Research, or provide SCI method guidance when Auto Research discovery invokes the locked broker capability. Searches only `sci`. If an ancestor contains `.tiangong-research` and the request is open-ended, multi-source, analytical, builds on prior outputs, or produces a conclusion/artifact, route to `tiangong-auto-research` and do not execute this standalone wrapper. Inside a managed workspace, standalone use requires the user's explicit isolated-query request and `execution_mode=standalone`.

oracle Bundle

Public APEXlang router with deterministic local-context discovery and compact machine-readable contracts.

rsmdt Bundle

Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/.

rsmdt Bundle

Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.

rsmdt Bundle

Unified codebase discovery across structure navigation, tech-stack detection, and documentation extraction. Use when onboarding to a project, locating implementation paths, identifying frameworks/tooling, or validating docs against code reality.

rsmdt Bundle

Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stakeholders.

creekmoon Skill

PRD写作规范 - 精简、大白话、图表优先

creekmoon Bundle

资深产品经理（PM）+ 产品设计角色技能，是功能/页面从想法到落地的结构源头：拆解真实需求（JTBD/Persona）、补全场景与边界、判断要不要做与先做什么（Build/Don't Build、RICE），并直接产出可执行的结构设计——轨道判断、页面形态、布局骨架、信息分区、状态清单、灰阶线框原型与验收标准，供架构、设计、开发阶段直接消费。Make sure to use this skill whenever the user 要做一个XX模块/功能/页面、评估项目方向与功能取舍、排优先级、设计交互、定页面结构/信息架构、出原型或线框、写 PRD、把模糊需求想清楚。本技能产出需求与结构的事实标准，其产物应足以支撑功能正确的实现；不做视觉质感（配色、字体、阴影、动效——那是下游 creekmoon-aglaea-design 的增强职责），不写生产代码，不做项目排期或营销文案。

vishalsachdev Bundle

Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.

tibsfox Bundle

Use when the user asks "what should I work on", mentions GSD phases, ROADMAP, or .planning/ artifacts. Routes to the correct GSD command for the current project state.

maodeyu180 Bundle

Create or edit images and generate videos through CatsAPI. Use for CatsAPI creative requests, model/parameter discovery, cost or balance checks, and recovering existing generation tasks. Respect an explicitly chosen different provider; do not route unrelated image analysis or repository maintenance into generation.

alfons0329 Bundle

Automated study roadmap and batch-classification page generator for LeetCode/NeetCode topics. Organizes problem sets into sequential study batches on Notion parent pages.

jramsahai Skill

Track work projects in the Obsidian vault: create/update project notes, status, key decisions, blockers, meeting notes, docs, and stakeholder links. Use for project state and project conversations. NOT for: individual tasks (task-tracking), pre-project ideas (idea-pipeline), or evergreen reference (knowledge-base).

c1trusovo831 Bundle

Discover, compare, and install agent skills when the user asks to find a skill or extend agent capabilities. Ordinary requests to perform a task do not require skill discovery.

librefang Skill

Project management expert for Agile, estimation, risk management, and stakeholder communication

prompthon-io Bundle

Persistent product price tracking for natural-language product requests. Use when a user asks to watch, track, monitor, compare, or report prices for a product, especially with a target price or threshold such as "Watch MacBook Pro M3 14-inch and tell me if it drops below $1200." Supports source discovery, Playwright/browser product checks, SQLite history, threshold comparison, and Markdown price reports.

hideki5123 Bundle

Use @pchuri/jira-cli to view, search, create, update, and delete Jira issues, comments, sprints, and projects from the terminal. Prefer this skill over `mcp__claude_ai_Atlassian__*` MCP tools when you need: JQL search, sprint/board management, markdown export, file-based descriptions, issue deletion, comment management, or shell pipelines. Trigger phrases include "jira", "jira-cli", "jira issue", "create jira issue", "search jira", "jira sprint", "jira board", "jira project", "jira comment", "jira JQL", "list jira issues", "view jira issue", "jira backlog".

hideki5123 Bundle

Review local git changes from a PMBOK-based product management perspective. Analyzes changes against 7 PMBOK knowledge areas: Scope, Risk, Stakeholder, Quality, Integration, Schedule, and Resource management. Produces a structured report identifying project-level impacts and risks. The PMBOK analyst role itself lives in the `pm-review:pm-review` subagent; this skill is a thin orchestrator that gathers the change set and project context before delegating. Use when the user asks for a PM review, product management review, PMBOK analysis, project impact assessment, scope review, risk review, or stakeholder impact analysis of local changes. Trigger phrases include "pm review", "product management review", "PMBOK review", "project impact", "scope review", "risk review", "stakeholder impact", "pm-review", "review from PM perspective", "project management review".

dev-ansh-r Bundle

Discover and verify a Qualcomm development environment for any Snapdragon or QCS/QCM/SA part - QCS6490, QCS8550, QCS8250, RB5, SA8295, Snapdragon X and others. Locates the target board, build host and AIMET host, confirms reachability, and reads back the installed QAIRT/QNN SDK version, eSDK toolchain, SoC identity, Hexagon HTP architecture and board image. Writes a .qualcomm-env config the other Qualcomm skills read. Use at the start of any QNN/QAIRT/AIMET/HTP/NPU task, when a converter or board command fails for unclear reasons, or when asked which SDK version or HTP architecture is installed.

hideki5123 Bundle

Turn a feature idea into an execution-ready document set through an adversarial PRD "council": grill the user for requirements, draft a PRD, then debate it with OpenAI Codex round-by-round until BOTH sides approve, and finally emit a Technical PRD (one overall summary + one per UseCase) plus a task list with agent assignments, dependencies, and acceptance criteria — designed so a PdM-role agent could later distribute the work to specialist agents. Document-generation only (no agent execution). Writes local files under docs/prd/<slug>/; never publishes to external trackers. Uses codex-server (the user's ChatGPT subscription) for the debate loop. Use when the user wants a PRD reviewed/approved by Codex, a "PRD council", a Technical PRD for task distribution, or a task breakdown from a PRD. Trigger patterns (match any variation): prd-council / prd council / PRD council / PRD + {Codex, GPT, ChatGPT} + {議論, 相互承認, レビュー, 承認, debate, review, approve} / CodexとPRDを議論 / CodexとPRDを相互承認 / PRDをCodexと詰める / technical prd / t

hideki5123 Bundle

End-to-end TDD development workflow with multi-agent team review and skill-based quality gates. Plans, discusses, and implements features using strict RED-GREEN-REFACTOR test-driven development. Handles worktree-based branch isolation (from latest remote), PRD and technical requirements creation, plan-mode exploration, embedded team discussion at every deliverable phase, skill-agent quality gates (review-local, orch-qa, scenario-gen, pm-review, e2e-test), mandatory test case design via test-scenario skill, TDD implementation, fresh agent implementation review, conventional commits, optional PR creation with self-pr-review and address-pr-comments. Use when the user asks to implement a feature, fix a bug, refactor code, add tests, or any multi-step development task. Triggers on "implement X", "build Y", "add feature Z", "fix bug", "refactor", "implement with TDD", "add feature with tests", "build X following TDD", or when the user invokes /dev-workflow.

hideki5123 Bundle

Turn a finished grill-me (or any design-finalizing) session into a running implementation kickoff. Synthesizes the session's shared understanding into a self-contained implementation brief, hardens it with a small agent team and an adversarial codex-server review loop (until Codex approves), then launches a backgrounded, remote-controllable, autonomous Claude Code session (claude-bg / ccb-style: --permission-mode auto --allow-dangerously-skip-permissions --bg --remote-control) that runs /prd-council seeded with the brief to produce the execution-ready plan and begin implementation. Confirm-before-launch by default. Document/prompt generation + session spawning; it does not itself write feature code. Use AFTER a grill session when the user wants to hand the agreed design off to a fresh autonomous session. Trigger patterns (match any variation): grill-to-impl / grill to impl / grill→impl / grillの成果を実装へ / grillしたセッションから実装 / grillした内容でbriefを作って / briefを作ってCodexにレビュー / Codexにレビューさせてからprdーcouncil / 別セッションでprd-counc

hideki5123 Bundle

Create Jira tickets from Slack conversations, optionally with Confluence documentation pages. Reads Slack threads/channels/search results via slack-cli, analyzes the conversation to extract problems, participants, decisions, and action items, then creates Jira issue(s) via jira-cli with the conversation context. A single conversation may produce multiple tickets if it covers distinct topics. For long or complex conversations (>15 messages), recommends creating a Confluence documentation page via confluence-cli with a context-aware format (postmortem for bugs, PRD for features, slim summary for tasks). Supports input as Slack permalink URL, channel name, thread timestamp, or search query. Presents drafts for interactive review before creating. Trigger phrases include "slack to ticket", "slack-to-ticket", "create ticket from slack", "jira ticket from slack", "create ticket from #channel", "create ticket from thread", "slack conversation to jira", "ticket from slack thread", "jira from slack", "slack to jira", "

sergekostenchuk Bundle

Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.

sergekostenchuk Bundle

Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.

aiblueprinthq Bundle

Run an optional guided product-discovery interview and draft project-plan.md and build-plan.md only after the user is ready. Use for /discovery, guided planning, thinking through a new product, or deepening plans. Never require it before /overview.

manan-buddhadev Bundle

Use when the user invokes /xray with a path to an implementation plan, spec, or PRD markdown file and wants to understand or review it visually instead of reading long prose

agentel-tech Bundle

Connect an AI Agent to the Agentel identity and communication network. Use for first-run registration, identity verification, authenticated network reads, profile and connection maintenance, public Updates, replies, Skill discovery, rankings, or Trust evidence. Do not expose credentials or perform consequential writes without explicit approval.

p7th0n Bundle

Run a Jeff Patton-style user story mapping session to build shared understanding with stakeholders before writing a roadmap entry or spec proposal. Default mode covers one feature area per session; can also do an explicit whole-project "backbone-only" pass on request. Use when starting discovery on a new feature area, prepping for a conversation with real users/stakeholders, or when the user says "let's story map X," "run patton mode," or asks about personas/activities/user stories for a product.