Product & Planning

xpozpublic Skill

Find domain experts, thought leaders, and subject-matter authorities on any topic. Searches Twitter and Reddit for people who demonstrate deep knowledge, frequent discussion, and above-average expertise in a specific field. Expert discovery, talent sourcing, researcher identification, and KOL (Key Opinion Leader) mapping.

adaptocms Skill

Build the project's "brain" — a rich, local multi-file knowledge base — through deep guided discovery (a short skippable interview plus active web/competitor/keyword research), and store a summary in Adapto as _adapto_project_config so every other skill writes on-brand. Plan-then-apply; fully optional.

nahisaho Skill

プレゼンテーション作成に必要なコンテキスト（8要素）の充足度を評価し、 不足要素を1問1答で補完するスキル。全スキル起動前の品質ゲートとして機能する。 Use when 「プレゼンを作りたい」「資料を作って」等のプレゼン作成依頼を受けた直後、 Phase 1（Presentation Architect）に進む前に必ず起動する。

nahisaho Bundle

Optimize Agent Skill description fields for maximum routing precision and discovery accuracy. Use when a skill is not being activated correctly, descriptions overlap between skills, or improving Tool Coverage score.

nulightjens Bundle

Full UI design pipeline. Wireframes first, then a design PRD, optional Stitch MCP mockups, shadcn/ui components, an anti-vibe-code checklist, explicit interaction states, and a browser-based visual feedback loop.

objectstack-ai Bundle

Project-manager dispatch loop: pull ready issues from the GitHub backlog, claim and dispatch each to a parallel `os-dev` developer subagent, review the structured reports they return, then dispatch the next batch — filing `needs-user-decision` issues for anything that requires the maintainer's confirmation instead of guessing. Use when asked to "work through the backlog", "派发 issue 给开发 agent", "batch-dispatch issues", or via /pm-dispatch. NOT a customer-published skill — internal agent tooling (lives in .claude/, never in the published `skills/` dir).

objectstack-ai Bundle

Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required). Use when asked to "work through the backlog", "batch-dispatch issues", "派发 issue 给开发 agent", or to stand up a multi-agent delivery loop in an ObjectStack app project. Do not use for authoring ObjectStack metadata (the domain skills cover that), for a single already-scoped change you can just make, or as a replacement for the project's own conventions file — that file always wins.

revfactory Bundle

Write comprehensive XML-structured project specifications (build plans / PRDs) for software projects. Use when a user wants to create a build plan, project spec, technical specification, PRD, or detailed requirements document for an application they want built — or wants to spec a new feature for an existing codebase, or to review, refine, or expand an existing spec. Triggers include requests like "write a project spec", "create a build plan", "make a technical specification", "spec out this app idea", "write requirements for my project", "write a PRD", and Korean requests like "프로젝트 스펙 작성해줘", "기획서/명세서 써줘", "빌드 플랜 만들어줘", "요구사항 정의서 작성", "이 아이디어 스펙으로 정리해줘", "기능 스펙 써줘", "스펙 검토/개선해줘". The output is an XML-formatted .md file optimized for consumption by AI coding agents (e.g., Claude Code, Cursor, Copilot Workspace) or human developers.

rweisssieker-xp Bundle

Use when turning Power BI sales forecast gaps into operational rescue actions, including backlog acceleration, customer activation, product substitution, delivery escalation, gap closure ranking, and forecast-to-action recommendations.

rweisssieker-xp Bundle

Use when designing or running a Power BI revenue digital twin for sales forecasting, target-gap simulation, backlog-to-invoice scenarios, what-if revenue paths, budget attainment, and forecast-to-cash decision support from an open Power BI Desktop model or exported forecast CSVs.

rweisssieker-xp Bundle

Use when calculating what must happen to reach Power BI revenue, budget, roll, margin, cash, or service targets, including reverse planning, target-gap decomposition, required backlog conversion, and required demand uplift.

rweisssieker-xp Bundle

