Product & Planning

slamb2k Bundle

The project's single "what's on deck" surface — one command, two sections. Shows the best-practice lifecycle stages this project should adopt next (computed from repo state, via the recommendation engine) AND the durable backlog of follow-ups (ideas, deferred fixes, open questions, risks, tech debt) captured at /build and /ship so they survive /clear. Lists both, and resolves, dismisses, adds, or reviews follow-ups. Use when you want to see or act on everything outstanding. Triggers: "what's next", "next steps", "/logbook", "what's on deck", "follow-ups", "the backlog", "what did we defer", "lifecycle steps", "what should I do next".

agentsecops Bundle

Vulnerability management and findings aggregation using DefectDojo. Centralizes security findings from all SecOpsAgentKit scanners (Semgrep, Bandit, ZAP, Trivy, Grype, Gitleaks, Nuclei, Checkov, Horusec) into a unified platform with automatic deduplication, SLA tracking, risk-based prioritization, and compliance reporting. Use when: (1) Aggregating findings from multiple scanners across products and pipelines, (2) Tracking remediation status and SLA compliance against policy thresholds, (3) Deduplicating overlapping findings across security tools, (4) Generating vulnerability reports for compliance audits (SOC2, PCI-DSS, GDPR), (5) Managing security debt and vulnerability backlog across teams and applications.

agentsecops Skill

Operational Technology (OT) security assessment using a two-stage methodology: (1) Identification/Discovery of OT devices and protocols, and (2) Vulnerability Assessment using online sources and Metasploit. Use when: (1) Conducting authorized OT/ICS security assessments, (2) Identifying and enumerating OT protocols (Modbus, S7, IEC 104, DNP3, BACnet, EtherNet/IP), (3) Discovering industrial control devices and PLCs, (4) Assessing OT protocol vulnerabilities and security weaknesses, (5) Performing compliance scanning aligned with IEC 62443 standards, (6) Validating network segmentation and access controls in OT environments.

ayoubben18 Bundle

Draw a task's blast radius twice. BEFORE implementing, a PLANNED map of the modules the missions expect to add, change or touch; AFTER the reviewers pass, an ACTUAL map derived from the real diff, plus the DRIFT between them. Writes docs/tasks/<task>/change-map.md. Use from create-task / extend-task (planned pass), and after review-implementation + sync-architecture in create-task / resume-task / start-task / start-roadmap (actual pass), or standalone on a task.

ayoubben18 Skill

Pre-implementation critic. Spins up a read-only domain critic that challenges a drafted plan — a task's missions or a roadmap's task graph — against the ubiquitous language, CONTEXT.md, and ADRs, and pushes back ONLY on genuine conflicts. Silent when the plan is sound. Use before implementing (from create-task / create-roadmap) or standalone to stress-test a plan against the project's domain model.

ayoubben18 Skill

Cross-plan coherence critic for a whole roadmap. Reads roadmap.md plus every planned task's progress-tracker.md and pushes back ONLY on genuine discrepancies BETWEEN the finished plans — broken seams, coverage gaps, duplicated work, reversed/missing edges, terminology drift, conflicting assumptions. Read-only; silent when the plans cohere. Run standalone after planning finishes and before /start-roadmap.

ayoubben18 Skill

Post-implementation documentation-sync detector. Spins up ONE read-only subagent on a completed task's diff to find everything the change introduced that the architecture docs don't yet know about — new endpoints, patterns, dependencies, domain terms, ADR-worthy decisions — routed to the exact doc each belongs in. Autonomous runs apply only append-only safe additions and defer domain/ADR reshapes; interactive runs present the proposed doc deltas to pick. Use after a task's missions are done (from create-task / start-task / start-roadmap) or standalone on a diff.

ayoubben18 Bundle

Post-implementation review. Spins up three read-only critics on a completed task's diff — cleaner-architecture, slop-defender, reusability-inspector — that push back ONLY on real issues. Autonomous runs apply safe fixes (tests-green-gated) and write everything to review.md next to progress-tracker.md; interactive runs present findings to pick. Use after a task's missions are done (from start-task / start-roadmap / create-task) or standalone on a diff.

vfarcic Skill

Complete PRD implementation workflow - create branch, push changes, create PR, merge, and close issue

vfarcic Skill

Analyze existing PRD to identify and recommend the single highest-priority task to work on next

vfarcic Skill

Fetch all open GitHub issues from this project that have the 'PRD' label

vfarcic Skill

Close a PRD that is already implemented or no longer needed

vfarcic Skill

Create documentation-first PRDs that guide development through user-facing content

crazynomad Skill

GitHub backlog governance manager-loop. Triage open issues (type + routing labels), complete thin descriptions, maintain a bounded ready queue (Todo ≤ 5) on a GitHub Projects board, and repair board drift (closed issue still "In Progress" etc.). Config-driven — reads .claude/backlog-manager.yaml from the target repo; runs an init flow to generate it if missing. DRY-RUN by default, pass "apply" to execute writes. Use for recurring backlog grooming / issue triage of any GitHub repo, standalone or driven by /loop. Requires gh CLI with repo + project scopes.

