Product & Planning

u1pns Skill

Acts as a Lead Technical Product Manager. Use this skill when the user needs to define requirements, write a PRD, map user flows, or specify features. Triggers: 'create PRD', 'write specs', 'user stories', 'functional requirements', 'define scope', 'product roadmap'.

u1pns Skill

Acts as a Technical Project Manager. Use this skill when the user needs to break down a project into tasks, plan a sprint, or organize a backlog. Triggers: 'create tasks', 'sprint planning', 'break down features', 'make a plan', 'project management', 'ticket generation'.

rivie13 Skill

Navigate the Website Frontend roadmap, understand current phase status, plan next tasks, and track what needs to be done. Use when user asks what to work on next, current project status, phase progress, roadmap, task planning, or what's left to do.

rivie13 Skill

Update Copilot instruction files to reflect current project state, architecture, phase progress, or conventions. Use when user asks to update instructions, refresh copilot context, sync instruction files with current reality, or update architecture/roadmap documentation in instruction files.

rivie13 Skill

Load Website Frontend repo instruction files into context. Use when working on website frontend code and needing coding conventions, build instructions, project structure, architecture, roadmap, or strategy context for the public website UI.

tomfordrumm Bundle

Turn a confirmed Product Brief or an existing web application into implementation-ready product documentation and vertical delivery slices, scaled for a prototype, lean working product, or production release. Use for PRDs, MVP plans, durable agent handoffs, or reconciling project documents with existing code. Do not use for initial idea discovery, market research, or implementation.

tomfordrumm Bundle

Turn an early product idea into a clear Product Brief through an adaptive interview. Use when a user needs help defining the problem, intended users, main journey, first-version scope, constraints, and success criteria before a PRD or implementation. Do not use for architecture, stack selection, market validation, or coding.

pnp-copilot-prompts Bundle

Reviews a given week of your OWN Teams meetings, chats, and sent emails to surface moments where you may have misread social signals or come across as passive-aggressive, curt, sarcastic, or dismissive — returning the exact quote, how it likely landed, and a kinder rewrite. Private self-reflection coaching for the signed-in user only. Use when you ask "was I out of line this week?", "did I come across as passive-aggressive?", "did I misread anyone this week?", "how did I come across?", "review how I came across", "check my tone this week", or "was I the difficult one?". Defaults to the current week; accepts any week. Do NOT use to evaluate, rank, or critique OTHER people — use meeting-intel for neutral meeting summaries, daily-briefing for a schedule overview, or stakeholder-comms to draft a message. This skill only ever analyzes your own words.

llm-coding Bundle

Recover the "theory" (Naur 1985) of an existing codebase through recursive question refinement before writing documentation. Use on brownfield projects where the spec is missing — produces a Question Tree separating what is answerable from code (with evidence) from what must be asked of the team (routed by role). Phase 1 builds the tree; team answers the OPEN leaves; Phase 2 synthesizes PRD, Cockburn use cases, arc42 architecture, and Nygard ADRs from the answered tree.

nbbaier Bundle

Turn a working session — the docs, issues, and half-formed ideas you've fed in, plus anything you point it at — into a spec and then a set of self-contained, executable implementation plans for OTHER models/agents to build. A senior architect that plans but never implements. Use when you have that context in hand and want it distilled into a PRD-style spec and broken into dependency-ordered, verifiable work items. Publishes to the repo's configured issue tracker or to markdown files.

mvdmakesthings Skill

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

mvdmakesthings Skill

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

shareai-lab-kode Bundle

A structured workflow for co-authoring high-signal docs (PRD, RFC, design docs, proposals, decision records). Use when the user needs to turn messy context into a readable artifact with clear goals, tradeoffs, and next steps. Emphasizes context capture, outline-first drafting, and context-free reader testing to catch blind spots.

endlessblink Skill

Safe MASTER_PLAN.md management with backup, validation, and intelligent updates. Use when updating task tracking, adding features to roadmap, or modifying project documentation.

jason-chen-coder Bundle

Clarify feature requirements, pressure-test scope and domain terms, and produce a feature spec before implementation. Use for fuzzy requirements, PRD/spec requests, 需求对齐, 拷问需求, or 设计文档. Read existing evidence before asking focused questions. For concrete implementation planning use dev-plan; a generic "do not edit code" instruction alone does not trigger intake. Supports --quick, --deep, and --spec-only.

runtypelabs Bundle

Compose and expose agent toolsets: task-level operations, batching, discovery, dry runs, and versioning.

lewing Skill

Query Maestro/BAR dependency flow data using the mstro CLI tool via bash. USE FOR: subscription health checks, build flow tracing, codeflow status, channel discovery, triggering subscription updates — when MCP tools aren't loaded or when scripting with JSON output and jq. Also use when investigating "is this subscription stale", "what's the latest build", "check backflow status". DO NOT USE FOR: tasks where maestro MCP tools are already available in context (prefer flow-analysis or flow-tracing skills when MCP server is loaded). INVOKES: bash (mstro CLI commands with --json output).

xpozpublic Skill

Find and rank influencers by niche, engagement, and authenticity using Xpoz. Searches Twitter, Instagram, and Reddit for active voices in any topic. Use when asked to "find influencers", "discover thought leaders", "who's talking about X", "influencer research", or "find KOLs".

rivie13-phoenix-agentic-engine-interface Skill

