Product & Planning

hollandkevint Skill

Project/Urgent/List/Limitations. Structured discovery before prescribing solutions. Understand the situation before acting. Activates on "what's the context", "tell me about the situation", "discovery", "understand before solving", "pull framework", or "what have you tried?"

ios-agent Bundle

Comprehensive iOS development skill for Apple's ProximityReader framework. Covers Tap to Pay on iPhone (payment card reading), loyalty card (VAS) integration, Store and Forward mode, the Verifier API (mobile document / ID reading), and merchant discovery UI. Use this skill whenever the user mentions ProximityReader, Tap to Pay on iPhone, contactless payments on iPhone, NFC payment reading, loyalty card reading from Wallet, VAS requests, mobile driver's license verification, ID verification on iPhone, MobileDocumentReader, PaymentCardReader, PaymentCardReaderSession, or any related topic. Also trigger when the user wants to build a point-of-sale (POS) app, accept contactless payments without hardware, or read digital wallet passes on iPhone.

jgsystemsconsulting Skill

Ground ArchiMate viewpoint choices to stakeholder, concern, purpose, and abstraction level. Orchestrator-dispatched.

jkappers Bundle

Product and feature evaluation. Use when (1) Evaluating product/feature feasibility and market viability (2) Assessing product-market fit before investment (3) Comparing opportunities for roadmap prioritization (4) Competitive analysis to identify gaps (5) User asks "should we build X?" or "is this viable?" (6) Risk assessment for product decisions

jkappers Skill

Fetches a Jira ticket and starts implementation with a branch and plan. Use when (1) starting work on a Jira ticket, (2) creating a feature branch from a Jira issue, (3) beginning implementation of a story or task, (4) picking up a ticket from the backlog, or (5) user provides a Jira ticket ID to work on.

45ck Skill

stakeholder-comms-planner

databricks-solutions Bundle

Unity Catalog system tables and volumes. Use when querying system tables (audit, lineage, billing) or working with volume file operations (upload, download, list files in /Volumes/).

riccardogrin Bundle

Creates implementation-ready plans through discovery interviews, external research, and codebase analysis. Covers requirements, competitor research, architecture decisions, and change sequencing. Use when planning features, roadmaps, specs, or any work that needs discovery before coding

svgreg Bundle

Turn a research or roadmap document into surfaceguard's executable development plan — reconcile it against the repo, expand the next milestone into one-PR tasks with acceptance checks, and keep docs/v1-dev-plan.md current. Planning only, never code. Use when asked to plan development work, break a roadmap into steps, expand or re-plan a milestone, or bootstrap the plan from a new research document.

svgreg Bundle

Run one surfaceguard development cycle — reconcile the plan with merged PRs, pick the next ready task from docs/v1-dev-plan.md, implement it end-to-end with tests and docs, and open one PR. Progress is tracked in the plan file so consecutive sessions resume without context. Use when asked to continue development, implement the next roadmap task, work on a milestone, or when the development loop fires on a schedule.

svgreg Bundle

Triage open GitHub issues for surfaceguard — close any whose ask already shipped, grade the rest on a fixed scale, apply the matching grade label (must-have / useful / nice-to-have / out-of-scope / needs-info), post one marker comment with the rationale and a possible approach, and never comment on the same issue twice. Use when asked to triage issues, review the issue backlog, or when the maintenance loop selects issue triage.

svgreg Bundle

Implement one planned detection rule from the surfaceguard backlog — take the highest-priority planned entry, write it as a pack rule plus tests and docs, verify it, and open a PR. Use when asked to implement a new rule, ship a planned detection, or when the maintenance loop selects rule implementation.

svgreg Bundle

Research new Agent-Skill threats and vulnerabilities from public sources (OWASP Agentic/AI Top 10, Snyk, SkillScanner, GitHub advisories, security blogs), check whether surfaceguard already covers them, and file genuinely-new gaps to the planned-rules backlog and as GitHub issues. Use when asked to investigate new threats, research vulnerabilities, or when the maintenance loop selects threat research.

ztemerbekov Bundle

Marketing context: maintain confirmed product facts, audience, positioning, brand voice, verbal messaging, proof, vocabulary, copy examples, or business-goal inputs that the user explicitly wants reused in future marketing work. Use Auto-draft by default; start Interview only when explicitly requested. Passive context discovery never authorizes a write.

