Product & Planning

bmad-code-org Bundle

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager

bmad-code-org Bundle

Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"

arize-ai-phoenix Bundle

Manage GitHub issues, labels, project boards, sprint operations, and roadmap health for the Arize-ai/phoenix repository. Use when filing roadmap issues, triaging bugs, applying labels, running sprint close-out and rollover, auditing board hygiene, checking ticket-load balance across the team, keeping roadmap epics up to date, flagging epics that need planning, or querying issue/project state via the GitHub CLI.

langfuse Skill

Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.

tristanmanchester Bundle

Use Parallel's parallel-cli to do live web search, URL extraction (clean markdown), deep research reports, bulk data enrichment (CSV/JSON), FindAll entity discovery, and web monitoring. Use when the user asks to look something up online, needs current sources/citations, provides URLs to read or summarise, requests deep/exhaustive research, wants to enrich a dataset with web-sourced fields, wants a list of entities (companies/people/places), or wants to monitor the web for changes over time.

tristanmanchester Bundle

End-to-end service design and service improvement workflow based on Lou Downe's "Good Services" (15 principles). Use when the user asks for a service audit, service blueprint, customer journey map/service map, designing a new service, fixing a broken service, improving findability/clarity/accessibility, or creating an actionable backlog and service standard.

mwguerra Bundle

This skill should be used when conducting PRD interviews, creating product requirements documents, planning new features, documenting bug fixes, or when using commands like "/prd-builder:prd", "/prd-builder:feature", "/prd-builder:bugfix", or "/prd-builder:refine". Provides comprehensive interview frameworks and question templates for building thorough PRDs.

narumiruna Skill

Draft, execute, or track lean, verifiable implementation plans for non-trivial migrations, refactors, PR splits, task checklists, and other work with sequencing, tradeoffs, unknowns, or risks, and delete them when complete; use write-roadmap for strategic direction and skip small obvious tasks.

narumiruna Skill

Create, revise, review, or track concise, outcome-oriented product and system roadmaps with phased milestone checkboxes and evidence-based progress, and delete them when complete; use write-plans for executable task planning and implementation tracking.

narumiruna Bundle

Create, name, rename, revise, or review agent skills for clear triggers, safe workflows, strong checks, lean content, and easy discovery, and score or numerically compare skills only when the user explicitly asks.

gasserane Bundle

Turn an external tech/AI source (YouTube video, podcast, blog article, tweet or thread) into a de-duplicated improvement roadmap for the MEL system and Claude Code setup: fetch the content, extract concrete techniques, inventory what the system already does, classify each idea reuse/improve/rebuild on an Adopt/Trial/Assess/Hold ring, and write the roadmap file with a mandatory What-NOT-to-build section. Use for "analyse this video/article/talk/thread for my system", "turn this into a system-improvement plan", or a pasted URL with improvement intent. Not for MEL research video files needing the transcription+consent pipeline (video-content-analysis), mining internal QA logs (/improve-system), inspecting the system itself (/system-audit, /grade-system), academic evidence review (evidence-synthesis), or writing the LinkedIn piece (linkedin-field-note).

jk-0001 Skill

Validate a business idea before investing time or money. Use whenever a solopreneur has a raw idea and needs a structured process to stress-test it against reality — covering problem definition, demand evidence, competitive context, customer discovery, riskiest-assumption testing, and a scored go/no-go decision. Trigger on phrases like "validate my idea", "is this worth building", "should I pursue this", "test my business idea", "does this idea have legs".

secondsky Bundle

SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows, comments, permissions, visual regression, and reusable QA automation. This skill should be used when building SAC end-to-end tests, onboarding SAC dashboards into Playwright, creating dashboard profiles or scenario YAML, using Microsoft Edge/CDP, Chrome DevTools MCP, Vercel Labs agent-browser, or manual discovery for SAC components, testing SAC optimized stories, configuring SAC auth storage state, managing visual/data baselines, testing comments, planning writeback, data actions, multi actions, role-based views, restricted Windows/company environments, or creating SAC failure triage artifacts.

