Product & Planning

jacardl Bundle

从 AI 回答文本中高精度识别目标品牌的竞品，支持知识库持久化和增量积累。当用户粘贴 AI 平台回答并要求识别竞品、分析某品牌竞争格局、从回答中提取竞品信息时触发。也适用于：持续追踪某一品牌的竞品变化、多平台 AI 回答批量竞品分析。

jacardl Bundle

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

gtmify Bundle

Account-based planning with stakeholder mapping, persona matching, and coordinated outreach strategy. Use when the user says 'plan for [company]', 'account plan', 'stakeholder map', 'ABM strategy', 'target account plan', or mentions building a coordinated play for a specific named company.

gtmify Bundle

Build a Now / Next / Later prioritized roadmap with effort estimates, dependencies, and the rationale behind ordering. Use when the user says 'build a roadmap', 'quarterly plan', 'prioritize features', 'product roadmap', 'roadmap update', 'what should we build next', or wants a structured prioritization output.

gtmify Bundle

Categorize, prioritize, and draft responses for an email backlog. Use when the user says 'triage my inbox', 'help with email', 'inbox zero', 'catch up on email', 'email backlog', 'draft responses', or pastes email content for prioritization and response drafting.

gtmify Bundle

Build a strategic plan for a specific deal or opportunity — stakeholder mapping, decision process, competitive positioning, and next plays. Use when the user says 'deal strategy', 'account plan', 'how do I win this deal', 'stakeholder map', 'deal review', 'opportunity plan', 'MEDDIC this deal', or asks for help strategizing a specific active opportunity.

ch4570 Bundle

Quickly find unreferenced dead-code candidates with file/line evidence and confidence. Use for unused functions, classes, exports, files, or 참조 없는 죽은 코드 탐색. Read-only discovery; excludes code deletion and general refactoring.

ch4570 Bundle

Markdown 문서를 편집 가능한 원본과 함께 오프라인 단일 HTML로 발행하고, 요청 시 로컬 Chromium 계열 브라우저로 PDF를 생성한다. 기술 문서, PRD, 메모, 보고서에 executive/technical/minimal 테마를 적용하거나 Markdown을 인쇄 가능한 HTML/PDF로 변환할 때 사용한다. PDF 완료 판정과 페이지별 시각 검수는 pdf-qa로 라우팅한다.

ch4570 Bundle

Record the fail-closed compatibility status of legacy Vulpora catalog-agent execution. This installable negative-contract skill must not run agents, discovery probes, or delegated tasks.

ch4570 Bundle

제품 아이디어, 기능 제안, 사용자 문제를 구현 가능한 제품 요구사항 문서(PRD)로 구체화한다. 제품 범위와 사용자 흐름을 정리하고, 관찰 가능한 기능 요구사항과 Given/When/Then 인수 기준을 연결하거나, 개발 handoff를 준비해야 할 때 사용한다. 아이디어 자체를 구현·배포하거나 외부 시스템을 변경하는 작업에는 사용하지 않는다.

andurilcode Skill

Apply scenario planning whenever the user is making long-term decisions, building roadmaps, evaluating strategies, or operating in an environment with significant uncertainty about how the future will unfold. Triggers on phrases like "what should our roadmap look like?", "how do we plan for the future?", "what if things change?", "we're not sure which direction the market will go", "how do we make this strategy resilient?", "what's our plan B?", "what are the different futures we could face?", or when a plan assumes a single future state. Also trigger when someone is over-committed to one expected outcome and hasn't stress-tested the strategy against alternative futures. Don't plan for one future — plan for multiple.

andurilcode Skill

Apply execution-planning whenever the user has made a decision and needs to turn it into action — decomposing work, sequencing tasks, estimating timelines, and assigning ownership. Triggers on phrases like "how do we execute this?", "break this into tasks", "what's the project plan?", "create a roadmap", "what are the dependencies?", "who does what by when?", "how long will this take to build?". Use proactively after decision-synthesis or architecture-evaluation produces a committed decision that requires coordinated implementation.

andurilcode Skill

Apply stakeholder and power mapping whenever the user is navigating organizational decisions, driving change, launching a product, building alignment, or trying to understand why something keeps getting blocked. Triggers on phrases like "why won't people adopt this?", "who do I need to convince?", "this keeps getting blocked", "how do I get buy-in?", "who are the key players?", "there's political resistance", "how do I manage stakeholders?", "who has influence here?", "someone is sabotaging this", or any situation where human actors, organizational dynamics, or change management are involved. Also trigger when a technically sound plan is failing for non-technical reasons — the real constraint is often human, not systemic. Never skip this skill when organizational change or adoption is involved.

openyida Bundle

宜搭完整应用开发编排技能。对普通 OpenYida 应用做完整搭建或补齐时使用；先确认已有资源并整理用户需求，再按 Fast / Plan 生成 prd.md 与 design.md，校验通过后按 PRD 创建或复用应用、表单、流程和页面；页面 UI 按已确认设计实现，代码示例按需参考。

openyida Bundle

基于整理好的需求事实规划业务，生成 prd/<项目名>/prd.md，负责业务、资源、页面、顺序和验收规则。

