Product & Planning

konglong87 Skill

Use when: 需要规划产品中长期发展、设定里程碑、对齐团队方向、制定季度/年度计划 Do NOT use when: 短期执行无需长期规划、方向已锁定无需路线图

konglong87 Skill

Use when: 需要评审 PRD/BRD/MRD 等需求文档的质量、检查完整性/清晰度/可行性/指标/风险/一致性、在开发前做文档把关 Do NOT use when: 文档尚未产出（应先 /pm-docs 生成）；仅需口头讨论无需书面评审

product-on-purpose Bundle

Creates, triages, and prunes a plugin's two backlogs (new-component proposals and enhancements) to the Advanced Skill Library Standard. Use when capturing a new-component proposal through the why-gate, prioritizing backlog items, or removing stale or completed entries.

product-on-purpose Bundle

Assesses a new agent capability against the capability matrix, the Standard, and every skill, subagent and command this plugin ships, then proposes a matrix update, a backlog entry or an ADR draft without implementing any of them. Use when deciding whether a new Claude Code, Cowork or Codex capability should be modelled or adopted, when analysing a capability gap after a survey reports one, or when checking which components were last verified against an older agent version.

arisng Skill

CLI tool for managing AI coding skills across different AI assistants like Claude, Cursor, and others. Use when you need to search, install, generate, or manage AI coding skills using the Context7 registry. Supports authentication, skill discovery, installation, and generation workflows.

blackbelttechnology Bundle

Estimate developer cost and effort for a set of use cases, functional and non-functional requirements on a given technology stack. Produces an architecture plan, a role-resolved man-hour estimate with P50/P85/P95 ranges, a side-by-side comparison of four delivery modes (human only, human + AI, AI-steered human-supervised, agentic HITL), and a business case with NPV/ROI/payback/TCO and a must-should-could scope ladder. Use when the user asks "how much would this cost to build", "estimate this project", "how many man-days", "make an offer/quote", "what would it cost with AI vs without", "build a business case for this feature", or wants to size a backlog, an RFP response, or a change request.

daedalus Skill

Use this skill whenever a task requires multi-step, knowledge-intensive research that benefits from parallel search, iterative gap-filling, and structured synthesis. Triggers include: competitive analysis, literature reviews, data extraction from web results, finding and comparing multiple sources across vendors or time periods, security advisory research, market research, technology landscape surveys, academic paper discovery, and any task where a single search would clearly be insufficient. Also triggers on: "research", "find all", "compare across", "gather information about", "extract from the web", "scan for", "compile a list of", "run a search agent", "use SaC", "search as code". Prefer this skill over a plain web search whenever the task has multiple facets, requires verifying information across sources, or needs structured output extracted from results. Do not wait for the user to explicitly ask — if the task is clearly research-shaped, invoke this skill immediately.

daedalus Bundle

Quantum systems discovery skill for finding novelties and pushing the state of the art. Use this skill whenever the user wants to: explore quantum phenomena, discover new quantum behaviors or algorithms, run quantum circuit experiments, test quantum hypotheses, simulate quantum systems with Qiskit, validate results on real IBM quantum hardware, find quantum advantage regimes, probe entanglement structure, or do exploratory quantum research. Trigger on phrases like "quantum experiment", "run on quantum hardware", "discover quantum", "Qiskit simulation", "IBM quantum", "quantum circuit", "quantum novelty", "push quantum state of the art", "quantum exploration", or any request to investigate a quantum system computationally. This skill manages the full pipeline: hypothesis → Qiskit emulation → plausibility check → real hardware submission → result analysis.

3dcom2711 Skill

Add an idea to the backlog parking lot (999.x numbering)

3dcom2711 Skill

Review and promote backlog items to active milestone

magnus919 Bundle

Shared decision-making and governance methodology for all C-suite profiles. Covers decision frameworks (RAPID, DACI, decision matrices, pre-mortems, red-teaming), strategic thinking patterns (inversion, first principles, second-order effects), stakeholder communication (executive summaries, board decks, strategy memos), and governance frameworks (risk appetite, delegation levels, escalation paths).

45ck Skill

Purpose

45ck Skill

Purpose

45ck Skill

stakeholder-communication-planner

sidsaladi9 Skill

Use when the user wants to update the roadmap, build a Now/Next/Later view, reprioritize after new information, decide what moves to make room for a new initiative, shift timelines after a dependency slip, or figure out where a new initiative fits. Forces explicit trade-offs and keeps the roadmap anchored to outcomes, not a feature wishlist.

