Product & Planning
Product & planning agent skills structure the thinking side of building: specs, PRDs, user stories, roadmaps, and prioritization frameworks. Install one and your AI agent produces planning documents with the same rigor and format every time.
-
programmeranthony Bundle Prd Engineer 2Use when 用户需要编写产品需求文档、整理功能需求、拆解 GitHub Issues 或制定实施计划时。触发场景:写PRD、产品需求、需求文档、prd、需求分析、功能设计、产品设计、需求评审、需求拆解、issue拆解、帮我写需求、整理功能点、我有个想法要落地、新功能规划。
-
ramp-public Skill Ramp Make X402 Payment 2Make and verify a small x402 payment from a funded Ramp x402 wallet, using Exa as the default demo merchant or an official x402 Bazaar for discovery. Use when asked to test x402, pay an x402-protected API, or demonstrate a Ramp x402 payment. For wallet provisioning or funding, use ramp-setup-x402-wallet instead.
-
arcadeai Skill Audit 4Run a diff-scoped code audit for architecture, dead code, and test quality. Uses the change from main to focus feature reviews; request a repository audit for whole-codebase discovery.
-
axross Bundle Agent Skill Management 2Deciding whether material belongs in a skill or project documentation, choosing its tier, and managing skill installation and active loading. Triggers on adding, editing, renaming, moving, or removing a skill; installed-copy or lockfile drift; same-name collisions, missing discovery, stale loaded content, or a loaded skill with a defective rule. Metadata authoring belongs to skill-authoring practices; host-specific reload and source-inspection commands belong to project operations. Covers source ownership, targeted installation, drift checks, and separate discovery and active-loading evidence.
-
axross Bundle Living Project Documentation 2Updating a project's own documentation when a change alters what it says, and reading it before planning one — the `docs/` tree recording what the project is and how it works now, and the mechanism that corrects it when a change makes it wrong. Triggers on "docs/", "spec", "domain model", "glossary", "ubiquitous language", "ADR", "supersede", "the docs are stale", "is this documented anywhere", "conventions/", "operations/". Not spec-driven development — a plan drives the change and this records what became true, so "spec-first" and "generate from the spec" route elsewhere; the plan document itself belongs to a PRD capability, and sentence-level craft to a technical-writing one. Covers decision records, conventions and operations, and five single-purpose validators.
-
axross Bundle Technical Document Authoring 2Drafting, structuring, editing, or reviewing a technical document — a design doc, RFC, ADR, runbook, README, API reference, changelog, or post-mortem — and the sentence-level craft that makes any of them readable. Triggers on "make this clearer", "how should I structure this", "is this readable", "too wordy", "passive voice", "hard to follow", "tighten this prose". Not for non-software writing — marketing copy, blog posts, talks, fiction, academic papers outside software — nor for a spec's section skeleton, which a PRD capability owns. Covers naming the reader, the four Divio document types, leading with the answer, and a plain-English vocabulary ceiling. Self-contained.
-
axross Bundle Product Requirement Document Authoring 2Writing, refining, or reviewing a PRD, feature spec, plan document, RFC, design doc, or issue description — the canonical tool-agnostic section structure such a document takes, and the craft behind each section. Includes the plan-writing or issue-drafting step of any delivery workflow. Triggers on "write a PRD", "draft a spec", "refine this issue", "structure this plan", "write acceptance criteria", "how do I verify this is done", "is this requirement testable". Not for writing the code, only the document that specifies it; UI markup, module placement, and test mechanics stay with the project's own conventions.
-
wendylabsinc Skill Linear 2Linear issue tracking and project management through the CLI or GraphQL API. Use when developers mention: (1) Linear issues or tickets, (2) issue tracking or task management, (3) WDY team issues, (4) closing, updating, or triaging tickets, (5) linking PRs to issues, (6) issue states (triage, backlog, started, completed).
-
zh30 Bundle Z SEO Plan 4Use when an independent developer asks for SEO, keyword research, ranking, 关键词, 搜索优化, or an SEO plan for a PRD, live URL, or page code. Researches demand and intent, maps primary and supporting terms to pages, and specifies on-page, technical, and content actions.
-
zh30 Bundle Z Write Prd 5Use when an independent developer asks to turn an idea, research notes, interviews, feature list, or rough spec into a decision-ready MVP PRD or 产品需求文档. Defines problem, users, goals, scope and non-goals, requirements, flows, metrics, risks, milestones, and acceptance criteria.
-
zh30 Bundle Z SEO Plan 5Use when an independent developer asks for SEO, keyword research, ranking, 关键词, 搜索优化, or an SEO plan for a PRD, live URL, or page code. Researches demand and intent, maps primary and supporting terms to pages, and specifies on-page, technical, and content actions.
-
zh30 Bundle Z Write Prd 6Use when an independent developer asks to turn an idea, research notes, interviews, feature list, or rough spec into a decision-ready MVP PRD or 产品需求文档. Defines problem, users, goals, scope and non-goals, requirements, flows, metrics, risks, milestones, and acceptance criteria.
-
zh30 Bundle Z SEO Plan 6Use when an independent developer asks for SEO, keyword research, ranking, 关键词, 搜索优化, or an SEO plan for a PRD, live URL, or page code. Researches demand and intent, maps primary and supporting terms to pages, and specifies on-page, technical, and content actions.
-
zh30 Bundle Z Write Prd 7Use when an independent developer asks to turn an idea, research notes, interviews, feature list, or rough spec into a decision-ready MVP PRD or 产品需求文档. Defines problem, users, goals, scope and non-goals, requirements, flows, metrics, risks, milestones, and acceptance criteria.
-
zh30 Bundle Z Write Prd 8Use when an independent developer asks to turn an idea, research notes, interviews, feature list, or rough spec into a decision-ready MVP PRD or 产品需求文档. Defines problem, users, goals, scope and non-goals, requirements, flows, metrics, risks, milestones, and acceptance criteria.
-
zh30 Bundle Z Customer Discovery 6Use when an independent developer needs to recruit, interview, or debrief real customers. Plans 5–15 Mom Test–style interviews and synthesizes past behavior, current workarounds or spend, pain frequency, and willingness to switch; includes 用户访谈 and 客户发现 requests.
-
zh30 Bundle Z Customer Discovery 7Use when an independent developer needs to recruit, interview, or debrief real customers. Plans 5–15 Mom Test–style interviews and synthesizes past behavior, current workarounds or spend, pain frequency, and willingness to switch; includes 用户访谈 and 客户发现 requests.
-
zh30 Bundle Z Customer Discovery 8Use when an independent developer needs to recruit, interview, or debrief real customers. Plans 5–15 Mom Test–style interviews and synthesizes past behavior, current workarounds or spend, pain frequency, and willingness to switch; includes 用户访谈 and 客户发现 requests.
-
zh30 Bundle Z Customer Discovery 9Use when an independent developer needs to recruit, interview, or debrief real customers. Plans 5–15 Mom Test–style interviews and synthesizes past behavior, current workarounds or spend, pain frequency, and willingness to switch; includes 用户访谈 and 客户发现 requests.
-
majiayu000 Bundle Dev Architecture Playbook 2Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.
567 -
vtex Skill Headless Intelligent Search 2Apply when implementing search functionality, faceted navigation, or autocomplete in a headless VTEX storefront. Covers product_search, autocomplete_suggestions, facets, banners, correction_search, and top_searches endpoints, plus analytics event collection. Use for any custom frontend that integrates VTEX Intelligent Search API for product discovery and search result rendering.
-
elzawarudo Bundle Krt Compound Master 2Supports standalone and Seneschal-nested delivery with per-run state, inherited initiative contracts, and brokered decisions. Discovery-gated artifact-first orchestrator for compound-engineering product delivery. Resolves roadmap/readiness generation, runs brainstorm/plan/document-review loops, derives mergeable work packages with focused review units, executes each review unit through resolved work/code-review roles, and hands shipping to krt-release-marshal with CI break-prevention evidence. Use when turning an existing documented software project into a sequenced roadmap and PR/Jira delivery program. Runtime aliases may expose this as krt:compound-master.
-
elzawarudo Bundle Krt Delivery Navigator 2Turn validated software requirements into a practical project delivery plan. Use when a user has a requirements packet, especially one produced by krt-requirements-weaver, and needs project planning artifacts such as scope framing, major tasks, prioritized backlog, milestones or iteration slices, schedule outline, team responsibilities, technology choices, dependencies, risks, and partial deliveries. Also use when the user asks how to build the system, how to organize the work, how to phase delivery, or how to plan the backlog before implementation. Runtime aliases may expose this as krt:delivery-navigator.
-
elzawarudo Bundle Krt Roadmap Cartographer 2Generate exactly one roadmap or readiness report for a documented initiative. Validates context sufficiency, maps source-backed roadmap items, dependencies, waves, and branch/PR strategy, or blocks with actionable readiness guidance. Use when a user needs a roadmap before compound delivery, or when krt-compound-master resolves its required roadmap_generator role. Runtime aliases may expose this as krt:roadmap-cartographer.
-
elzawarudo Bundle Krt Product Polish Council 2Orchestrates a comprehensive, evidence-based polish audit of web, mobile, and desktop applications through a versioned atlas, a cartographer, and twelve evaluators, with a required cognitive-load overlay on every finding. Use when asked to polish an application, assess its product maturity, walk end-to-end flows, find rough seams or amateur behavior, produce a prioritized improvement backlog, or verify that a round of changes raised perceived quality.
-
helderberto Skill Spec 2Create a spec (PRD) through user interview, codebase exploration, and module design. Use when starting a feature with unclear requirements, when the user asks to spec or define what to build, or says "write a spec" or "write a PRD". Don't use when requirements are crisp and a plan already exists (use /plan or /build).
-
leeovery Bundle Workflow Roadmap 2Product Roadmap
-
leeovery Bundle Workflow Discovery 2The universal first phase. Shape the work the user is bringing — confirm what kind of work it is, sketch its outline — then persist it and route into the pipeline.
-
leeovery Bundle Workflow Legacy Research Split 2Act as **curator + interviewer**. Walk the user through decomposing broad research files — each holding multiple themes — into topic-scoped files plus matching discovery-map items.
-
nvidia-omniverse Bundle Portable Build Runtime Paths 2Make native builds, command-line tools, viewers, plugins, shaders, test harnesses, and packaged artifacts portable across working directories, install trees, copied build trees, users, and machines. Use when Codex works on CMake/install rules, RPATH/RUNPATH, dynamic library lookup, shader or asset discovery, CLI resource paths, packaging, deployment, or bugs that only reproduce outside the repo root.
-
nvidia-omniverse Bundle Renderer Implementation Roadmap 2Sequence a nanoUSD renderer build from nothing into a correct, scalable backend using only the renderer skill set. Use when Codex starts a new renderer or backend, plans renderer milestones and phase order, decides what must be correct before the next layer, or needs the contracts-first build order and reduced-fixture corpus that turn the other renderer skills into a buildable plan with no reference renderer to copy from.
-
genfeedai Bundle Email Finder 2Find and verify contact emails associated with a domain using free discovery methods first and APIs when keys are available. Triggers on domain email scans, contact discovery, email pattern finding, and email enrichment.
-
genfeedai Bundle Leads Researcher 2Research prospect accounts, company data, decision makers, contact details, and buyer intent signals. Triggers on lead research, account research, prospect enrichment, decision-maker discovery, tech stack research, and buying signals.
-
farmountain Bundle Prd Agent 2PRD Generator Agent
-
farmountain Bundle Backlog Manager 2Backlog Manager Agent
-
farmountain Bundle Stakeholder Agent 2Stakeholder Agent
Frequently asked questions
What are Product & Planning agent skills?
Product & planning agent skills structure the thinking side of building: specs, PRDs, user stories, roadmaps, and prioritization frameworks. Install one and your AI agent produces planning documents with the same rigor and format every time.
Which Product & Planning skills are most installed?
Popular Product & Planning skills on SkillMD right now include prd-engineer, ramp-make-x402-payment, audit. Rankings shift as installs change; sort this page by "Most installs" for the live list.
Do Product & Planning skills work with Claude Code and Cursor?
Yes. Every skill here ships as a SKILL.md file, an open format that works in Claude Code, Claude.ai, Cursor, Codex, Windsurf, and 60+ other agents. Install one with npx skillmds@latest add <owner>/<name>, or copy the file into your agent's skills directory.