Use when scoring whether a Power BI model and forecast pipeline are ready for autonomous planning, including data quality, backlog snapshots, order-to-invoice matching, model accuracy, bias, granularity, constraints, overrides, and action tracking.

rweisssieker-xp Bundle

Use when coordinating multiple AI forecasting perspectives for Power BI sales forecasts, including backlog, seasonality, budget, sales skepticism, risk, consensus, dissent, and explainable forecast arbitration.

rweisssieker-xp Bundle

Use when turning autonomous Power BI planning deviations into managed exceptions, including revenue gaps, risky backlog, unrealistic targets, biased models, sparse segments, owner hints, status, escalation, and closure evidence.

peiiii Skill

Gamma sample skill for local discovery and CLI smoke tests.

gaia-research Skill

Chart a too-big effort as a shared map of decision tickets on the Gaia headquarters issue tracker, then resolve them one at a time until the way to the destination is clear. Use when someone says: "this is too big for one session", "chart a map", "wayfinder map", "plan this effort", "what do we need to decide first", "open a wayfinder", "work the map", "what's on the frontier", or /wayfinder. Covers any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven and beyond — but every map and every ticket lives on ONE tracker: gaia-research/gaia-skill-tree. This is cartography (planning an effort as decisions), NOT triage of an existing backlog — for that use /gaia-triage.

gaia-research Skill

Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this issue still valid?", "what's clogging the backlog?", "run a triage pass", or /gaia-triage. Covers two workstreams: (1) GitHub issue lifecycle — identifying resolved, stale, or need-more-info issues and acting on them via gh CLI; (2) skill-batch intake — evaluating draft proposals in registry-for-review/skill-batches/ and routing them toward promotion or rejection. This is the gatekeeping step before new skills enter the canonical registry; and (3) a cross-repo triage sweep — sizing, P0-P4 prioritization, umbrella/epic synthesis, and assignment across every gaia-research org repo, on the one headquarters tracker.

helius-tech-labs Bundle

Build Solana applications combining OKX DEX aggregation, token intelligence, and market data with Helius infrastructure. Covers DEX swaps (500+ liquidity sources), token discovery, smart money signals, meme token analysis, transaction submission via Sender, fee optimization, shred-level streaming via LaserStream, and wallet intelligence.

helius-tech-labs Bundle

Build Solana applications combining OKX DEX aggregation, token intelligence, and market data with Helius infrastructure. Covers DEX swaps (500+ liquidity sources), token discovery, smart money signals, meme token analysis, transaction submission via Sender, fee optimization, shred-level streaming via LaserStream, and wallet intelligence.

composio-community Skill

Runs the morning maintainer standup for NemoClaw. Triages the backlog, determines the day's target version, labels selected items, surfaces stragglers from previous versions, and outputs the daily plan. Use at the start of the workday. Trigger keywords - morning, standup, start of day, daily plan, what are we shipping today.

cyperx84 Skill

Break down a YouTube video, article, or local file into structured findings, lens-ranked ideas, and output notes using the breakdown CLI. Use when the user asks to analyze, break down, summarize into actionable notes, or turn content into a vault note, PRD, or task list.

devarfeen Bundle

Use when the user wants to port, migrate, rebuild, or recreate a feature that already exists in a REFERENCE implementation into a TARGET stack (e.g. bring a legacy screen into the new app). Sits at the discover → plan entry — reads the target's binding context, traces the reference's real behaviour/workflow/permissions/states the way /feature-discovery does, surveys what the target already has, and writes ONE gap map artifact, then suggests /grill-with-docs and stops. The reference is truth for behaviour; the target's design system is truth for UI. Never implements, never auto-chains; interviews for any missing input.

devarfeen Bundle

Generate clear, PM-friendly release notes, changelogs, and session summaries from git commits, feature work, or the current development session. Use when the user asks for release notes (for a date, date range, project, or feature), a changelog, a PM/stakeholder update, or to summarize what changed in plain language for non-technical readers. A handoff for the next agent session is /handoff instead.

devarfeen Bundle

