Product & Planning

kriscard Bundle

Creates an approval-gated spec for non-trivial feature work from an issue URL or requirements text. Use when the user asks for a spec/PRD, pastes a Linear, GitHub issue, or Jira URL, or requests implementation where scope is ambiguous enough to need acceptance criteria before coding.

kriscard Skill

Obsidian goals review for quarterly or monthly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly or quarterly goals, check whether goals are on track, or runs /goals.

kriscard Bundle

Use when the user wants help shaping an idea through conversation: generating options, choosing between options, stress-testing assumptions, or turning an early idea into a lightweight spec. Also use when explicitly asked to run the ideation pipeline from messy input into contract, PRD, and implementation spec artifacts. Trigger on "ideate", "explore this idea", "poke holes in this", "help me choose", "turn this into a PRD/spec", or /ideation. Do not use for merely capturing an idea, processing inbox notes, or building the MVP directly.

luckyrjain Bundle

Classify one or more raw, unscoped incoming issues, bugs, or feature requests: category, severity, duplicate-of (when evidence supports it), and a recommended owning skill or squad. Use when raw issues need triage before anyone acts on them. Keywords: triage these issues, classify these bugs, what category is this, is this a duplicate of another issue, which team owns this issue. Not for a live paging-webhook incident (incident-triage-agent), an already-scoped tracker query to work through (backlog-runner), or a bare ownership lookup with no raw issue to classify (squad-map).

luckyrjain Bundle

Use when rough product ideas, feature proposals, workflows, existing PRDs, or build/no-build questions need a validated PRD, gap review, or readiness assessment. Keywords: PRD, product requirements, should we build, challenge this idea, review PRD, MVP scope, build readiness, feature spec. Not for implementing code (loop-task-implementer), MR review (pr-review), domain mapping (domain-comprehension), or writing tests (test-writer).

luckyrjain Bundle

Use when an approved architecture decision or PRD needs to become an implementation-oriented design: components, APIs, events, data model, state machines, consistency, retries, idempotency, capacity, failure strategy, observability, rollout. Keywords: system design, technical design doc, component design, data model, state machine, rollout plan. Not for deciding whether the architecture itself is sound (architecture-review), reviewing an existing API's contract (api-design-review), or writing the PRD (prd-architect).

luckyrjain Bundle

Scheduled queue-management wrapper around loop-task-implementer — pulls N tickets from a Jira/GitHub Issues query, works through them in dependency order overnight, opens a PR per task, never auto-merges. No new Builder/Reviewer/review logic — delegates entirely to loop-task-implementer per task. Not for interactive, human-typed single-task requests — those route to loop-task-implementer directly. Keywords: overnight run, ticket queue, backlog sweep, scheduled multi-task loop, nightly PRs.

luckyrjain Bundle

Investigate a research question against primary sources — repository evidence and, when available, external documentation — and report findings with a cited source and evidence status per claim. Use when a question needs an evidenced, sourced answer rather than a recollection. Keywords: research this, find out whether, what does the documentation say, investigate this question, cited findings. Not for reconstructing this codebase's own current behavior (domain-comprehension), or deciding between options once the facts are known (engineering-decision-discovery).

luckyrjain Bundle

Use when a backlog of tech debt items needs ranking by business impact, engineering drag, operational risk, and effort. Keywords: tech debt, debt prioritization, debt backlog, engineering drag, refactor prioritization. Not for planning a specific migration program (migration-program-manager, which this skill can escalate to) or a cost/rightsizing sweep (cost-optimization-sprint-planner).

luckyrjain Bundle

Use when a PRD, proposed design, or architecture diagram needs a validated architecture decision before implementation begins — risks, scale limits, failure modes, security posture, operability, and alternatives considered. Keywords: architecture review, ADR, architecture decision record, design review, should we build it this way, scale limits, failure modes. Not for authoring the PRD itself (prd-architect), implementation-level component/API/data-model design (system-design), or reviewing an already-merged PR's code (pr-review).

luckyrjain Bundle

Build a verifiable, evidence-backed representation of a business domain and an as-built PRD for the in-scope service(s) and/or domain. Executable source code is primary truth; runtime telemetry validates behavior, not intent. Keywords: subsystem onboarding, multi-repo architecture ground truth, bounded-context mapping, current-state requirements reconstruction, and engineering-leader summaries. Not for ownership lookup only (squad-map), MR review (pr-review), or future-state product specification from an idea (prd-architect).

