Product & Planning

emily2040 Bundle

Structure collaboration between data scientists, AI agents, and domain experts when domain judgment is required. Use when an agent needs a judgment-heavy data science workflow for structure sme review for agent-assisted ds, including evidence review, local artifact inspection, risk classification, stakeholder-ready decisions, reproducibility, governance, or agent-to-agent handoff. Trigger for Codex, Claude, Gemini, Copilot, Cursor, Windsurf, Gravity, LangGraph, CrewAI, AutoGen, or local agents when this exact workflow is needed.

emily2040 Bundle

Diagnose missing-data mechanisms and design imputation, exclusion, or sensitivity plans. Use when an agent needs a judgment-heavy data science workflow for diagnose missing data before imputation, including evidence review, local artifact inspection, risk classification, stakeholder-ready decisions, reproducibility, governance, or agent-to-agent handoff. Trigger for Codex, Claude, Gemini, Copilot, Cursor, Windsurf, Gravity, LangGraph, CrewAI, AutoGen, or local agents when this exact workflow is needed.

getcargohq Skill

Find the buying committee at a target account — every stakeholder matching a set of titles, seniorities, and departments, powered by Cargo. Triggers: "find the buying committee at Acme", "who are the decision makers at this company", "find stakeholders", "multi-thread this account", "who else should I be talking to at this account". Providers: aiArk. Skip when: you are sourcing across many companies rather than going deep on a few — use find-b2b-leads.

honerlaw Bundle

Prints the current overall status of a project's minerva workstream as markdown tables — every unit's lifecycle stage, phase progress, branch/PR state and the next lifecycle step to run, plus knowledge-wiki health and the deferred backlog. Read-only; mutates nothing. Use when the user asks where things stand, what's in flight, what to do next, what still needs shipping or cleaning up, or for a status check / summary / dashboard / overview of the work; when an agent resumes a project and needs to orient before picking up work ("pick up where we left off", "what were we doing"); or when they invoke `minerva:status`.

m1nga Bundle