sidsaladi9 Skill

Adversarially attacks a PRD, strategy, or plan to find its holes before reality does — naming load-bearing assumptions, weakest links, and what a skeptical exec or competitor would exploit. Steelmans the plan first, then attacks it hard. Use when you're about to ship a doc to leadership, "this feels too clean," "what am I missing," "poke holes in this," "what would kill this," or prepping for a tough review.

sidsaladi9 Skill

Turns a PM artifact into a clean, self-contained HTML visual you can open and screenshot — a RICE/Kano prioritization matrix, a Now/Next/Later roadmap board, an OKR tree, a metrics scorecard, or a journey-map swimlane. Use when you say "make this visual", "turn this into a board / matrix / chart", "render the roadmap", "show me a scorecard", "visualize this", "I want to screenshot this", or after any skill produces a structured artifact and a picture would land harder than text.

sidsaladi9 Skill

Defines a North Star Metric that captures delivered customer value and decomposes it into 3-4 movable input metrics. Use when you need to "pick a North Star metric," "we're optimizing for revenue and it's hurting us," "build an input metric tree," "what should the team actually move," "align the roadmap to one number," or "our metric is a vanity metric."

sidsaladi9 Skill

Score and rank features, ideas, or bets and produce a defensible ranked list plus a clear recommendation. Use when the user wants to prioritize these features, decide what to build first, RICE score this backlog, rank these ideas, run a value vs effort 2x2, or pick the right prioritization framework. Picks the framework, defines the scale, scores consistently, and surfaces the close calls.

sidsaladi9 Skill

Turns a vague feature idea or problem statement into a structured, review-ready feature spec or PRD with goals, non-goals, success metrics, and testable acceptance criteria. Use when a PM says "write a PRD", "spec this feature", "turn this idea into a spec", "scope this", "define success metrics", "write acceptance criteria", or needs to break a big ask into a phased spec.

sidsaladi9 Skill

Breaks an epic, spec, or feature into well-formed user stories with Given/When/Then acceptance criteria, applies INVEST, and splits stories that are too big. Use when a PM says "break this epic into stories", "write user stories", needs "acceptance criteria for X", wants to "split this story", or asks to "turn this PRD into a backlog".

sidsaladi9 Skill