Navigate the Phoenix project roadmap, understand current phase status, plan next tasks, and track what needs to be done. Use when user asks what to work on next, current project status, phase progress, roadmap, task planning, or what's left to do.

rivie13-phoenix-agentic-engine-interface Skill

Load Interface repo instruction files into context. Use when working on Interface SDK code and needing coding conventions, build instructions, project structure, architecture, roadmap, or strategy context for the TypeScript SDK.

rivie13-phoenix-agentic-engine-interface Skill

Update Copilot instruction files to reflect current project state, architecture, phase progress, or conventions. Use when user asks to update instructions, refresh copilot context, sync instruction files with current reality, or update architecture/roadmap documentation in instruction files.

pcatattacks Bundle

Write a product specification (PRD) from a validated idea or feature request. Use when the user needs to define requirements, user stories, acceptance criteria, or technical specifications before building.

pcatattacks Bundle

Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.

pcatattacks Bundle

Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.

assimovt Skill

Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria.

assimovt Bundle

Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.

assimovt Skill

Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.

assimovt Skill

Synthesize user research into actionable insights using atomic research methods. Use when asked to synthesize research, organize user feedback, find patterns in interviews, summarize customer discovery, or turn raw notes into insights and recommendations.

assimovt Skill

Map opportunities using Teresa Torres' Opportunity Solution Trees. Use when asked to identify opportunities, find product gaps, explore new areas, map the solution space, or connect business outcomes to customer needs and testable solutions.

assimovt Skill

Prioritize features and backlog items using RICE scoring and Linear's enablers vs blockers lens. Use when asked to rank features, prioritize a backlog, decide what to build next, or evaluate feature requests against each other.

46ki75 Bundle

Expert guidance for the A2A (Agent2Agent) Protocol — an open HTTP-based protocol for independent, opaque AI agents to collaborate as peers. Covers v1.0: data model (Agent Card, Task, Message, Part, Artifact, Extension); operations (`SendMessage`, `SendStreamingMessage`, `GetTask`, `ListTasks`, `CancelTask`, `SubscribeToTask`, the `*TaskPushNotificationConfig` family, `GetExtendedAgentCard`); task lifecycle and multi-turn flows; three protocol bindings (JSON-RPC, gRPC, HTTP+JSON/REST) and custom bindings; agent discovery (well-known URI, registries, signed Agent Cards); enterprise security (TLS, OAuth 2.0 / OIDC / mTLS, in-task authorization); SSE streaming and webhook push notifications; the extension framework; A2A↔MCP relationship; and the six SDKs (`a2a-python`, `a2a-js`, `a2a-java`, `a2a-go`, `a2a-dotnet`, `a2a-rs`). Always invoke for A2A, Agent2Agent, agent card, A2A tasks / messages / artifacts / parts, push notification configs, A2A extensions, Agent Card signing, or any of the six SDK package names.

46ki75 Bundle

Expert guidance for AG-UI (Agent–User Interaction Protocol) — the open, event-based protocol connecting AI agents to user-facing apps. Covers the run lifecycle, event types (lifecycle, text, tool-call, state, activity, reasoning), RunAgentInput, AbstractAgent/HttpAgent, multimodal messages, shared state via STATE_SNAPSHOT/STATE_DELTA (RFC 6902 JSON Patch), frontend-defined tools, interrupt-aware HITL with RunAgentInput.resume, encrypted reasoning for ZDR, capability discovery, middleware, serialization with parentRunId branching, the TypeScript (`@ag-ui/client`, `@ag-ui/core`) and Python (`ag-ui-protocol`) SDKs plus community SDKs. Use whenever someone builds or consumes AG-UI, wires up CopilotKit, LangGraph, CrewAI, Mastra, Pydantic AI, LlamaIndex, Agno, AG2, Microsoft Agent Framework, Google ADK, AWS Strands, or Bedrock AgentCore, or mentions AG-UI, ag_ui, RunStartedEvent, STATE_DELTA, TOOL_CALL_START, REASONING_*, AbstractAgent, HttpAgent, or EventEncoder. Always invoke.

atm301 Bundle

行銷策略總監 Kevin — 商業策略、KPI 規劃、客戶提案、新品上市、競品分析。Use when user mentions 策略/strategy/KPI/目標/goal/roadmap/提案/pitch/新品/launch/季度/Q2/Q3/競品/positioning, or asks for 商業決策 or 策略定調. 15 年 4A + 新創資歷，講話有條理會挑戰假設，重視 ROI 與可執行性。

atm301 Bundle

產品經理 Peter (PM) — PRD、MVP 切片、功能排序、砍需求、user story。Use when user mentions PRD/MVP/spec/roadmap/user story/驗收/acceptance/scope/功能優先序/feature priority/這個功能, or asks to 砍需求 or 評估值不值得做 or 寫 PRD or 排 roadmap. YAGNI 信徒，怕過度設計，問「不做會死嗎？」

ameen-alam Bundle

This skill conducts discovery conversations to understand user intent and agree on approach before taking action. It should be used when the user explicitly calls /interview, asks for recommendations, needs brainstorming, wants to clarify, or when the request could be misunderstood. Prevents building the wrong thing by uncovering WHY behind WHAT.

microsoft Skill

Analyze your email patterns over a time period — volume trends, top senders, response time estimates, busiest days, and unread backlog statistics.