Product & Planning

nicoladevera Skill

Drafts a full PRD from rough input — problem statements, meeting notes, bullets, or partial drafts. Use when asked to "write a PRD", "draft a product requirements doc", "turn these notes into a PRD", or "structure this problem as a PRD". Applies quality criteria from doc-review automatically.

nicoladevera Skill

Reviews PM documents against quality criteria and produces actionable feedback with severity ratings. Use when asked to "review this PRD", "give feedback on this doc", "evaluate this spec", "review this ticket", or "assess this project brief". Detects document type automatically.

nicoladevera Skill

Analyzes backlog health or drafts a sprint plan with goals, capacity math, and story selection. Use when asked to "plan the sprint", "analyze the backlog", "create a sprint plan", "help with sprint planning", or "select stories for the sprint".

nicoladevera Skill

Decomposes a PRD, spec, or feature description into shippable stories with acceptance criteria. Use when asked to "break this into tickets", "generate tasks", "write user stories", "create acceptance criteria", or "decompose this feature for engineering".

nicoladevera Skill

Plans what to learn before committing — assumption mapping, method selection, evidence thresholds, sequencing. Use when asked to "plan discovery", "what should we research first", "create a discovery plan", "map our assumptions", or "help us decide what to test".

nicoladevera Skill

Compares initiative candidates, sequences work, and produces prioritization rationale with explicit trade-offs. Use when asked to "prioritize the roadmap", "help me decide what to build next", "compare these initiatives", "sequence our work", or "roadmap planning".

nostrband Skill

Use whenever the user wants to find, rank, or shortlist directories and listing sites where they can submit an AI product — an AI tool, AI app, AI agent, or agent skill / plugin — to get backlinks, referral traffic, and discovery. Triggers on "where can I list my AI tool", "directories to submit my AI agent", "agent-skills directories", "best AI tool directories for backlinks", "where do I get my GPT/Claude app discovered", or "pull submission details for these AI-directory domains", even when described indirectly (we built an AI agent, where do we get it in front of people). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-mcp-directories for MCP-server listings specifically, and to find-product-directories for general SaaS/software/app launches with no AI angle. Skip finding an AI consultancy/agency to hire (use find-ai-consultancy), comparing AI products ("ChatGPT vs Claude"), building an A

nostrband Skill

Use whenever the user wants to find, rank, or shortlist directories and registries where they can submit or list an MCP server (Model Context Protocol server) — to get backlinks, referral traffic, and discovery by agent builders. Triggers on "where do I list my MCP server", "best MCP directories", "MCP registries to submit to", "get my MCP server discovered", or "pull submission details for these MCP-directory domains", even when described indirectly (we built an MCP server, where do we publish it). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-ai-directories for general AI-tool / AI-agent / agent-skill listings, and to find-product-directories for general SaaS/software launches. Skip building an MCP server or asking how MCP works (DIY), finding a firm to build one (use find-ai-consultancy / find-software-developer), and MCP link-building *services*.

gigio1023 Bundle

Use when the user starts substantial work in territory they don't know well — a new project, research direction, investment or money-management strategy, career or life plan, product or game idea, or an unfamiliar part of a codebase — with no spec, plan, or reference yet; or when they ask for an unknowns pass, blind spot pass, option map, throwaway variants, or a launch brief. Surfaces unknowns with the single cheapest technique, compresses what was learned into a launch brief, and, when the user cannot test the result directly, explains consequential decisions and offers a comprehension check. NOT for well-specified or small tasks, multi-round Socratic discovery (use deep-interview), final decision synthesis (use fable5-model-routing), or packaging session state (use session-handoff).

gigio1023 Bundle

Use when the user explicitly wants to be interviewed deeply, grilled on a vague idea, led through requirements discovery, or questioned until a plan, product, workflow, or decision is clear enough to hand off. Runs an Ouroboros-centered, context-first Socratic interview one question at a time and ends with a user-approved Interview Brief. NOT for job-interview rehearsal, surveys, therapy or clinical intake, a single clarification, requests to summarize existing material without further questions, or light discovery that one technique plus a launch brief would settle (use find-unknowns).

gigio1023 Bundle

