Product & Planning

trecek Skill

Assess whether analytic decisions were pre-specified or post-hoc and whether exploratory/confirmatory norms are aligned. Boundary lens answering "Is this discovery or test, and are norms aligned?"

excatt Skill

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

excatt Skill

Interactive requirements discovery through Socratic dialogue and systematic exploration

sendaifun Skill

Integrate LI.FI for cross-chain swaps, bridging, payments, route discovery, and transfer status tracking across Solana, EVM, Bitcoin, and Sui. Use when building Solana applications or AI agents that need quotes, routes, executable transactions, supported chains/tokens/tools, or cross-chain transfer monitoring.

nodejsmith Bundle

Use when the user says: "spec this out", "help me define what I want to build", "interview me about this idea", "design this change", "write a design doc", or needs to define WHAT and HOW to build something. Proportional discovery interview + codebase investigation → design.md.

willyu1007 Bundle

Create a goal-aligned macro-level roadmap artifact (dev-docs/active/<task>/roadmap.md) by asking clarifying questions and recording assumptions; planning only (no code changes).

nodejsmith Skill

Use when the user says: "wayfinder", "chart this effort", "too big for one session", "multi-session plan", "foggy effort", "progressive discovery", or has a large uncertain effort that needs progressive discovery before planning.

nodejsmith Skill

Use when the user says: "shape this feature", "plan the UX", "design brief", "UX planning". Plan UX/UI for a feature before writing code via structured discovery interview.

agile-v Skill

Converts messy discovery inputs (interviews, feedback, research, tickets) into structured hypotheses, assumptions, and candidate requirements with full traceability.

propane-ai Skill

Get or structure a sales playbook from ~~knowledge base~~ or context. Repeatable motions (who, when, how, assets) for discovery, demo, negotiation, and closing. Trigger with "get sales playbook", "what's our playbook for [motion]", or use the /get-sales-playbook command.

propane-ai Skill

Write structured design briefs with problem statements, design goals, constraints, and success criteria. Use when briefing a feature, scoping design work, aligning with a PRD, or documenting design decisions.

propane-ai Skill

Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics. Use when speccing a new feature, writing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.

propane-ai Skill

Plan sprints and iterations, break down work into tickets, refine backlog, check capacity. Use when planning a sprint, creating tickets from a spec, refining backlog, or writing good ticket titles and acceptance criteria.

propane-ai Skill

Design status reports, research reports, and stakeholder reporting. Use when creating design status updates, research summaries, or UX reports for stakeholders, leadership, or cross-functional teams.

propane-ai Skill

Prioritize design work and align with product roadmap using Now/Next/Later and design-debt frameworks. Use when managing design backlog, reprioritizing design work, or aligning design with product milestones.

propane-ai Skill

Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.

propane-ai Skill

Plan and prioritize product roadmaps using frameworks like RICE, MoSCoW, and ICE. Use when creating a roadmap, reprioritizing features, mapping dependencies, choosing between Now/Next/Later or quarterly formats, or presenting roadmap tradeoffs to stakeholders.

telum-ai Skill

Captures a project learning at discovery. Use when waiting for retrospective risks losing or repeating it.

telum-ai Skill

Creates PRD.md, epics, and E000. Use after required PROMISE artifacts and before any epic work.

telum-ai Skill

Sequences epics, dependencies, and resources. Use after project-plan for multi-team or multi-quarter Platform delivery.

dangeles Bundle

Use when coordinating handoffs between workflows (e.g., skill-editor to programming-pm). Provides the universal handoff schema, validation rules, and workflow discovery conventions.

dangeles Bundle

Use when performing deep literature-review research — review-paper discovery, targeted deep research (15-30 papers per section), recency surveys, and convergence tracking (typically dispatched by lit-pm). NOT for orchestrating the full review (use lit-pm) or sourcing individual quantitative parameters (use researcher).

joaquimscosta Bundle

Synthesize project documentation and codebase into comprehensive roadmap status, gaps analysis, and blockers. Use when assessing project health, identifying blockers, tracking progress, comparing plan vs reality, documenting risks, or planning next milestones. Triggers: "roadmap", "project status", "blockers", "risks", "progress", "next milestone", "gaps", "what's done".

joaquimscosta Bundle

Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.

x-school-academy Skill

Create a comprehensive Product Requirements Document defining complete product behavior, functional and non-functional requirements, and user flows. Use when starting stage 05 (prd) or when user asks to define product requirements or acceptance criteria.

sgcarstrends Bundle

Required reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons, etc.) and query analytics data (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces). Covers HogQL syntax differences from ClickHouse SQL, system table schemas (system.*), available functions, query examples, and the schema-discovery workflow.

b-open-io-prompts Bundle

Explore a running app on randomized unscripted paths to surface new bugs, broken flows, and confusing UX, then file deduplicated tickets. Use for "free roam", "explore the app", "monkey test", "exploratory testing", "find issues I don't know about", or "discovery loop". Respects a never-touch list and blast-radius boundary. Not for scripted regression tests.

x-school-academy Skill

Plan and execute agile development sprints, breaking down product requirements into manageable backlogs with clear acceptance criteria and test plans. Use when starting stage 10 (sprints) or when user asks about sprint planning or backlog creation.

x-school-academy Skill

Complete backlog implementation in feature-driven development. Read backlog requirements, reference implemented features, design approach, implement code, and document. Use when implementing features, changes, bug fixes, or improvements.

ccplugins Bundle

Write up a coding session for a non-technical stakeholder — the context, what was built, and the engineering reasoning behind it — the way a senior engineer briefs a product manager who does not read code. Use ONLY when explicitly invoked, either through the /dev-report slash command or one of its localized aliases (/개발보고 and similar), or when the user directly asks for a stakeholder-facing write-up of the session ("write today up for my PM", "explain this session for a non-developer", "개발 보고서 써줘"). Do NOT trigger on an ordinary "what did you just do?" — that wants a short plain answer, not a report.

b-open-io-prompts Bundle

This skill should be used when the user asks to "add plugin settings", "make a plugin configurable", "store per-project plugin configuration", "use settings.local.json", "create a plugin state file", "expose skill settings in Agent Master", or "add a skill interface". Distinguishes official Claude Code settings from project-owned configuration and documents bOpen Agent Master skill interface discovery.

catlog22 Skill

Intelligent code cleanup with mainline detection, stale artifact discovery, and safe execution. Supports targeted cleanup and confirmation.

catlog22 Skill

Dual-mode brainstorming pipeline. Auto mode: framework generation → parallel role analysis (spawn_agents_on_csv) → cross-role synthesis. Single role mode: individual role analysis. CSV-driven parallel coordination with NDJSON discovery board.

wirasm Skill

Interactive PRD generator - problem-first, hypothesis-driven product spec. Use when the user wants to create a PRD, write a product or feature spec, scope a new product, or invokes $prp-prd.

wirasm Bundle

Creates an implementation-ready plan for a feature, bug fix, refactor, or chore from a PRD, issue, document, or description using codebase evidence, first-principles reasoning, and conditional root-cause analysis, research, or spikes. Publishes issue-derived plans back to their source issue. Use when the user asks to "plan this feature", "plan this bug fix", "plan issue X", "create an implementation plan", "turn this PRD into a plan", investigate how a change should be built, link related plans, or invokes $prp-plan.

martinopolo Skill

Parse .mpx/SPEC.md by spawning mpx-spec-analyzer. Regenerates ROADMAP.md and phase CHECKLIST.md files.