xonevn-ai Bundle

Mine Claude Code session logs for skill idea candidates. Use when running the weekly skill generation pipeline to extract, score, and backlog new skill ideas from recent coding sessions.

xpert-ai Bundle

Use the Valve Business Workbench middleware tools for context-aware valve object analysis, evidence and constraint review, ontology Action discovery and preflight, reviewable proposal creation, and audit. Use when a user asks about the current Workbench valve, a valve identified by code, or a governed valve business operation.

code-saurabh Skill

Create, edit, read, and design PowerPoint presentations (.pptx). Use whenever a .pptx file is involved — creating slide decks, pitch decks, or stakeholder presentations; reading or extracting content from an existing .pptx; editing or updating slides; building from a template. Trigger on "deck", "slides", "presentation", "pitch deck", "PowerPoint", or any .pptx filename.

rohitg00 Bundle

Interactive design wizard that guides through a complete frontend design process with discovery, aesthetic selection, and code generation. Use for creating distinctive, production-ready UI.

abhillashjadhav Skill

The pm-agent-os orchestrator. Use when the user invokes /pm or hands over any product-management request — synthesizing interviews, mining feedback, mapping assumptions, tearing down a competitor, sizing an opportunity, framing jobs-to-be-done, planning research, or any multi-step product task spanning discovery, strategy, build, launch, or iterate. Classifies the request into lifecycle stage(s), invokes the matching stage skills in sequence, and blocks every output whose verification gate has not passed. Also use when the user asks to run any output past a reviewer persona — 'review as engineer/designer/executive/skeptic/customer/data-analyst/legal' — routing to the persona agents in .claude/agents/. Do NOT use for coding tasks, repo maintenance, PR reviews (/pr-review's job), or knowledge questions about PM concepts with no work item attached.

abhillashjadhav Skill

Use this skill when a product spec, feature requirement, PRD, or user story needs to be converted into a concrete evaluation rubric. Triggers on phrases like "write an eval for this", "create a rubric", "how do I test this AI feature", "define good output", "what should I measure", or when a user pastes a spec and asks what success looks like. Produces a binary pass/fail checklist — not vague metrics, not suggestions — a rubric you can run against model outputs today. This is the skill AI PMs need before anything ships to production. Do NOT use to execute an evaluation or invent requirements absent from the supplied specification.

abhillashjadhav Skill

Forces a written PRD before any code generation. Use this skill when the user says "build", "create app", "make me a", "vibe code", "let's build", "I want an app that", "spin up a", "prototype a", "ship a", or any phrasing that signals they want code generated from a high-level idea. Also use when the user references an existing project but the conversation has no PRD context (no /prds/ file referenced, no clear success metric). The skill blocks code generation until a 5-field PRD exists as a markdown file in the repo. Do NOT use when the user is asking factual questions, debugging existing code, editing a specific file they've named, or working in a repo where a PRD for this feature already exists at /prds/. Skip when user explicitly says "skip the PRD" or "just code it" — but flag the risk once before proceeding.

abhillashjadhav Skill

Iterate-stage skill: turns a spec into the complete runnable verification layer — binary gates, anchored rubric, paste-ready judge prompt, and harness instructions — in one pass. Use when a feature needs its full eval built — 'create an eval for this spec', 'build the verification layer', 'spec to eval harness', 'turn this PRD into something we can run outputs through' — or when /pm routes such a request here. Do NOT use for the gates+rubric design artifact alone (prd-to-eval), for judge prompts over existing criteria (llm-as-judge-designer), for executing an eval over outputs, or for eval definitions.

abhillashjadhav Skill

Discovery-stage skill: reframes a feature idea or feature request into jobs-to-be-done statements containing zero solution language. Use when the user wants the underlying job behind a feature — 'frame this as JTBD', 'what job is this feature hired for', 'what are users really trying to get done', 'rewrite these requests as jobs' — or when /pm routes such a request here. Do NOT use for explaining JTBD theory, writing PRDs (Build stage), synthesizing interviews (interview-synthesizer — its patterns can feed this skill), or prioritizing feature lists.

abhillashjadhav Skill

Build-stage skill: turns a PRD or feature spec into a verification layer — binary quality gates for disqualifiers plus an anchored 1-5 rubric for tradeable qualities, with the two never mixed. Use when the user needs to define and test 'good' for a feature — 'turn this PRD into an eval', 'define good for our AI summarizer', 'build quality gates and a judge rubric', 'how do we test whether this works' — or when /pm routes a spec-bearing eval-design request here. Do NOT use to generate artifacts against frozen criteria (builder-validator), to execute an eval over outputs, for gate-vs-rubric knowledge questions, or for build/kill decisions (ai-feature-go-no-go).

abhillashjadhav Skill

Launch-stage skill: turns launch data into a structured retro where every lesson cites an observed event and decisions are judged separately from outcomes. Use when a launch has run and the learning needs extracting — 'run the retro on the launch', 'what did we learn from the March launch', 'post-launch review with these numbers', 'turn these launch notes into a retro' — or when /pm routes such a request here. Do NOT use for mid-launch status updates (stakeholder-update), for designing the investigation into a metric drop (research-brief), for team-process retros with no launch data, or for retro-facilitation knowledge questions.

abhillashjadhav Skill

Discovery-stage skill: turns an open product question into a structured research plan where every method is mapped to the decision it informs. Use when the user needs to plan research before acting — 'write a research plan for X', 'how should we figure out why Y happened', 'what research do we need before betting on Z', 'draft the research brief' — or when /pm routes such a request here. Do NOT use to synthesize research already run (interview-synthesizer / feedback-pattern-miner), to execute surveys or studies, for qual-vs-quant knowledge questions, or for web/market deep-research tasks.

abhillashjadhav Skill

Strategy-stage skill: turns a pricing question into structured options — every option carries a stated margin mechanism, never a naked price point. Use when the user is weighing pricing structures — 'per seat or usage-based', 'freemium vs free trial', 'structure the pricing options', 'bundle or unbundle the add-on', 'how should we price X' — or when /pm routes such a request here. Do NOT use to conjure a single price with no cost/margin context, to size markets (opportunity-sizer), to audit a roadmap's economics (roadmap-reality-check), or for definitions of pricing terms.

abhillashjadhav Skill

Discovery-stage skill: breaks a product idea into its load-bearing assumptions, ranked riskiest-first, each tagged testable/untestable with a proposed test. Use when the user pitches an idea and asks what it depends on — 'map the assumptions', 'what are we betting on', 'what could kill this', 'what needs to be true', 'riskiest assumption first' — or when /pm routes such a request here. Do NOT use to write the PRD or spec (Build stage), to size the market (opportunity-sizer's job), for knowledge questions about assumption-testing methods, or for analyzing non-product documents.

abhillashjadhav Skill

Build-stage skill: freeze requirements into binary criteria, generate the artifact, then self-audit against the frozen criteria verbatim before delivery. Use when the user asks for an artifact WITH requirements attached — 'draft X and check it against these requirements', 'build Y to this spec', 'generate and self-QA before showing me' — or when /pm routes a spec-bearing generation request here. Do NOT use when no requirements exist to freeze, for reviewing work the user wrote themselves, for building eval harnesses from specs (prd-to-eval), or for knowledge questions about QA.

abhillashjadhav Skill

Discovery-stage skill: builds a TAM/SAM/SOM opportunity size where every number carries a stated source or an explicit estimate label — no naked figures. Use when the user asks how big a market or opportunity is — 'size the market for X', 'TAM/SAM/SOM for Y', 'is this niche big enough', 'market-size inputs for the deck' — or when /pm routes such a request here. Do NOT use for definitions of sizing terms, for single-fact lookups like a company's market cap, for internal revenue forecasting, or for mapping idea risks (assumption-mapper's job).

abhillashjadhav Skill

Build-stage skill: watches a working session and proposes one-line memory captures — never an interview — building a four-file project context (INDEX, STAKEHOLDERS, DECISIONS, STATE) that compounds across sessions. Use when the user asks for persistent project memory — 'set up project memory', 'make Claude remember my stakeholders', 'you keep forgetting my project' — and proactively whenever a decision, stakeholder fact, or state change worth keeping surfaces in conversation. Do NOT use for one-off summaries, for auditing an existing context file (context-auditor), or for questions about whether Claude remembers past chats.

abhillashjadhav Skill

Launch-stage skill: turns raw project state into audience-calibrated status updates whose numbers reconcile exactly to the input — emphasis varies by audience, facts never do. Use when project state needs communicating — 'write the launch status update for the exec team', 'weekly stakeholder update from these notes', 'update sales on where the launch stands' — or when /pm routes such a request here. Do NOT use for public launch announcements (announcement-drafter), for logging decisions to memory (pm-context-system), for one-off meeting summaries, or for cadence-process questions.

abhillashjadhav Skill

Discovery-stage skill: turns material about a competitor's product — pricing pages, docs, changelogs, screenshots, customer reports — into a structured teardown where every claim is marked observed or inferred. Use when the user names a competitor product and asks for a teardown, competitive analysis, or comparison — 'tear down X', 'how does our Y compare to theirs', 'what is X doing with their pricing' — or when /pm routes such a request here. Do NOT use to write positioning or battlecards (Strategy stage), to scrape or collect the competitor data itself, for company-culture questions, or when no competitor material or product is identified — with nothing to observe it asks for material rather than inventing findings.

abhillashjadhav Skill

Strategy-stage skill: designs a north star metric and its input-metric tree for a product — the NSM must be leading, not lagging, and the output states the causality check it passed. Use when the user wants to choose or fix their top metric — 'design a north star metric', 'what should our NSM be', 'is MRR a good north star', 'build the metric tree' — or when /pm routes such a request here. Do NOT use for definitions of metric concepts, for analytics instrumentation setup, for diagnosing why a metric moved (research-brief), or for setting OKR targets on existing metrics.

abhillashjadhav Skill

Launch-stage skill: turns a shipped spec into an internal/external announcement pair with zero capability claims beyond what actually shipped — every claim mapped to its spec line. Use when a launch needs its announcements — 'draft the launch announcement', 'internal and external announcement for the release', 'changelog + customer email', 'blog post for the feature we shipped' — or when /pm routes such a request here. Do NOT use for internal status updates (stakeholder-update), GTM one-pagers (gtm-brief), announce-now-or-wait timing decisions, or general marketing-site copy.

abhillashjadhav Skill

Convert an explicitly approved PM Agent OS product decision or PRD into an ID-keyed, machine-checkable contract accepted by the Production Engineering OS frozen compiler. Use when a human decision-maker asks to hand approved product intent to Production Engineering OS, create an executable engineering contract, or prepare the P1 PMOS-to-real-provider run. Do NOT use for unapproved decisions, unresolved product-critical questions, ordinary prose PRDs, coding, implementation, deployment, or release decisions.

abhillashjadhav Skill

Discovery-stage skill: turns user-interview transcripts into evidence-cited patterns. Use when the user provides one or more interview transcripts, discovery-call notes, or user-research conversations and asks what patterns, themes, or learnings they contain — 'synthesize these interviews', 'what patterns are in these transcripts', 'what did we learn from these calls' — or when /pm routes a Discovery request here. Do NOT use for lists of feedback items or support tickets (feedback-pattern-miner's job), for summarizing a single meeting, or to invent personas or findings when no transcript data is provided — with no data it refuses.

abhillashjadhav Skill

Strategy-stage skill: audits a roadmap against unit economics — every item tagged supported or unsupported with the economic mechanism stated. Use when the user provides a roadmap plus business numbers and asks what's economically justified — 'reality-check this roadmap', 'which items pay for themselves', 'what survives contact with the P&L', 'does this lineup make economic sense' — or when /pm routes such a request here. Do NOT use to author a roadmap, to prioritize purely by customer impact without economics, to size markets (opportunity-sizer's job), or for definitions of unit-economics terms.

abhillashjadhav Skill

Discovery-stage skill: turns a raw feedback dump — support tickets, app-store reviews, NPS verbatims, survey answers — into ranked themes whose counts reconcile exactly to the input total. Use when the user provides a list of discrete feedback items and asks what the patterns, top complaints, or priorities are — 'rank these tickets by theme', 'what are people complaining about most', 'mine this review export' — or when /pm routes such a request here. Do NOT use for interview transcripts (interview-synthesizer's job), for replying to a single feedback item, or for process questions about how to collect feedback.