Use only when the user asks for a plan file or a revision of one, or names gigio-write-plan: produces one file in .plans/ with staged tasks — needs, owned files, acceptance, checks — anchored to PROJECT.md judgment rules. The plan is data: a solo session reads it top to bottom, a lead uses the same file to dispatch parallel workers. Writes the plan, announces it, and stops — it never implements tasks itself. NOT for executing or resuming a plan (gigio-execute-plan), reviewing finished work (gigio-review-results), or discovery while the work itself is still unclear (find-unknowns, deep-interview). Never activate because work looks sizable; ordinary in-session task tracking is not this skill and needs no plan file.

gigio1023 Bundle

Use only when the user invokes small-model-handoff by name, or when a pack skill (gigio-execute-plan, orchestrate-subagents) name-calls it while dispatching to a weaker executor, to turn an already researched and approved plan into a bounded prompt for an executor less capable than the planner. Covers scoped changes, test, build, and check runs, reproductions, and read-only evidence collection. Requires exact scope, actions, authority, capability assumptions, evidence, and stop rules. NOT for automatic invocation, model/cost/executor recommendations, peer or high-capability executors, discovery, planning, open-ended work, or general session handoffs.

idaibin Bundle

Use when a Git or non-Git workspace needs a machine-queryable repository asset scan, impact/relationship query, coverage or drift check, or an optional derived navigation view; not for task-local discovery, source changes, repository-guidance authoring, or change review.

igmarin Skill

Use when assessing whether a PRD is technically sound, reviewing estimates for realism, or preparing a technical go/no-go. Trigger words: tech lead, feasibility, PRD review, estimation quality, technical risk, go/no-go, architecture concerns.

igmarin Bundle

Use when the user wants a PRD, product requirements, a feature spec, or a written scope. No implementation code. Trigger words: PRD, product requirements, plan a feature, write a spec, requirements document.

igmarin Skill

Use when reviewing a PRD for completeness, testability, clarity, or feasibility. Trigger words: review PRD, PRD review, validate PRD, feasibility check, requirements review.

igmarin Skill

Use when selecting tickets for a sprint from a prioritized backlog, setting a sprint goal, or allocating capacity. Trigger words: plan sprint, sprint planning, sprint goal, sprint capacity, sprint backlog, what should we work on this sprint.

igmarin Skill

Use when a feature needs the full delivery cycle from PRD through retrospective, not a single planning phase. Trigger words: delivery lead, end-to-end, full cycle, pipeline, PRD through retro, orchestrate delivery.

igmarin Skill

Use when planning a feature, running product discovery, defining requirements, or preparing a sprint backlog. Hard gates sit between phases — do not skip to tasks or tickets without approval. Trigger words: product owner, PRD, discovery, requirements, task breakdown, tickets, sprint backlog, scope a feature.

igmarin Bundle

Use when breaking a feature or approved PRD into an implementation task list. Trigger words: task list, implementation plan, feature breakdown, generate tasks, TDD tasks, break down this PRD.

igmarin Skill

Use when tracking a sprint or project, assessing execution health, flagging blockers, or writing a stakeholder update. Trigger words: project manager, execution tracking, estimates, risk register, status report, blockers, milestone tracking.

igmarin Skill

Use when prioritizing a backlog, ranking features, or applying RICE, MoSCoW, value-vs-effort, or WSJF. Trigger words: prioritize, backlog, RICE, MoSCoW, value vs effort, ranking, WSJF.

igmarin Skill

Use when writing a stakeholder status report, sprint update, or weekly project update. Do not invent progress. Trigger words: status report, sprint update, weekly update, project status, stakeholder update.

igmarin Skill

Use when discovering which planning skill or persona to run. Covers PRDs, tasks, tickets, backlog, sprint, retro, status, risks, GitHub issues, and the four personas. Trigger words: planning, PRD, tasks, tickets, estimation, risks, status, backlog, sprint, retrospective, agile, product management.

instavm Skill

Enumerate subdomains from captured traffic. Use when user asks about subdomain discovery, attack surface mapping, or domain reconnaissance.

jasontang-ai Bundle

Use this skill to review whether an external implementation or adapter follows ACP protocol semantics and discovery expectations.

jezweb Bundle

Use when you want a lightweight, claimable task board that lives in the repo as markdown, for parallel multi-agent work or your own backlog, where a card is a file and the folder it sits in is its status. Covers the folder-board layout, claiming and completing by moving the file, worktree-safe concurrency for a fleet, frontmatter conventions, discoverability one-liners, and an optional zero-dependency local web UI to view and drag cards. Triggers, "kanban", "task board", "track parallel agent work", "claimable work queue", "what's in flight".

jezweb Skill