openyida Skill

按 taskUuid 获取钉钉听记、会议录音转写、会议纪要或 AI 听记的完整详情；只负责读取内容。若用户要求转 PRD，先用本技能取内容，再交给 yida-flash-note-to-prd。

openyida Bundle

从已有钉钉闪记、会议记录或需求文档内容中提取产品需求，生成结构化 PRD。若用户只给 taskUuid，先用 yida-tingji 读取内容，再进入本技能。

openyida Bundle

识别并读取需求来源，理解和澄清用户需求，输出供 PRD 与视觉设计共同使用的需求事实。

topprismdata Skill

Extract reusable knowledge from work sessions into new Claude Code skills. Use when: (1) /claudeception command to review session, (2) "save this as a skill" or "extract a skill", (3) "what did we learn?", (4) After non-obvious debugging, workarounds, trial-and-error discovery, or counterintuitive solutions. Do NOT trigger for routine fixes or straightforward tasks with obvious solutions.

topprismdata Skill

Use when: (1) User says "总结经验", "复盘", "extract methodology", "what did we learn", "抽象智慧", or asks to reflect on a completed project, (2) A non-obvious breakthrough, major failure, or counterintuitive discovery has just occurred, (3) User asks "why does this pattern keep appearing" or "what's the deeper principle here", (4) Before starting a new project when user wants to review past wisdom. Do NOT trigger for routine bug fixes — use claudeception instead.

brandonburrus Bundle

This skill should be used for system and software design: writing a product spec (PRD), a tech spec (system design, design doc), or an ADR (architecture decision record), and for domain design consults: API contracts, database schemas, observability (SLOs, alerts, dashboards), LLM agent architecture, CLI command surfaces, MCP servers, CI/CD pipelines, and migration or deprecation plans. It applies when the user says "PRD", "tech spec", "spec this out", "ADR", "record this decision", "why did we choose X", "design the API", "add an endpoint", "design the schema", "model this data", "define SLOs", "design the alerts", "build an agent", "add an LLM feature", "build a CLI", "build an MCP server", "set up CI", "plan the migration", or "deprecate this". It should not be used for implementation planning (use create-code-plan), ticket slicing (use decompose), persuasive RFCs (use write-proposal), or UI and visual design (use design).

xobotyi Bundle

Language-agnostic coding workflow: discovery, change decomposition, commit sizing, comment and naming policy, and completion evidence.

xobotyi Skill

Requirements elicitation and validation through structured questioning. Invoke whenever task involves defining what to build, scoping a problem or feature, or starting the DRAFT pipeline.

ptreezh Bundle

OKR (Objectives and Key Results) expert. Provides objective setting, key result design, progress tracking, alignment mapping, and OKR cycle facilitation. Suitable for strategic planning, performance management, and goal-setting frameworks.

ptreezh Bundle

Agile Project Management expert. Provides Scrum/Kanban framework implementation, sprint planning, backlog prioritization, team facilitation, and velocity tracking. Suitable for software development, product management, and adaptive project delivery.

wanghaisheng Skill

Design Discovery

jmsktm Skill

Track project milestones with progress monitoring, deadline management, and stakeholder communication

jmsktm Skill

Guide customer discovery interviews and develop customer insight frameworks

notysoty Skill

Systematically identifies edge cases and boundary conditions for any function, API, or user flow.

qte77 Bundle

Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags. Use when checking requirement coverage, finding orphaned code, or generating a coverage matrix.

qte77 Skill

Generate an investor or stakeholder presentation from Phase 5 synthesis; produces a structured slide outline with headlines, talking points, and data citations. Run after `synthesizing-research` (Phase 6).

qte77 Skill

Converts UserStory.md into a structured PRD.md document. Use after generating UserStory.md and before initializing the Ralph loop.

iceflower Bundle

Microservices architecture patterns including service decomposition, communication (sync/async, gRPC), API gateway, Saga, CQRS, event sourcing, transactional outbox, data management, and fault isolation (Circuit Breaker, Bulkhead). Use when designing or reviewing microservice architectures, or implementing distributed transactions, service discovery, or strangler fig migration.

arcadeai Skill

Run a diff-scoped code audit for architecture, dead code, and test quality. Uses the change from main to focus feature reviews; request a repository audit for whole-codebase discovery.

stanestane Bundle

Adversarial design audit that stress-tests a game feature, system, pitch, roadmap item, or product idea by assuming failure and identifying the most credible reasons it would fail. Use when pressure-testing a concept before production, performing a pre-mortem, challenging a feature that sounds good on paper, exposing blind spots in design thinking, or getting a hostile-but-constructive critique with concrete failure mechanisms and de-risking moves.

stanestane Skill

Evaluate game features, feature pitches, live-ops ideas, UX changes, economy changes, roadmap choices, retention initiatives, monetization initiatives, and ambiguous design problems using the GROW model: Goal, Reality, Options, Will. Use when a team needs structure, clearer decision-making, better option generation, explicit tradeoff analysis, or a concrete recommendation and next-step plan instead of circular discussion.