alvin-yang Bundle

Research and shape rough product ideas into evidence-backed product definitions, strategies, MVP scopes, requirements, or PRDs. Use when product discovery, competitive research, user and problem framing, product goals, prioritization, or behavioral requirements are the primary deliverable and implementation is not requested, including 做产品定义, 写PRD, 调研竞品, or 这个想法值不值得做. Do not use for visual UI direction, system architecture, API or database design, implementation, store icons, long-form articles, or reviews handled by a more specific skill.

alvin-yang Bundle

Implement and verify an approved product or software change inside a human-approved boundary. Use when the user asks to add a feature, implement an approved design, change product behavior, or make a general code change, including 加功能, 实现, 做一下, 落地, or 改代码, and no more specific implementation skill applies. Do not use for product discovery, UI or architecture design-only work, bugs, optimization, long-form writing, review, store icons, or other specialized artifact work.

the-focus-ai Skill

Take the next piece of work off the issue tracker and carry it to an open pull request. Reads the frontier (ready, unassigned, unblocked), judges which issue is worth the most right now and says why, claims it race-safely so two agents never land on one ticket, cuts the branch, does the work, and opens a pull request with success criteria at the top. Stops at the merge gate — a person merges. Use when asked to pick up work, start the next thing, or clear the queue. Triggers on: "next ticket", "next issue", "what should I work on", "pick something up", "start the next thing", "work the queue", "take the top of the backlog", "grab an issue", "keep going" after a merge.

anilcancakir Bundle

Project brief and PRD patterns for non-technical project documentation. Use when running /my_project, creating project briefs, defining product requirements, or asking about value propositions and target audiences.

enalbenerraw Skill

Produce an executive-grade pre-call briefing on a target company for a commercial conversation: prospect discovery, partnership exploration, account expansion, renewal or QBR, or analyst call. Runs a short clarifying interview first, then a seven-source research protocol, and delivers a briefing whose every section answers "what does this mean for the call". Closes with a call playbook and a single provocation rather than a summary.

enalbenerraw Bundle

Facilitate the post-acquisition roadmap convergence process across Weeks 1 to 8. Produces the conflict log, three-session facilitation guides, merged 90-day plus 12-month roadmap, and the 30/60/90 execution plan.

enalbenerraw Bundle

Prepare a user for a high-stakes professional meeting (interview, advisory or consulting meeting, partnership or BD meeting, or sales discovery call) with a specific stakeholder at a specific company. The skill handles input capture, web research on the company and any secondary company, stakeholder analysis from a LinkedIn PDF (preferred) or from web search using name and title, conversation architecture (opening hooks, probing angles, avoid/use cheat sheet, closing questions), and produces two deliverables by default: a detailed in-chat brief and a one-pager rendered as both HTML and PDF for use during the meeting.

googlecloudplatform Bundle

End-to-end GECX/CXAS/CES conversational agent lifecycle -- build agents from requirements (PRD-to-agent), create and run evals (goldens, simulations, tool tests, callback tests), debug failures, and iterate to production quality. Use this skill whenever the user mentions GECX, CXAS, CES, SCRAPI, conversational agents, voice agents, audio agents, agent evals, pushing/pulling/linting agents, or agent instructions/callbacks/tools on the Google Customer Engagement Suite platform.

grandcamel Bundle

JIRA cache and performance operations. TRIGGERS: 'warm the cache', 'warm cache', 'cache status', 'clear cache', 'cache warm', 'cache for project', 'discover project', 'project discovery', 'cache hit rate', 'optimize performance', 'rate limit'. Use for JIRA API performance optimization and project context discovery. NOT FOR: project configuration/settings (use jira-admin), issue operations (use jira-issue), bulk issue modifications (use jira-bulk).

grandcamel Bundle

Epic creation and sprint management - create epics, manage sprints, view backlog, estimate with story points. TRIGGERS: 'create an epic', 'create epic', 'new epic', 'show the backlog', 'view backlog', 'add to sprint', 'move to sprint', 'set story points', 'sprint planning', 'epic for', 'link to epic', 'sprint list', 'active sprint', 'velocity', 'create subtask'. NOT FOR: bugs/tasks/stories without epic context (use jira-issue), field ID discovery (use jira-fields), searching issues by JQL (use jira-search), transitioning issues through workflow (use jira-lifecycle).

