Product & Planning

alexxiang2008 Skill

首席产品设计师（/prd-writer 的中文别名）

alexxiang2008 Bundle

首席产品设计师 - 通过多轮启发式对话，帮助用户规划产品路线图、设计 MVP、绘制原型图、输出架构蓝图，最终生成完整的 PRD 文档。支持 /prd 或 /产品需求 命令启动。

szoloth Bundle

Coach users on storytelling, communication, and influence using 45 practitioner-tested techniques from Lenny Rachitsky's archive. Use when drafting presentations, preparing for stakeholder conversations, writing executive communications, pitching ideas, seeking buy-in, or improving persuasion. Triggers on "how should I present this", "help me pitch", "get buy-in", "convince", "influence", "stakeholder prep", "improve my writing", "presentation feedback", "storytelling", "executive presence", "meeting prep", or any request to make a communication more compelling.

ajbarea Skill

Audit a plan's design decisions — library, framework, pattern, and architecture choices in IMPL.md / ROADMAP.md — for missing `# research(YYYY-MM):` provenance, then web-search to ground them. Use when you want architectural choices verified against current best practice before they harden into code, rather than resting on training-cutoff recall. Catches committed decisions stated as fact but never checked — the class of miss that becomes revertable work.

apache Skill

Use for Doris tablet/replica health, version skew, clone backlog, disk balance, and tablet repair. Commands: SHOW PROC tablet_health, SHOW TABLET, ADMIN REPAIR.

aquarius-mu Skill

Turn the current conversation context into a PRD and save it. Use when you want a formal product requirements document from the current discussion.

timmy6942025 Skill

Use this skill when running, configuring, connecting to, or extending the OpenCode HTTP server. Covers opencode serve, opencode web, authentication, mDNS discovery, CORS, the full OpenAPI 3.1 spec, all REST endpoints (sessions, messages, config, providers, files, tools, LSP, MCP, agents, TUI control, events, docs), the SDK generated from the spec, connecting clients, attaching terminals, IDE plugin integration, and real-time SSE event streaming.

timmy6942025 Skill

Create, configure, and troubleshoot OpenCode agent skills (SKILL.md definitions). Covers file locations, discovery, frontmatter spec, permissions, per-agent overrides, and publishing.

tranz007 Skill

Turn a feature request, stakeholder request, idea, complaint, or vague design assignment into a clear UX problem frame with user outcome, evidence, constraints, assumptions, unknowns, and success signals. Use before solutioning when the real problem or reason for the work is unclear.

aictrl-dev Bundle

Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says "create an issue", "open a ticket", "make a backlog item", or describes a feature or chore that should be tracked; delegate defects to create-bug.

aigengame Skill

Update STATE.md — the lightweight cross-session "daily report" of project progress. Rewrite (never append) the current milestone/phase, what this session completed or changed, experience relevant to the next work, the recommended next issues/tasks, and the filtered-and-inherited backlog of unfinished cross-session items. Use at the end of a working session, when wrapping up, or when explicitly invoked.

aj-geddes Bundle

Guides deliberate management of technical debt: recognition, tracking, prioritization, and paydown. ALWAYS trigger on "technical debt", "code shortcut", "pay down debt", "debt tracking", "just for now", "temporary hack", "hardcoded value", "copy-paste code", "missing tests", "TODO cleanup", "refactor plan", "debt priority", "interest cost", "boy scout rule", "code quality backlog". Use when taking a shortcut, discovering suboptimal code, planning debt paydown, or quantifying ongoing cost of compromises.

ry-run Bundle

Use Ace Tool MCP (`mcp__ace_tool__search_context`) for semantic repository discovery. Use it when the exact file, symbol, or implementation path is unknown, rather than starting with exact IDE search or direct file edits.

ry-run Bundle

Use Ref MCP to search documentation sources and then read the exact returned URL. Use it for documentation-site discovery and page-level reading when the right doc page is not yet known, rather than versioned library-ID lookup.

