Product & Planning

m0m0i Skill

Write the technical design — the architecture, the seams between components, and the decisions worth recording as ADRs. Use after the PRD and before the backlog, or when a capability needs a design bigger than one spec.

nangongwentian-fe Bundle

Review a completed or nearly completed non-trivial task and directly maintain durable lessons across project docs, memory, existing skills, or new skills without asking for separate confirmation. Use after complex debugging, deployment, live verification, repo documentation work, repeated workflow discovery, creating or updating a skill, or when the user asks whether anything is worth remembering, updating, or deleting.

opskat Bundle

opskat CLI for asset management and remote operations (SSH, databases, Redis, MongoDB, Kafka, Kubernetes, etcd, file transfer). Use when: managing server assets, executing remote commands, writing opsctl scripts/automation, or working with approval workflows and permission rules. Also triggers for: deploying to servers, server diagnostics/troubleshooting, batch operations across fleet, database queries, file transfers between servers, server inventory/discovery.

owid Bundle

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

palashjain95 Bundle

This skill should be used when the user asks to "find me roles", "what should I apply to", "search for jobs", "discover roles", or "what's out there". Searches across job boards, company careers pages, and the web for roles matching the candidate's profile. Surfaces hidden gems and triages by fit. Supercharged with ~~jobs for multi-platform search and ~~search for semantic discovery.

pedroromeroluna Skill

Interview the operator and write the strategic layer of a product —vision, problem, users, scope, competitors, opportunities, open questions, glossary— into the `context/` of its node in the brain, never into the body repo. Manually triggered, last link of the discovery pipeline and the gate before specs.

pedroromeroluna Skill

Pressure the facts behind a claim before a decision closes — counter-question with a concrete example, capped attempts, escape hatches, evidence hierarchy — and route what comes out to the loaded node's decisions or backlog. Manually triggered, and also the method any other interviewing tool cites by path.

pedroromeroluna Skill

Design one research round against the single riskiest hypothesis — behavioral screening, one modality chosen on purpose, a guide whose every question is tied to a hypothesis or a job dimension — and write the Research Plan as dated research of the loaded product node. Manually triggered, third station of the discovery pipeline.

pedroromeroluna Skill

Converge the raw answers of real fieldwork —clusters with their noise and their outliers, jobs to be done in three dimensions with two verbatims each, the customer profile, opportunities scored against the business outcome— and write the Insight Brief as dated research of the loaded product node. Manually triggered, fifth station of the discovery pipeline: the first one that runs after real fieldwork.

pedroromeroluna Skill

Run the solution space in two modes — DIVERGE prepares the workshop (traceable How Might We, seed ideas sealed until the humans have ideated, a timeboxed agenda and the board written zone by zone) and CONVERGE reads what the team produced and voted and writes the Value Map plus the prototype brief. Manually triggered, sixth station of the discovery pipeline; it never picks the winning idea.

pedroromeroluna Skill

Size the opportunity with secondary research only — directional TAM/SAM/SOM where every number carries its cited source and the assumption that turns it into a number for this product — and write the Market Brief as dated research of the loaded product node. Manually triggered, second station of the discovery pipeline.

pedroromeroluna Skill

Pilot the v1 research guide against synthetic personas —every trait marked as evidence or assumption, at least one skeptic— to find broken questions before spending real fieldwork, and write the Diagnosis + Script v2. Manually triggered, fourth station of the discovery pipeline; it validates nothing.

pedroromeroluna Skill

Run the socratic discovery interview that separates the symptom from the cause, grades the evidence, applies the metric gate and prioritizes up to three hypotheses, and write the Discovery Brief as dated research of the loaded product node. Manually triggered, first station of the discovery pipeline.

pssah4 Bundle

One entry point for repos that predate current DIA conventions: brownfield onboarding (existing codebase, legacy code, reverse engineer, we already have code) and legacy DIA upgrades (migrate v1/v2, upgrade DIA, FEATURE to FEAT, restructure backlog). Detects repo state, then runs a reverse walk, a script pass, or a gap walk.

pssah4 Skill

Verifies the V-Model artifact graph: Epics, Features, ADRs, PLANs, Backlog, Wayfinder rows, code refs. Syntactic and semantic modes. Explicit user command for "consistency check", "graph check", "dead links", "orphan features", or before a release; routine enforcement runs via the pre-commit hook, not per phase.

reopt-ai Bundle

Design and implement production-grade product event instrumentation with the reopt Data SDK in a consumer app, from journey discovery and measurement planning through typed contracts, browser/server delivery, consent, catalogue-as-code, tests, and live verification. Use for "instrument events", "analytics measurement plan", "reopt event taxonomy", "data SDK integration", "이벤트 설계", "이벤트 심기", "데이터 SDK 연동". Use data-sdk-review instead for a read-only audit.

rfxlamia Bundle

BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.

arenukvern Bundle

Generic contract/schema boundary audit across authoring, discovery, validation, and execute—detecting split-brain between listings and invoke paths, gateway divergence, and permissive placeholders. Use when changing tool registration, RPC/plugin registries, dynamic tools, MCP or WebMCP surfaces, CLI exec aliases, OpenAPI or JSON Schema contracts, migrators/codegen, bridge argument encoding, or platform docs that describe API contracts.

arenukvern Skill

Use this skill when the agent exposes app-specific surfaces by registering custom MCP tools and resources inside the Flutter app (mcp_toolkit dynamic registry — AgentCallEntry, bootstrapFlutter additionalEntries / addEntries). Covers tool vs resource vs evaluate-expression, Map-based handlers, schema strictness, discovery via fmt_list_client_tools_and_resources, fmt_client_tool, fmt_client_resource, and lifecycle pitfalls.