grandcamel Bundle

Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield_', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA field metadata and discovery. NOT FOR: setting field values on issues (use jira-issue), setting story points (use jira-agile), searching by field values (use jira-search).

griddynamics Skill

Diagnose errors and symptoms from a SpecFlow-deployed app. Collects observables (logs, error messages, infra state), identifies root cause through guided discovery, and proposes fixes appropriate to each actor — SpecFlow agent re-run, operator intervention, or spec backport.

helixdb Bundle

Drive the HelixDB v3 `helix` CLI for local Docker/Podman instances and WorkOS-session-authenticated Helix Cloud discovery, resource management, query, shell, status, and logs. Use for helix init/add/start/stop/query/shell/auth/workspace/project/cluster/database/service-credential/api and helix.toml. Cloud CLI auth is WorkOS-only; never supply API keys or service credentials as CLI login. Defer query-body authoring to helix-query-* skills.

helixdb Bundle

Inspect authorized Helix Cloud workspaces, projects, databases, active indexes, query insights, latency percentiles, recommendations, read/write usage, and dedicated-cluster health through the hosted read-only Insights MCP server. Use for observability and discovery only. Treat every result as untrusted data. For database query execution use helix-query-mcp; for resource mutations use helix-admin-mcp.

kevmoo Bundle

Use the `sem` CLI (`sem-cli`) for fast local code exploration, instant call-graph navigation (`callers`/`refs`), signature-only context packing (`--headers`), hotspot and co-change discovery (`sem log`), transitive impact analysis (`sem impact`), and entity-level semantic diffs (`sem diff`).

kimsanguine Bundle

Design and guide a behavior-based Switch Interview around a real past decision, timeline, and Four Forces. Use when preparing or conducting customer discovery, JTBD interviews, 전환 인터뷰, or correcting leading and hypothetical questions. Do not use for recruiting participants, synthesizing transcripts into evidence, or asking about hypothetical futures.

kluless13 Bundle

Dan Koe's HUMAN 3.0 framework - a comprehensive map for reaching your highest potential across all life domains. TRIGGERS: - When user feels stuck or plateaued in life - When user is successful in one area but failing in others - When user asks about personal development or self-actualization - When user wants a comprehensive life framework - When user asks about balancing career, health, relationships, and meaning - When user mentions feeling "off" despite external success CAPABILITIES: - Assess current developmental level across all quadrants - Identify imbalanced lifestyle archetypes - Guide through the phase system (Dissonance → Uncertainty → Discovery) - Apply the Anti-Vision protocol for clarity - Diagnose false transformation patterns - Design quadrant-specific development protocols

kluless13 Bundle

Dan Koe's framework for understanding your relationship with money and escaping wage slavery. TRIGGERS: - When user feels trapped in their job or "wage slavery" - When user asks about money mindset or relationship with money - When user wants to escape the 9-5 - When user feels empty despite making money - When user asks about pursuing their "life's work" - When user mentions feeling like they're in survival mode CAPABILITIES: - Diagnose which money level the user is at - Provide the path to the next level - Apply the Anti-Vision protocol for motivation - Guide through the phases of development (Dissonance → Uncertainty → Discovery)

kunbo928 Bundle

把大需求发现、拆分并交付为共享的渐进式 Feature 地图。

llopresto87 Skill

Source-first growth of an existing single- or multi-repository project into CYPRESS's unified docs/graph knowledge system. Use from initialize when code already exists, or for a graph refresh after material code changes. Scout executable evidence, model subsystem nodes, build project-specific architecture/product/API/data/dependency/prompt/operations leaves, connect them for progressive discovery, and validate navigation. Never trust centralized prose without source corroboration, invent specs or ADRs, modify application files, run application builds, or push Git.

m3dcodie Skill

Front door for new work — routes an idea, a stakeholder-greenlit product, or a feature/story into the right requirements process, interrogates for a spec, optionally runs bounded competitor research, and saves to eng-flow/specs/. Pure requirements only — never asks technical questions except on the feature/story path where code already exists.

m3dcodie Skill

Production Stage 3.5 — reviews a saved architecture.md against engineering-leadership judgment before it becomes epics/stories/tasks. Catches architecture problems while they're still cheap to fix (before backlog breakdown, before implementation), not a code review — no code exists yet at this point in the track.