ry-run Bundle

Use Vercel MCP for project discovery, deployments, build and runtime logs, toolbar threads, protected preview access, and Vercel documentation. Use it when the task centers on Vercel-hosted application state, rather than local-only execution.

ry-run Bundle

Use the JetBrains IDE MCP Server (IntelliJ IDEA 2025.2+) for IDE-backed indexing, inspections, symbol info, project file operations, and structural refactoring. Use it when you need exact project-aware analysis or safe IDE refactors, rather than broad semantic repository discovery.

automatewithuday Skill

Systematically extract, classify, and pre-handle prospect objections from sales data. Build objection playbooks that turn 'no' into 'tell me more' — in cold outreach, discovery calls, and follow-ups.

automatewithuday Skill

Extract actionable intelligence from sales call transcripts. Systematic frameworks for mining discovery calls, demos, and follow-ups to improve messaging, objection handling, and close rates.

bjcoombs Bundle

Read-only org repo state report. Reuses ghsync's repo discovery (teams union org-repo-list) but, instead of cloning, queries each repo's remote GitHub state - open PRs, CI on the default branch, open security alerts (Dependabot / code-scanning / secret-scanning), and branch protection - and rolls it into a terminal summary plus a timestamped markdown file. Endpoints that need admin and return 403/404 are reported as no-access / unknown, never as a clean zero. TRIGGER when the user types /ghreport, asks 'what state are the org's repos in', wants an org health report or repo state snapshot, or asks about open PRs / failing GitHub Actions / security alerts across a whole org or personal account.

bjcoombs Bundle

Run a list of work units to completion with an Agent Team: derive a dependency DAG and hot-file map, spawn one ephemeral teammate per unit (or combined group), drive each PR through pr-review-merge, smart-merge in waves, recover from crashes, and run a retrospective. Source-agnostic — the caller supplies a work-source adapter. A library skill invoked BY the /tm and /issues commands, not run directly by a user (it needs a caller-supplied adapter). TRIGGER when a command needs autonomous multi-unit team orchestration to completion — a tag, issue queue, backlog, or set of tickets run to done with Agent Teams. For a single PR use pr-review-merge instead; not for one-off single-task work.

bmad-code-org Bundle

Strategic business analyst and product discovery partner for WDS. Use when the user asks to talk to Saga or requests the WDS analyst.

bmad-code-org Bundle

Implementation agent. Owns the tech audit, the PRD, and the build. Reads Freya's Work Orders and turns them into working code — one verified task at a time.

bogdanbaciu21 Bundle

Run a high-thinking decision workflow that evaluates options through multiple independent model/provider perspectives, forces dissent, ranks the options, and returns one synthesized verdict with assumptions, evidence gaps, and an action plan. Bring your own API keys (Anthropic, OpenAI, and/or Gemini). Use when someone says "deep-decide", "mega decide", "pressure-test this decision", "evaluate options deeply", "which option should I pick", "rank these options", "stress-test this choice", or asks for a multi-model decision review. Do not use for pure factual research; use a deep-research skill for source discovery or long research reports, then feed its findings in here.

bogdanbaciu21 Bundle

Draft a weekly stakeholder update for any software project. Use when the user asks for a weekly update, Friday email, status report, sprint summary, or stakeholder progress report. Pulls commits from git and issue counts from the project's tracker (GitHub Issues by default; Linear or Jira when an MCP server, API token, or CLI is available), asks a short set of clarifying questions, and produces a draft markdown file in docs/weekly-updates/. Optionally renders an HTML email using a brand template if one is configured.

opsmill Skill

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

opsmill Skill

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

fossasia 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.

zhongjingyun Bundle

Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes.

caelaxie Skill

Create or update Hermes general plugins with `plugin.yaml`, `register(ctx)`, tool schemas, handlers, hooks, slash commands, CLI commands, and discovery or enablement debugging. Use when asked to build a Hermes plugin, write `plugin.yaml`, implement `register(ctx)`, add Hermes tools or hooks, or troubleshoot plugin loading and opt-in enablement.