petrkindlmann Bundle

Build and visualize QA dashboards and reports with Allure Report, Grafana, and ReportPortal. Covers test execution visualization, stakeholder-facing quality reports, trend/flakiness panels, release-readiness gates, alerting, and CI integration for automated report generation. Use when: "test dashboard," "Allure," "test report," "quality dashboard," "Grafana," "ReportPortal," "test results visualization." Not for: defining which KPIs to measure or how to interpret them — use qa-metrics (this skill builds the panels; qa-metrics decides what they should show). Related: qa-metrics, ci-cd-integration, ai-bug-triage.

petrkindlmann Bundle

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

petrkindlmann Bundle

Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs. Staged pipeline: requirements extraction → risk analysis → coverage matrix → scenario generation → oracle design → test code → human review, with guardrails against hallucinated APIs and weak assertions. Use when: "generate tests from spec," "tests from PRD," "tests from user story," "auto-generate test cases," "AI write tests for me." Not for: testing AI/LLM features in your product — use ai-system-testing. Not for: auditing a pre-existing test suite you did not just generate — use ai-qa-review (Step 7 here only reviews tests THIS pipeline produced). Related: playwright-automation, unit-testing, api-testing, qa-project-context.

petrkindlmann Bundle

Create and fill .agents/qa-project-context.md with the project's tech stack, test frameworks, CI/CD pipeline, environments, quality goals, risk areas, team structure, and conventions. This is the one file every other QA skill reads first, so they skip redundant discovery and give context-aware advice. Use when: "set up QA context," "configure testing," "initialize project," first use of any QA skill. Not for: bootstrapping a brand-new project's QA end-to-end — use qa-start (which calls this skill as its first step). Related: qa-start, risk-based-testing, test-strategy, qa-metrics, playwright-automation.

petrkindlmann Bundle

Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview frameworks and continuous reassessment. Run this BEFORE test-strategy or test-planning. Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction — use test-strategy. Not for: a single sprint/release test plan — use test-planning. Not for: hands-on session-based bug hunting — use exploratory-testing. Related: test-strategy, test-planning, release-readiness, qa-metrics.

petrkindlmann Bundle

Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD," "dev-QA pairing," "definition of done," "testability," "quality culture," "QA in sprint planning." Not for: writing the unit tests themselves — use unit-testing; automated PR test-quality review at scale — use ai-qa-review; multi-quarter QA direction or roadmap — use test-strategy. Related: unit-testing, ai-qa-review, test-strategy.

petrkindlmann Bundle

Design and execute structured exploratory testing sessions. Covers Session-Based Test Management (SBTM), charter writing, heuristic-based exploration (HICCUPS, FEW HICCUPS), bug discovery patterns, note-taking templates, and conversion of findings to automated tests. Use when: "exploratory testing," "SBTM," "manual testing," "bug hunting," "test charter," "heuristic testing." Not for: an AI browser agent autonomously exploring the app from a natural-language goal — use agentic-browser-testing. Not for: testing your product's own AI/LLM features — use ai-system-testing. Related: test-planning, ai-bug-triage, risk-based-testing, agentic-browser-testing.

petrkindlmann Bundle

Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.

transilienceai Bundle

Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.

transilienceai Bundle

Domain assessment and web application mapping - subdomain discovery, port scanning, endpoint enumeration, API discovery, and attack surface analysis.

transilienceai Bundle

Run a professional penetration engagement OR a network vulnerability scan from a scope. WEB mode (apex domains / app URLs) — mandatory surface expansion, systematic OWASP attack-class coverage, reversible active exploitation, authoritative validation, Transilience PDF. NETWORK mode (a list of IPs/CIDRs, e.g. 1500 hosts) — machine-prudent BATCHED tool-first nmap sweep (host discovery + bounded common+less-common port/service scan + CVE surfacing) with a uniform per-IP output tree, then bounded deep-dives on the highest-value hosts. The general (non-CTF) analogue of hackthebox/htb-solve.