elsa-workflows Bundle

Refresh the Elsa roadmap from current evidence. Use when Codex needs to update ROADMAP.md or the public roadmap issue by researching elsa-core, elsa-studio, and elsa-extensions source code, specs, releases, commits, issues, pull requests, and discussions; classify shipped foundations, partial/productization work, roadmap candidates, stale items, and recommendations; then update the roadmap checklist and GitHub issue coherently.

majesteitbart Bundle

Define and approve a measurable outcome and Spec. Use when a new delivery request has unclear scope, missing outcome, or missing owner.

vobase Bundle

Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

githubmofo Skill

Master 7-stage security pipeline orchestrator — coordinates discovery, authorization, static audit, runtime validation, governed remediation, recheck, and reporting.

opsmill Skill

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → opsmill-dev-creating-issues; the idea has not been stress-tested yet → opsmill-dev-grilling-ideas first; bug reports.

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 → opsmill-dev-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 → opsmill-dev-creating-prd; the idea is still fuzzy and unhardened → opsmill-dev-grilling-ideas first.

vercel-labs Skill

Emulated Sign in with Apple / Apple OIDC for local development and testing. Use when the user needs to test Apple sign-in locally, emulate Apple OIDC discovery, handle Apple token exchange, configure Apple OAuth clients, or work with Apple userinfo without hitting real Apple APIs. Triggers include "Apple OAuth", "emulate Apple", "mock Apple login", "test Apple sign-in", "Sign in with Apple", "Apple OIDC", "local Apple auth", or any task requiring a local Apple OAuth/OIDC provider.

vercel-labs Skill

Emulated Google OAuth 2.0, OpenID Connect, Gmail, Calendar, and Drive for local development and testing. Use when the user needs to test Google sign-in locally, emulate OIDC discovery, handle Google token exchange, configure Google OAuth clients, work with Gmail messages/drafts/threads/labels, manage Calendar events, upload or list Drive files, or work with Google userinfo without hitting real Google APIs. Triggers include "Google OAuth", "emulate Google", "mock Google login", "test Google sign-in", "OIDC emulator", "Google OIDC", "Gmail API", "Google Calendar", "Google Drive", "local Google auth", or any task requiring a local Google API.

vercel-labs Skill

Emulated Microsoft Entra ID (Azure AD) OAuth 2.0 / OpenID Connect for local development and testing. Use when the user needs to test Microsoft sign-in locally, emulate Entra ID OIDC discovery, handle Microsoft token exchange, configure Azure AD OAuth clients, work with Microsoft Graph /me, or test PKCE/client credentials flows without hitting real Microsoft APIs. Triggers include "Microsoft OAuth", "Entra ID", "Azure AD", "emulate Microsoft", "mock Microsoft login", "test Microsoft sign-in", "Microsoft OIDC", "local Microsoft auth", or any task requiring a local Microsoft OAuth/OIDC provider.

xgent-ai Bundle

以资深产品经理视角把一个想法/诉求梳理成可被 SPMS 生命周期管理的需求——项目级「概述/目标/非目标」+ 逐条 FR/NFR（含可断言的验收标准与测试用例种子），产出 PRD 文档并写入 SPMS，作为 dev-plan 的前置输入。凡用户要求「写 PRD / 写需求文档 / 梳理需求 / 拆需求 / 提需求 / 需求评审 / 把这个想法变成需求 / 录入需求」，或给出一段业务诉求并期望先把「做什么、为什么、怎样算做完」定清楚时，务必使用本 skill——即使用户没说「PRD」三个字。正文按终局全景写,分期交付建议只在末尾一次给出并逐条标明终验期,避免把阶段交付误记为整条需求已完成。Use whenever the user wants requirements written, clarified, decomposed, or filed into SPMS (FR/NFR) before any implementation planning happens; the body states the full target scope, and a final section proposes delivery phases carrying each requirement's final-acceptance phase.

xgent-ai Skill

把一个技术主题、或一份技术文档（PRD、开发计划、技术方案、评审纪要）讲成任何背景的读者都能看懂并复述出来的 HTML 文档——大图示、显眼的关键数字、带图例的图表、表头带释义的表格、尽量少的术语。凡用户输入 /elintp <主题或文档>，或要求「讲得通俗一点 / 把这份 PRD 讲成人话 / 写给业务同事看的说明 / 给不做研发的同事解释这个系统」时使用。Use when the user types /elintp <topic-or-document>, or asks for a plain-language explainer or restatement of a technical document aimed at readers outside the engineering team.

xgent-ai Bundle

由需求（PRD 正文 + 验收标准）成套产出测试用例草稿并写入 SPMS（TC-N，关联需求），覆盖正常路径/边界/权限/并发四类，逐条验收标准给出「标准 → 用例」映射,写入前先查重。凡用户要求「补测试用例 / 写测试用例 / 出测试计划 / 这条需求要怎么测 / 覆盖一下验收标准 / 测试用例够不够」时，务必使用本 skill——即使用户没说「用例」两个字。Use whenever the user wants test cases written, test coverage expanded, or a test plan derived from SPMS requirements and filed as TC-N via the PMS MCP tools.

y3owk1n Bundle

Create, derive, or update the PRD — the single source of truth every other skill reads.

y3owk1n Bundle

Render a PRD feature file to a spec issue and cut its ticket sub-issues in one pass.

y3owk1n Skill

Structured interview to sharpen a plan or design, then emit a PRD delta.

y3owk1n Bundle

Write and prune documents agents read: SKILL.md, CLAUDE.md, AGENTS.md, prd/ files.