vfarcic Skill

Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.

vfarcic Skill

Unified tool for managing cluster data: organizational patterns, policy intents, and resource capabilities. For patterns and policies: supports create, list, get, delete, deleteAll, and search operations (patterns also support step-by-step creation workflow). For capabilities: supports scan, list, get, delete, deleteAll, and progress operations for cluster resource capability discovery and management. Use dataType parameter to specify what to manage: "pattern" for organizational patterns, "policy" for policy intents, "capabilities" for resource capabilities.

vfarcic Skill

Create changelog fragment for release notes. Invoke during /prd-done workflow during the first push to the PR.

vfarcic Skill

Update PRD progress based on git commits and code changes, enhanced by conversation context

vfarcic Skill

Update PRD based on design decisions and strategic changes made during conversations

skenetechnologies Skill

When the user wants to drive adoption of a specific feature -- including launch planning, discovery mechanisms, adoption funnels, or feature deprecation. Also use when the user says "feature launch," "feature rollout," "underused features," "feature stickiness," or "how to get users to use a feature." For in-product messaging, see in-product-messaging. For onboarding, see product-onboarding.

britt Skill

Use when writing status updates, communicating delays or blockers, announcing launches, or requesting decisions and resources from stakeholders - structures the message by audience level (exec/management/peer/team) with lead-with-the-punchline framing

britt Skill

Use when identifying project stakeholders, asked 'who are the stakeholders', checking whether a plan covers all stakeholder goals, or linking GitHub issues to stakeholder needs - maintains persona profiles (goals, pain points, priorities) and generates goal-to-issue coverage reports with gaps

britt Bundle

Use when asked to write a product spec, PRD, or requirements document, or to design a new feature or project before implementation - interactively elicits problem, audience, success criteria, and scope, then produces a structured spec file

qte77 Skill

Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous execution.

henkisdabro Bundle

Generate comprehensive Product Requirement Plans (PRPs) for feature implementation with thorough codebase analysis and external research. Use when the user requests a PRP, PRD, or detailed implementation plan for a new feature. Conducts systematic research, identifies patterns, and creates executable validation gates for one-pass implementation success. Do NOT use for client discovery, requirements gathering, or scope definition - those need a separate clarification pass before the PRP step.

shir-bruchim Skill

Generates PRDs through guided discovery. Use when starting a feature or defining requirements.

shir-bruchim Bundle

Interviews users to build project specs through guided discovery. Use when starting a new project or feature.

shir-bruchim Skill

Converts PRDs into prd.json for Ralph. Use when preparing PRDs for Ralph or breaking features into atomic stories.

shir-bruchim Bundle

Orchestrates the Ralph pipeline (spec-interview → PRD → execute). Use for features needing autonomous implementation.

codescene-oss Skill

Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file.

bmad-code-org Bundle

Create, update, validate, or analyze a game project's PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD — often derived from a GDD or prepared for external-tool integration.

jona Skill

Strategic guidance for design-focused founders and product leaders based on Dylan Field's experience scaling Figma from a WebGL experiment to an 8-product company with 1700 employees. Use when seeking advice on founding design-tool companies, evaluating product-market fit signals, making early startup decisions (launching, pricing, pivoting), understanding how AI changes design's value proposition, integrating designers into AI product development, or applying mental models for startup leadership and product strategy. Triggered by questions about design entrepreneurship, startup scaling, product-market pull vs fit, cold outreach strategies, roadmap planning, or the future of design in AI era.

jona Skill

Guidance for building AI systems for scientific discovery, based on lessons from AlphaFold's development. Use when designing ML systems for scientific domains, planning validation strategies using blind benchmarks, deciding how to release scientific AI tools for maximum impact, evaluating data acquisition vs architectural research investment, building tools for domain expert adoption, structuring ML research projects with compute budgeting, or assessing when a scientific AI tool has crossed the relevance threshold for real-world use.

wuchubuzai2018 Bundle

OKR 目标与举措撰写及润色技能。当用户需要编写季度 OKR、SMART 目标、PDCA 举措、个人行为描述，或要求将汇报话术改得更实在、更像本人表达时使用。适用于 AI 研发、产品、平台集成和代码质量等工作场景。

getsentry Bundle

Produce a weekly digest of upstream framework/library activity (releases, Discussions, RFCs, RSS) for the Sentry JS SDK. Use when asked to "track framework updates", "check framework releases", "what changed upstream", "weekly framework digest", "what's new in React/Next/Nuxt/etc.", or to surface backlog candidates from upstream frameworks. Do NOT use for checking Sentry SDK releases, internal package updates, or individual bug triage.

gemini-cli-extensions-data-agent-kit-starter-pack Skill

Guides the authoring and validation of Apache Airflow DAGs for Managed Service for Apache Airflow (MSAA; formerly Cloud Composer). Covers environment context discovery, Airflow 2 vs 3 compatibility, authoring best practices, and local/remote validation processes. Use when creating or extending an Airflow DAG. Don't use when authoring Python code unrelated to Airflow DAGs.