Builds an executive business case / ROI model that justifies funding one feature or investment — cost of inaction, options (incl. do-nothing), an expected-value benefit model (reach × adoption × value-per-unit), build+run cost, payback and ROI, sensitivity, and a fund/kill ask. Use when you say "build a business case", "is this worth building", "what's the ROI", "justify this investment", "cost-benefit", "make the case to fund this", or "should we build X or not". Justifies ONE bet against its own cost — it does not rank a backlog (that's prioritize), set a price (that's pricing), or choose direction (that's product-strategy).

sidsaladi9 Skill

Sizes a market with both top-down and bottom-up methods using the TAM/SAM/SOM framework, states every assumption, reconciles the two estimates, and sanity-checks the result. Use when you need to size an opportunity, fill the market section of a PRD or business case, justify a bet to leadership, or pressure-test a number someone handed you ("how big is this really?", "what's the TAM?", "is this market worth entering?").

sidsaladi9 Skill

Turns raw, messy meeting notes or a transcript into a crisp, shareable summary. Use when someone says "summarize these meeting notes", "turn this transcript into action items", "what did we decide", "clean up my notes", or "send a recap". Works for any meeting type — standup, planning, review, 1:1, or stakeholder sync — from pasted notes or a connected transcript tool.

sidsaladi9 Skill

Drafts the communications a PM owns when something is breaking or just broke — an internal escalation note, customer-facing status updates on the right cadence, a resolution/all-clear, and a short blameless postmortem for leadership. Use when you say "we have an incident", "the launch broke", "draft a customer notice", "status page update", "outage comms", "customers are hitting errors", "we're down", or "write the postmortem". Reactive comms only — not pre-mortem (failure before launch), release-notes (what shipped), or stakeholder-update (routine status).

sidsaladi9 Skill

Writes a product vision — the 3-5 year picture of the world your product is trying to create, and what has to become true along the way. Use when a PM or founder says "write the product vision", "what's our vision", "where is this going in three years", "the team can't see the bigger picture", or when every roadmap conversation collapses into next quarter because nothing above it exists.

sidsaladi9 Skill

Audits what actually shipped against what the spec promised, and turns the gap into a decision list. Use when a PM says "did we build what we specced", "what's actually in this release", "the spec says X but the product does Y", "check this against the PRD", "what got dropped", or before writing release notes, a launch announcement, or a retro on a delivery that drifted.

sidsaladi9 Skill

Plan a sprint — scope work, estimate realistic capacity, set a goal, and draft a copy-pasteable plan. Use when you say "plan our sprint", "size the backlog", "what fits in this sprint", need a "sprint goal", are deciding "P0 vs stretch", or need to "handle carryover" from last sprint. Works from a pasted backlog or pulls from Linear/Jira if connected.

sidsaladi9 Skill

Maps stakeholders onto an influence/interest grid, captures each one's stance, motivations, and decision power, and derives a per-person engagement plan with a RACI overlay. Use when you say "who do I need to get on board," "map my stakeholders," "build a power/interest grid," "figure out who's blocking this," "who decides vs. who's just informed," or "I keep getting surprised by the same exec."

sidsaladi9 Skill

Plans and scripts customer discovery interviews using The Mom Test. Use when a user wants to plan a customer interview, write discovery interview questions, build an interview script, generate Mom Test questions, or talk to users about a problem. Produces a non-leading question script grounded in past behavior, plus a note-taking template.

sidsaladi9 Skill

Generate a stakeholder update tailored to audience and cadence. Use when the user wants to "write a stakeholder update", "exec update", "weekly status", "monthly status", "announce the launch", "escalate this blocker", or "make a leadership-friendly version" — and when the same progress needs to be re-cut for execs, engineers, or customers.

sidsaladi9 Skill

Synthesize user research from interviews, surveys, and feedback into structured, evidence-backed insights. Use when you have a pile of notes to make sense of and say things like "synthesize these interviews", "find themes in this feedback", "what are users telling us", "turn this research into insights", or "analyze these support tickets". Extracts themes ranked by frequency and impact, then translates them into roadmap recommendations.

sidsaladi9 Skill

Builds a Teresa Torres-style opportunity solution tree that maps customer opportunities to a desired outcome, then to solutions and experiments. Use when the user asks to "build an opportunity solution tree", "map opportunities to our outcome", "OST for X", "structure our discovery", or "what should we focus discovery on". Keeps the team from jumping straight to solutions.

jpeetz Bundle

Use this skill when the user has decided to build a mobile app and needs a complete production blueprint — not brainstorming, not feature ideas, but an actual build brief. Covers both iOS and Android with exact tech stack, screen specs, monetization, and a 30-day sprint plan. Use when the user says things like "Scaffold this app" "Give me a build plan" "Write the PRD" "How do I build this?" "Create a technical spec" "Blueprint this idea" even if they don't mention "scaffolding" or the number of sections.

ardurai Bundle

God-level technical project management: Agile/Scrum (ceremonies, story points, velocity, sprint planning, retrospectives, impediment removal), Kanban (WIP limits, flow metrics, cycle time, throughput, Little's Law), roadmapping (OKRs, RICE/ICE scoring, opportunity solution trees, now-next-later), stakeholder management (RACI, communication plans, executive reporting, managing up), technical debt management (debt quadrants, debt register, ADRs), risk management (ROAM, risk register, pre-mortems), estimation techniques (three-point, planning poker, PERT, #NoEstimates movement), incident management (ICS roles, incident commander, severity levels, blameless postmortems), DORA metrics (deployment frequency, lead time, MTTR, change failure rate), and engineering metrics (cycle time, PR throughput, code review SLA). Never back down — deliver any project, align any stakeholder, and measure what matters.

ardurai Bundle

God-level software architecture patterns: microservices decomposition (DDD bounded contexts, strangler fig, anti-corruption layer), monolith-to-microservices migration, hexagonal/ports-and-adapters, clean architecture, onion architecture, event-driven patterns (pub/sub, event mesh, choreography vs orchestration), CQRS+Event Sourcing in production, Saga pattern, Outbox+CDC, API versioning strategies, backward compatibility, schema evolution (Avro, Protobuf), service discovery, sidecar/ambassador/adapter patterns, and architecture decision records (ADRs). Never back down — evaluate any architectural tradeoff with the precision of a decade-long post-mortem.