Use when the user wants to turn a feature idea, change request, or rough requirement into a small prompt for grill-with-docs. When cheap repo exploration reveals domain terms missing from or stale in CONTEXT.md, surface those candidate terms for user approval before any context update. Post-decision artifacts route onward instead: turning an ADR into a spec (PRD) is /to-spec, and investigating how existing behaviour works is /feature-discovery.

devarfeen Bundle

Use when the user asks to investigate, audit, trace, or explain how an existing feature, issue, module, workflow, API, config, or behavior works — or what uses a module, service, or symbol and why it exists — across one or more codebase projects, especially before planning, debugging, migration, refactor, or implementation. Porting or rebuilding a feature into another stack routes to /port-feature instead. Stays read-only and surfaces code-discovered domain terms that may be missing from or stale in CONTEXT.md so the user can approve follow-up context updates. A whole-repo "how does everything connect" question is the graphify companion's job.

devarfeen Bundle

Orchestrate herdr worker tabs for a spec (PRD). Takes a spec reference — a Linear issue ID (PRWL-100, ABC-123) or a GitHub issue URL/number — finds its open sub-issues in the workspace's tracker of record (Linear or GitHub), launches one herdr-managed worker tab per issue running a chosen coding CLI, then monitors the tabs until every issue is completed with test evidence, blocked, or errored. Use when running inside herdr (HERDR_ENV=1) and the user wants to fan a spec out to per-issue workers.

devarfeen Bundle

After /to-tickets, pull cross-repo confidence out of your head into a durable contract + a smoke gate — but only when a spec (PRD) touches more than one PROJECT-CODE. It maps the producer surface that changed (usually the API PROJECT-CODE), traces each consumer's call-sites narrowly like /feature-discovery, and writes an agent-browser smoke checklist that proves the seam holds. Use when a multi-project spec (PRD) is sliced and you want to know the integration won't break before shipping or handing to the PM. Single-project spec with no cross-project consumers → it reports "single project — no contract needed" and stops.

devcxl Bundle

Guide users through co-authoring a substantial structured document such as a proposal, spec, RFC, PRD, or decision doc. Trigger only when the user needs a staged writing workflow from context gathering through drafting and reader validation; do not use for small edits, proofreading, translation, or generic Q&A.

dlt-hub Bundle

Safely manage dlthub secrets in *.secrets.toml. Use when the user directly asks to set up, configure, or inspect credentials (API keys, database passwords, tokens). Also use when writing Python code that needs to read secrets via dlt.secrets without exposing values. Do NOT use for pipeline creation, source discovery, or debugging pipeline execution — those skills call setup-secrets when they need credentials configured.

endorphin-ai Bundle

Product management skill for PRD writing and acceptance review. Use when creating requirements documents or validating deliverables against acceptance criteria.

evanklem Skill

Conversational bug discovery → issue draft. Light listening, background exploration, scope assessment. Asks before gh issue create — never auto-files. Use when conducting a QA session, triaging user-reported issues, or filing bugs.

evanklem Skill

Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).

gemini-cli-extensions Bundle

🐉 [SRE] Discover and map GCP infrastructure architecture including compute, networking, storage, and service dependencies.

googlecloudplatform Skill

Build a target-validation dossier for a gene / protein / pathway — biology, disease association, druggability, existing programs, key publications, trial pipeline, safety signals. Use for early-stage discovery target review, portfolio decisions, or when the user asks "what do we know about target X".

greatsumini Skill

고객사 Discovery call, Pre-meeting, 워크샵 등을 요약할 때 의사결정 배경과 정보 출처를 명시하여 사용자의 반복 질의 방지

hburaktasyurek Bundle

Use only when the user explicitly names task-groundwork to ground a vague or non-trivial software task before specification or implementation. Investigate the current repository, relevant roadmap context, history, and real-use constraints; resolve technical branches with evidence, expose only genuine human decisions, and return a concise decision-ready brief. Do not use for a narrow task that is already ready for direct execution.