transilienceai Bundle

Infrastructure tech-stack identification — cloud providers, CDN/WAF, DNS services, TLS/CT, DevOps tooling, plus asset discovery (domains, subdomains, IPs).

transilienceai Bundle

Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.

igorwarzocha Bundle

Architect and refine OpenCode skills to extend agent capabilities. Handles directory scaffolding, SKILL.md authoring, frontmatter optimization, and resource organization (scripts/references/assets). Use proactively for creating new skills, updating existing workflows, or fixing skill discovery issues. Examples: - user: "Create a new skill for database management" → scaffold directory and initial SKILL.md - user: "My skill isn't triggering correctly" → analyze and refine frontmatter description - user: "Add a python script to the image-processing skill" → structure scripts/ directory - user: "How should I structure a skill for API docs?" → design references/ layout

jackjin1997 Skill

Use when user reports overwhelm from too many tasks, asks for week/sprint/OKR planning help, or describes spending 'all day firefighting' while long-term projects stall. Triggers on Chinese phrases 太多事 / 不知道先做哪个 / 排不过来 / 周计划 / sprint planning / 救火 / 优先级 / overwhelm / 焦虑 / 做不完 / todo 列表炸了, and explicit task triage requests. Especially valuable when waiting list has 15+ pending items, or when user says "重要的事一直推不动 / 都在做紧急的事". Do NOT use for small lists (<5 items just sort by deadline), team-level responsibility assignment (use RAPID/DACI from backlog), or when importance needs quantitative weighting (use weighted decision matrix).

jackjin1997 Skill

Converts a PRD or broad technical requirement into an AI-executable agile workflow with cards, checklists, branch-diff mapping, review gates, and a final comparison report. Use when the user wants PRD review, agile card decomposition, AI execution tracking, implementation branch review, or PRD-to-code traceability.

bitwize-music-studio Bundle

Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.

vercel-vercel-plugin Bundle

Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, BYOK, budgets, spend reporting, observability, compatible APIs, and coding-agent configuration. Use when adding AI Gateway to an app, migrating provider calls, choosing models or providers, debugging gateway requests, or running `vercel ai-gateway` commands.

waybarrios Skill

Discover the active AWS profile, region, account, and caller identity before SageMaker or AWS work. Use when local AWS context is needed or unspecified; do not use for cloud-agnostic model planning.

microsoft Bundle

Governs Microsoft Fabric OneLake catalog health, protection, and trust through Fabric Admin, Core, and Power BI REST APIs. Use for tenant or owner-scoped audits and guarded remediation of domains, workspace assignment, capacity, labels, tags, descriptions, refresh, and item identity. Catalog item discovery belongs to search-consumption-cli.

ulpi-io Skill

Discover code by MEANING and DEPENDENCY structure, not by matching text — with the `codemap` CLI: hybrid vector+BM25 semantic search, symbol lookup, incoming/outgoing dependency tracing, file summaries, PageRank importance, afferent/efferent coupling, and cycle detection over an indexed repo. Only authoritative when the index exists and is fresh — a stale or empty index is called out, not trusted. Use for architecture-aware code discovery instead of plain text search.

whawkinsiv Skill

Use this skill when the user is new and doesn't know where to start, asks 'what should I do first,' 'what order do I do things in,' 'where do I begin,' 'I have an idea but don't know what's next,' or seems lost among the available skills. Also use when the user asks for a roadmap or overview of the full process from idea to launched product. This is the starting point — it routes users to the right skill for their current stage.

whawkinsiv Skill

Use this skill when the user needs to prioritize features, define an MVP, create a roadmap, or decide what to build next. Also use when the user asks 'what should I build first,' 'is this feature worth building,' 'how do I decide between X and Y,' or 'feature prioritization.' Covers RICE prioritization, hypothesis testing, MVP definition, and ruthless feature prioritization for early-stage SaaS.