Wind-tunnel a new idea before anything gets built. When the user brings a product, skill, site, or feature idea and asks for a pre-build test — "simulate some users and test this", "probe this idea", 帮我模拟用户测测 / 新想法:先别建,推演一下 — derive 4–7 personas from the idea's claimed audience with forced diversity slots, then run each through honest first-contact simulation: discovery → first-glance reading (misreads recorded verbatim) → start or not → first friction → return or not. Output: BUILD/NARROW/RETHINK verdict with assumption debt, problems ranked by breadth × fatality, a fix each, a revised one-pager, and a reality bridge: real-user tests with kill criteria for the deadliest findings — simulation generates hypotheses, never market evidence. NOT for a bare "这个想法怎么样 / what do you think" (answer directly, or thinking-partner), NOT for instruction text or SKILL.md files (scenario-probe's seat), NOT for a runnable product (product-experience-officer's seat), NOT for technical feasibility (research, not personas).

m1nga Bundle

Design, audit, repair, and operationalize reliable agent loops with explicit goals, triggers, persistent state, orchestration, independent verification, failure recovery, open skill discovery or creation, controlled self-improvement, and retirement conditions. Use to build a loop, an autonomous or recurring agent workflow, a multi-agent operating system, a self-improving process, a zero-context recovery flow, a permanent update/replacement loop, or to turn a prose plan or repeated prompt into a genuinely executable loop. Trigger on natural phrasings such as "I keep running this prompt by hand — automate it", "make this agent run on its own and check its own work", "why does my automation silently fail", and Chinese phrasings such as "把这个流程变成自动循环", "帮我设计一个自动跑的 agent 工作流". For a plain scheduled reminder or interval re-run without state or verification, use the host scheduler (cron/schedule tools) instead. For static product architecture and responsibility contracts, use map-product-system.

m1nga Bundle

Finish self-authored skills through user-perspective review, comparable-skill research, tested improvements, and verified GitHub publication. Use when creating, materially updating, or releasing an owned skill, and for skill discovery experiments.

matis-dev Bundle

Use to cut an approved plan into shippable vertical slices (decompose), refine one feature into milestones (deep-dive), or — upstream of code — write a brief, PRD, or research plan. Enforces the slice ceiling, INVEST, and Gherkin acceptance criteria. Every number is sourced or labelled a hypothesis.

nextstage-brasil Bundle

(NS) Cypress E2E in independent tests-e2e/ at repo root (bootstrap when missing). DRY device-aware commands (shared/pages/device). Use when writing/refactoring Cypress specs, custom commands, scaffolding E2E, or implementing E2E tasks — not when planning E2E task markdown (ns-spec-driven references/e2e-test-task-generator.md). Mandatory discovery before specs.

nextstage-brasil Bundle

(NS) Gated PM: clarify, RICE/WSJF, sprint, PERT/Monte Carlo; version handoff; risk/status/OKR; orçamento, Function Points, proposta comercial; cronograma P100/P85/P50. Use on transcripts, backlog, timeline, delivery date, status, orçamento, cotação, cronograma, handoff, fecha a versão — even if PM unnamed. Do NOT use for coding, SDD, GitLab issue execution, or `/ns-requirements-enricher`.

nuonuo0518 Bundle

Validates an existing game project PRD or GDD for production readiness. Runs a comprehensive 10-step review covering information density, clarity & ambiguity, traceability, implementation leakage, game-domain compliance, and holistic quality. Use when the user asks to validate, review, audit, check, score, or verify a game PRD, GDD, requirements doc, or design spec — especially phrases like "验证设计案", "检查PRD质量", "审查需求文档", "这份文档能不能进开发", "PRD写得怎么样", "review this GDD", "is this PRD production-ready", "check requirements doc". Do not use for: drafting or writing a new PRD/GDD from scratch; general writing polish or grammar fixes; validating non-game PRDs (SaaS, enterprise, mobile apps without game mechanics); code review; UX specification; implementation planning; or discussing what a good PRD looks like in the abstract.

zrozoom Skill

Repository and project manager. Git Flow, Issues/PRs, GitHub Projects, sprint planning, backlog management, and ROADMAP synchronization. Trigger when: create an issue/PR, push changes, plan a sprint, review backlog, update the roadmap, stwórz issue/PR, wypchnij zmiany, planuj sprint, przegląd backlogu, aktualizacja roadmapy.

zrozoom Skill

Use when generating operational reports, release notes, demo readiness checks, stakeholder updates, infrastructure cost/expiry checks, or bilingual changelogs. Triggers: /release-notes, /investor-report, /demo-check, /cost-check, changelog, release notes, stakeholder report, monthly metrics, demo readiness, before demo, infrastructure costs, cost monitoring, certificate expiry.

zrozoom Skill

Backlog prioritization for GitHub issues and Jira tickets. Finds items without milestones, proposes owners and priority, and reports QA queue size. Trigger when: /triage backlog, prioritize backlog, issues without milestone, triage backlogu.

zrozoom Skill

Stakeholder report generator. Collects product metrics, GitHub milestones, and DB stats where available, then formats PDF-ready markdown. Trigger when: /investor-report, stakeholder report, raport inwestorski, metryki produktu.

agent0ai Skill

Use the frontend API surface correctly for app files, discovery, identity, and permission-aware browser data access.

anyoneanderson Bundle

Plan an epic for /harness: draft product-spec.md interactively, derive roadmap.md with sprint decomposition and bundling, then emit one tracker Issue per sprint. The last human-in-the-loop step before autonomous sprints begin in /harness-loop. Prerequisite: /harness-init must have already initialised .harness/ and .claude/agents/ in this project. This skill is not for spec-driven (/spec-generator) workflows. English triggers: "Plan the epic", "Run harness-plan", "Create product-spec" 日本語トリガー: 「epic を計画」「harness-plan を実行」「product-spec を作成」

apple Bundle

Analyze a codebase before starting a Metal 4 port. Produces a discovery report with platform readiness, graphics backend analysis, feature coverage matrix, and trace-grounded findings. Use before any porting work begins.

apple Skill

Define the next porting goal. Reads the discovery report and current porting state, proposes a goal with milestones, and creates a goal document.

arboraistudio Bundle

Plan customer discovery, user interviews, first-user acquisition, founder sales, cold outreach, rejection handling, customer conversion, and learning from prospects.

robinebers Bundle

Use when the user asks for a full security scan or security code review of a pull request, commit, branch, patch, working-tree diff, or repository. Run distinct phases: threat modeling, finding discovery, validation, attack-path analysis, and final markdown output.

robinebers Skill

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

chrike Bundle

Use for software implementation planning when the user asks for planning, an implementation plan, approach comparison, task breakdown, roadmap, step-by-step plan, or splitting a feature/refactor into clear implementation slices before the next safe implementation step, or when a requested software implementation has unresolved implementation approach, dependency-ordering, sequencing, migration, compatibility, rollout, or scope decisions that cannot be safely inferred. Do not use when the primary request is an architecture, ownership, interface, seam, or dependency-boundary decision; use design-codebase first when available, then return here for dependent rollout or sequencing planning. Do not use for PRD authoring, issue or tracker drafting/publication, durable multi-session decision-map workflows, ordinary code explanation, or implementation of an already-settled plan.

chrike Skill

Use when the user explicitly asks to ideate, refine, explore alternatives, or converge on a product, feature, process, or solution concept before implementation planning. Do not use for ordinary vague implementation requests, one-question intent interviews, implementation plans, architecture or ownership decisions, PRD or issue drafting, or reliability review of an existing plan.

chrike Skill

Use when the user clearly asks to create, publish, or update a tracker item; turn discussion into a PRD, explicit technical specification, issue draft, tracker-ready work item, or triage result; or modify tracker state such as status, labels, comments, or closure. Keep ordinary coding, planning, review, and repository-local work-item execution in their own flows.

evoclaw Skill

Use when designing the analysis framework for a discovery or data analysis project — defines story line, analysis dimensions, sufficiency criteria, and alternative explanations to check

evoclaw Skill

Use when a user expresses research intent but has not yet identified a specific research direction, completed a literature review, or confirmed resource readiness — covers Phase 1 from topic discovery through G1 gate

isaac-sim Skill

USD asset discovery, measurement, placement, and validation in Omniverse. Asset cataloging (bbox, shaders, prim count), placeholder-to-asset swap, offset correction, shader compatibility for headless renders, animation baking, articulation, and USD composition architecture.

thesmokedev Skill

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.

omicverse Bundle

CellFateGenie: Adaptive Threshold Regression for pseudotime-associated gene discovery, Mellon density, lineage scoring via ov.single.Fate.

jal-co Bundle

Find, install, and configure MCP servers. Use proactively for MCP discovery, OAuth setup, env vars, stdio vs SSE transport, or troubleshooting MCP connections. Examples: - user: "Add the filesystem MCP server" → read server file, add to mcpServers in opencode.json, verify transport type - user: "How do I use MCP with GitHub?" → check catalog, install @modelcontextprotocol/server-github, configure OAuth token - user: "MCP not connecting" → check transport type (stdio/SSE), verify args/command, check env vars are passed - user: "What MCPs are available?" → run list_mcps.py, show catalog with auth types and install commands

jal-co Skill

Create and manage OpenCode skills with proper SKILL.md format, frontmatter, and organization. Use for skill creation, naming conventions, permission configuration, and reference management. Use proactively when user says "create a skill", "SKILL.md", "skill discovery", "skill permissions", or asks about skill structure. Examples: - user: "Create a skill for database migrations" → design SKILL.md with description, instructions, optional references/ - user: "How do I restrict which skills an agent can use?" → explain permission.skill patterns - user: "Where should I put my skill?" → explain project vs global paths

kv0906 Skill

Draft or edit a document — PRD, spec, design doc, technical brief. Use for "/doc project title" to create a new doc or edit existing.

kv0906 Bundle

Jira integration via acli CLI. Use when user says '/jira', 'check Jira board', 'create Jira ticket', 'move ticket to done', 'search Jira', 'sync blockers from Jira', 'what's in the sprint', 'Jira status', 'assign ticket', 'view backlog', or wants to interact with Jira issues, sprints, or boards from the terminal.

kv0906 Skill

Interview user about a spec file and write detailed requirements. Use when user asks to "interview me about this spec", "brainstorm this PRD", "review spec with questions", or wants structured requirements gathering for a document.

m0rtalphe0nix Bundle

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