chanktb Bundle

Plans a Google Ads launch or expansion: how to split budget, which campaign types to run (Search, Branded Search, Performance Max, Demand Gen) and in what order, expected conversions/CPA/ROAS given budget and AOV, and a phased ramp roadmap. Reads context + audit + measurement; forecasts from real account data when available, benchmarks when not. Use when the user says "plan", "budget", "what campaigns should I run", "how should I launch Google Ads", "media plan", "campaign mix", "forecast".

chanktb Skill

Builds a Demand Gen campaign blueprint — audience-led, creative-heavy campaigns across YouTube, Discover, and Gmail. Covers audience strategy (your-data, lookalikes, custom segments), image and video creative sets, ad formats, and the upper/mid-funnel measurement caveats. Emits a human .xlsx plus a campaign-spec .json (demand_gen). Reads account-context.yaml. Use when the user says "demand gen", "demand generation", "youtube campaign", "discovery ads", "top of funnel".

codespringapp Bundle

Turn an idea into a CodeSpring plan — from a sales-call recording, a transcript, a voice note, or someone just talking at you about what they want. Interviews the person (or mines the recording) for the job the app does, walks the screens with them, picks the platform from what the app actually needs to do, finds the one technically hard part and names a real solution for it (including existing open-source prior art), cuts to a v1 that can be sold, then writes the map — core features, sub-features, notes — and hands off to cs-build-create-prd and cs-build-create-tasks. The no-code-yet counterpart to cs-build-import-codebase. Triggers, "plan my app", "generate a plan", "turn this recording into a plan", "I have an idea for an app", "design my app in CodeSpring", "map out this idea", "I've got a client call recording, make the plan", "plan from scratch".

codespringapp Skill

Specialist for creating CodeSpring PRDs. Interactive — it lists the user's core features, asks which one and whether to generate a Frontend, Backend, or Both PRD, then deep-dives the real code and generates the PRD(s) and attaches them to the feature's bridge on the canvas. The PRDs capture the shared backend contracts and design system so new features are built without duplicating or breaking what exists. Use when the user wants a PRD / spec for a feature. Triggers, "create a PRD", "make a frontend PRD", "make a backend PRD", "generate PRDs for this feature", "document this feature in CodeSpring", "spec out X so I can design new features".

codespringapp Skill

Turn a CodeSpring feature's notes + PRDs into a numbered, prioritized Kanban task list linked to that feature. Reads the feature, its sub-features, its PRDs, and any features that link to it, then writes ordered tasks that are safe to build in parallel — each with what/why/what-it-touches/what-not-to- touch/dependencies. Use when the user has a feature planned and wants a build plan. Triggers, "create tasks", "make a task list", "break this feature into tasks", "generate a build plan", "turn my PRD into tasks", "what do I build first".

codespringapp Bundle

Research a product idea before committing it to a CodeSpring build plan. Finds direct competitors, open-source projects, substitutes, and relevant platform capabilities; separates commodity features from a defensible wedge; then records an evidence-backed recommendation and creates only the scoped feature and tasks worth building. Use when the user asks whether an idea already exists, requests market or competitor research, asks what would make a product unique, or wants to validate an idea before creating a PRD or tasks.

codespringapp Bundle

Get an existing app into CodeSpring as a visual feature map — a small set of core features (sidebar-level) with nested sub-features and a "how it works" note each — then PRDs (via cs-build-create-prd) and Kanban tasks. Takes an OPTIONAL audit + verdict: with no audit it documents what exists; with an audit it builds the corrected target map (what the app should be) and generates fix or rebuild tasks from the findings. Detects an existing map, judges whether it is any good, and keeps or repairs it instead of duplicating it — and offers to audit first if the codebase looks broken. Triggers, "import my codebase into CodeSpring", "map my existing app", "reverse engineer my app into features", "bring this project into CodeSpring", "visualize my code in CodeSpring".