Use when setting up an ongoing agent dedicated to a role rather than a one-off task, a webmaster, researcher, bookkeeper, support triager. Covers shaping the persona and its lane, populating a specialist with real reference (not a generic shell), running it with one bounded output per run, putting it on a heartbeat, and the observer disciplines for a role that watches a live human system and may ramp up to running it (observe without consuming the signal; the observer-to-actor trust ladder). For backlog-grinding work that tunes its own procedure, see run-a-self-refining-loop.

jezweb Skill

Use when a role has substantial repeated work one session can't finish (enriching hundreds of records, grinding a backlog, sweeping a large catalogue) AND the work keeps teaching you how to do it better. Covers the tick shape, the separate state files, idempotency, queue-learnings-apply-next-tick, and the rules that keep a self-modifying loop safe. The deep end of run-a-role-agent; don't reach for it for one-offs or fixed procedures.

jiangjiax Bundle

产品 PRD 生成工具。结合《创造》的产品故事方法论、product-position 的定位框架， 以及 Lenny's Newsletter 的 PRD 最佳实践，帮你从想法生成一份可执行的产品需求文档。 触发方式：/li-prd、「帮我写 PRD」「生成需求文档」「写产品文档」「把这个想法写成 PRD」 「黑客松 PRD」「整理产品需求」「我要开始做了，帮我理清需求」 即使用户没说"PRD"，只要他们想把一个产品想法整理成可执行的文档，也应触发本 skill。 DO NOT trigger for: 内容脚本生成、选题分析、数据复盘等内容创作任务。

jiangjiax Bundle

PRD 专家顾问模式。三位知名 PM/CEO 扮演顾问角色，主动审查 PRD，找出薄弱环节并给出可直接写入文档的改进方案，用户 accept/reject 决定是否采纳。 触发方式：/li-prd-review、「强化 PRD」「专家顾问」「帮我看看这份 PRD」「让专家来审 PRD」「PRD 有哪些漏洞」「帮我优化 PRD」「PRD 还有什么问题」。 即使用户没说"PRD"，只要他们想让专家角色审查一份产品文档并给出改进方案，也应触发本 skill。 DO NOT trigger for: PRD 生成任务（用 li-prd）、内容脚本生成、选题分析等内容创作任务。

jordanhubbard Bundle

Validates code correctness, discovers edge cases, and enforces quality gates before shipping. Use when you need to write test plans, run regression suites, diagnose flaky tests, analyze failure patterns, or verify that a fix addresses the root cause rather than just the symptom. Handles test plan creation, integration testing, edge case discovery, quality metrics tracking, and regression detection across the Loom codebase.

jordanhubbard Bundle

Strategic product agent that triages customer feedback beads, writes actionable user stories with acceptance criteria, prioritizes work by user impact, and maintains roadmap alignment. Use when new customer feedback arrives, when features need prioritization, when user stories need writing, when roadmap drift is detected, or when weekly product status reports are due. Handles feature gap analysis, backlog grooming, and cross-team coordination through Loom meetings.

katalon-labs Bundle

Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types, Platform/TestOps IDs, verify uploaded runs, handle failed auto-upload, or summarize execution results after automation completes. Written for the automation tester whose framework has already run and whose report is sitting on disk. If the Playwright run has not happened yet, start at playwright-execute.

katalon-labs Bundle

Set up, verify, and troubleshoot Katalon True Platform/TestOps MCP connectivity for any AI coding agent. Use when you need to install or configure the Katalon MCP server, connect to a Katalon platform account, verify available Katalon MCP tools, diagnose missing authentication or repository access, confirm project/repository discovery, or explain what platform operations are and are not exposed through the MCP. One-time cross-cutting setup, run once by whoever wires the agent to the platform, before any lifecycle skill can work.

katalon-labs Bundle

Report Katalon True Platform/TestOps quality metrics to people outside QA. Use when you need to answer a stakeholder question with testing data, choose the few metrics that actually answer it, trend coverage, execution health, defect risk and stability across several releases, sprints, or iterations rather than inside one, and write the summary a manager presents upward at a steering committee, an exec review, or a quality business review. Produces a headline answer with the named specifics behind it, never a metric dump. The MCP returns current state with no history tool, so trends are built from execution dates plus snapshots this skill stores per period. For the ship or no-ship call on a single release, use release-analyze; for a pre-pipeline suite verdict, use test-review. Written for the test manager who has to present quality upward and the test lead who assembles the numbers.