Product & Planning

socketdev Skill

Collapse noisy backlogs: verify done work, fold duplicates, delete stale tasks.

promovaweb Bundle

Use depois que o MVP tiver sido aceito para entrevistar a pessoa responsável sobre a evolução do produto, propor milestones pós-MVP e vincular specs sem reabrir silenciosamente o núcleo acordado. Não use para definir o MVP inicial, executar tarefas ou mudar uma spec concluída.

andresnator Bundle

Trigger: PRD, product requirements, technical product spec. Create rigorous PRDs for high-stakes, cross-team, regulated, or security-sensitive work.

shuwanito Bundle

Product manager agent specializing in strategic vision, user needs analysis, roadmap alignment, and ROI evaluation. Use when you need product strategy, feature prioritization, roadmap planning, or user-centric decision making.

shuwanito Bundle

Corporate strategy and diversification leader. Use when defining strategic vision, evaluating vertical expansion, identifying adjacent markets, prioritizing strategic investments, coordinating cross-functional execution between Finance/Marketing/Product, or converting market needs into acquisition priorities. Specializes in M&A scouting, ecosystem strategy, and long-term roadmap planning.

shuwanito Bundle

Red team offensive security and continuous pentesting specialist. Use when you need automated penetration testing, exploit simulation, APT emulation, or vulnerability discovery. Searches CVE databases and security advisories to identify unpatched vulnerabilities in project dependencies.

shuwanito Bundle

Generative testing and fuzzing agent specializing in AI-powered test generation, autonomous fuzzing, and property-based testing. Use when you need automated test generation, fuzz testing strategies, property-based test design, or edge case discovery through generative techniques.

zeenie-ai Skill

Discover and load tools progressively as needed (reduces token overhead)

jordangaston Bundle

Generate a Product Requirements Document (PRD) for a new product or feature. Use when the user asks to create a PRD, write a product spec, define product requirements, or invokes /prd. Guides the user through a structured PRD template covering goals, personas, features, tech notes, and go-to-market strategy.

jordangaston Skill

Run a Binstack decision-making analysis. Binstack chooses between competing options by checking each against stack-ranked priorities using binary materiality (does this option materially move the needle -- yes or no?) rather than weighted scoring. Best for: (1) Prioritizing a backlog of features, projects, or initiatives where you need one winner, (2) Choosing between alternatives that seem 'close' on paper but differ in strategic impact, (3) Decisions where defensibility matters -- explaining 'why this and not that' to stakeholders. Not ideal for: cost/effort tradeoff analysis (use ROI), exploring a problem space (use HEAD), or decisions with a single dominant criterion that needs no framework. Trigger on: 'binstack', 'prioritize these options', 'which should we build next', 'rank these features', or when the user has multiple options and needs a clear, defensible pick.

jordangaston Skill

Run a Fermi ROI analysis to prioritize initiatives by estimated return on investment. Uses orders-of-magnitude estimation (powers of ten) instead of false-precision scoring. Best for: (1) Ranking a backlog where cost/effort tradeoffs matter, (2) Choosing between investments with different scales of impact and effort, (3) Quick prioritization that resists estimation error. Not ideal for: choosing between options that differ on strategic fit rather than ROI (use Binstack), exploring a problem space (use HEAD), or decisions where effort is irrelevant. Trigger on: 'fermi roi', 'estimate ROI', 'prioritize by ROI', 'which is the best investment', 'rank these by return', or when the user needs to compare initiatives by impact-per-effort. Based on: https://longform.asmartbear.com/roi-rubric/

jordangaston Bundle

Guides users through the Double Diamond design process — a four-phase framework (Discover, Define, Develop, Deliver) for solving complex problems through divergent and convergent thinking. Use this skill whenever the user mentions the Double Diamond, design process, design thinking, problem framing, problem definition, divergent thinking, convergent thinking, design sprints, UX process, product discovery, solution space, problem space, or wants help structuring how to approach a complex design or product challenge. Also trigger when users want to move from a vague problem to a clear solution, need help running a discovery phase, want to define a problem statement, are brainstorming solutions, or need to plan prototyping and validation. This skill applies to product design, service design, UX, strategy, and any domain where structured creative problem-solving is needed.

jordangaston Bundle

Analyze your product's competitive strategy using the Needs Stack framework (from Jason Cohen / A Smart Bear). Use this skill whenever the user mentions competitive strategy, competitive positioning, needs stack, product positioning, disruption analysis, moving up the value chain, customer needs hierarchy, or wants to understand how their product fits against competitors at different levels of customer need. Also trigger when the user asks about positioning against disruptors, finding higher-value product opportunities, or figuring out what level of customer need their product actually serves. Works especially well for founders evaluating new product ideas, analyzing incumbents they want to disrupt, or defending against upmarket/downmarket threats.

jordangaston Bundle

Diagnose a brand's ad account and turn research into a prioritized creative roadmap — two-way persona analysis (who your ads target vs. who actually buys), the one-to-two-sentence diagnosis, evidence ranking, and the icebox/quarterly/monthly roadmap system. Use whenever the user is auditing an ad account, onboarding a brand or client, asking what to test next, drowning in creative ideas and unsure what to prioritize, doing quarterly or monthly creative planning, or turning customer research into ads. Also trigger on creative strategy, creative roadmaps, creative sprints, ad account audits, persona research, marketing awareness levels, market sophistication, creative diversity, Andromeda, creative pillars, doubling down on winners, or phrases like 'we're just testing randomly week to week', 'what should we make next', 'I have too many ideas', or 'my team keeps reacting instead of planning.' Trigger even when the user never says the word 'diagnosis.'

jordangaston Bundle

Guides founders and product teams through rigorous customer/user research interviews. Use this skill whenever the user mentions customer interviews, user research, customer discovery, talking to users, validating a startup idea, interview guides, customer development, user interviews, discovery interviews, or wants help preparing questions for potential customers. Also trigger when users mention wanting to understand customer needs, test a value proposition, get feedback on an early product concept, or combat bias in customer conversations. This skill is especially relevant for early-stage founders but applies at any stage of product development.

jordangaston Skill

Guide users through creating a strategic plan using the Fairytale Strategic Planning framework (from Jason Cohen / A Smart Bear). Use this skill whenever the user mentions strategic planning, quarterly planning, OKRs, team planning, roadmap planning, figuring out what to work on next, prioritization for a team or company, or asks for help thinking through their business strategy and next steps. Also trigger when the user says "fairytale plan," "narrative plan," or references the Double Diamond design process in a planning context. This skill is especially useful for founders, product leaders, and engineering managers doing quarterly or annual planning cycles, but works for any team or individual trying to decide what matters most right now.

jordangaston Bundle

Facilitates extreme brainstorming sessions based on Jason Cohen's framework of pushing business dimensions to absurd extremes to unlock breakthrough ideas. Use this skill whenever the user wants to brainstorm, generate new ideas, rethink strategy, challenge assumptions, explore new business models, think about competitive positioning, shake up their roadmap, do a strategy exercise, or is feeling stuck in incremental thinking. Also trigger when users mention "extreme questions," "extreme brainstorming," "10x thinking," "reframe the problem," or want to break out of small/tactical thinking patterns. This works for any stage of company — from pre-idea founders to scaled businesses.

x-cmd Bundle

Root index of x-cmd skill0 sub-skills. Defines the OKR-style agent workflow (goal → rule-verified results → execute), skill discovery, and agent tooling preferences. Style: principle-first, concise, delegate specifics to authoritative external sources.

x-cmd Skill

IP address utilities — geolocation, subnet scanning, port discovery. Zero barrier — use with x-cmd or curl + standard networking tools. Use for "ip", "geolocation", "subnet", "port scan", "network".

x-cmd Bundle

Naming framework for x-cmd modules / commands / subcommands. Subjective + scenario-driven; the skill is a thin shell, NOT a rulebook. Three layers: investigate (goal), naming.<user-task>.yml (OKR + session record, a .rule file), naming.okr-creator.yml (meta-rule that audits the session).

andresnator Bundle

Trigger: PRD light, quick PRD, lightweight PRD, MVP requirements. Create lightweight PRDs for small features, internal tools, and early ideas.

andresnator Bundle

Create or refine Jira Spike tickets in Jira Markup. Use when the user wants a Spike, research ticket, investigation ticket, technical exploration, discovery work, research question, or SDD-ready Spike input.

andresnator Skill

Trigger: scope analysis, target boundary discovery. Delimit class/package/module scope.

andresnator Bundle

Trigger: deep plan, evidence-first plan, planificar a fondo, planificacion basada en evidencia, discovery plan. Discover decisions and plan executable work from repository evidence.

blacklanternsecurity Skill

Enumerates Active Directory domains and maps attack surface for penetration testing.

blacklanternsecurity Skill

Discover web application injection points and route to the correct exploitation skill during authorized penetration testing.

blacklanternsecurity Skill

Network reconnaissance, host discovery, port scanning, and OS fingerprinting. Produces a port/service map that the orchestrator uses to route to service-specific enumeration skills.

blacklanternsecurity Skill

Deploy webshells to IIS, Apache, or Tomcat web roots via SMB share write access. Use when a domain user has write access to a file share that maps to a web server's document root — write a webshell via smbclient/net use, then trigger it via HTTP for RCE. Covers PHP, ASPX, and JSP webshells, .NET impersonation for same-host lateral movement, and internal site discovery.

blacklanternsecurity Skill

Linux local privilege escalation enumeration and attack surface mapping.

blacklanternsecurity Skill

XMPP/Jabber service enumeration for Openfire, ejabberd, Prosody, and other XMPP servers. Trigger when ports 5222 (client), 5223 (legacy TLS), or 5269 (server-to-server) are found open. Covers authentication testing, user enumeration, MUC room discovery, and server fingerprinting. Do NOT use for AD enumeration or credential spraying — route those to the appropriate skills.

blacklanternsecurity Skill

Windows local privilege escalation enumeration and attack surface mapping.

blacklanternsecurity Skill

Deploy WAR files via Apache Tomcat Manager for remote code execution. Use when Tomcat Manager is accessible with valid credentials (manager-script or manager-gui role). Covers WAR generation, deployment via text API and HTML interface, reverse shell delivery, and cleanup. Common initial access vector after credential discovery via LFI, default creds, or config file exposure.

bm629 Bundle

Use when authoring a PRD (product requirements document) for a software or product project — turning a product idea into a comprehensive, plannable requirements doc. Guides the producer through the METHOD, not the outline: grounding the problem in evidence (jobs-to-be-done), defining measurable success metrics with guardrails, drawing a defensible MVP boundary, specifying functional + a non-functional taxonomy with numeric targets, writing testable acceptance criteria, keeping the problem→goal→metric→feature→AC chain traceable, naming dependencies, and surfacing risks + open questions — to a bar an engineer can plan milestones from. Also amends an existing PRD as a versioned, changelogged delta. Composes with a separate PRD template tool (the section structure) and a deep-research capability. Not for reviewing a finished PRD and not for authoring other document types.

bm629 Bundle

Use when reviewing or judging a finished PRD (product requirements document) to decide whether the downstream build can be planned from it — an acceptance gate, not authoring. Judges the PRD against a 12-condition plannability bar: the problem is evidenced (not asserted), users are concrete, success metrics are measurable (with guardrails where gameable), the MVP boundary is defensible, features + acceptance criteria are concrete, non-functional requirements carry numeric targets, the problem→goal→metric→feature→AC chain is traceable (no orphans), dependencies are named, no evidence is fabricated, and open questions are surfaced. Also reviews an AMEND as a delta-scoped review. Emits exactly `VERDICT: approve|revise` plus actionable findings. Approves a PRD that meets the bar (no false-revise on a thin one) and revises only on a real, named gap. Not for authoring or fixing a PRD, not for engineering design docs (specs, ADRs, RFCs), and not for other document types.

bm629 Bundle

Use when authoring or amending a test plan / QA verification plan — what to test, at what level, to what done-criteria, and the cases to run. Guides the METHOD, not the outline: deriving every case from a feature-spec behavior/AC or api-spec operation/error (never inventing one); the functional levels the project warrants; RISK-WEIGHTED catalog sizing (BVA/equivalence/decision-table/state-transition/pairwise, not the cross-product); a non-functional taxonomy (perf/security/accessibility WCAG 2.2 AA/compat/i18n) each with a numeric target where warranted; metric-threshold-on-a-named-dataset cases for ML/probabilistic behavior; and amending as a versioned delta with impact+risk regression selection — to a bar where a tester executes it with no questions, every behavior traced. Composes with a template tool + deep-research; consumes handed-in upstreams (feature-spec/api-spec/PRD/NFRs), never a blank page. Specs the cases, not the scripts; not the runbook, not the behavior contract, not reviewing one.

bm629 Bundle

Use when reviewing/judging a test plan / QA verification plan — deciding whether a tester can execute it and every behavior is covered. A gate, not authoring. Judges it against a single-sourced 10-condition bar: every handed-in upstream behavior (feature-spec/api-spec ops+errors, else PRD) has >=1 TRACEABLE case; functional levels fit; entry/exit testable (coverage floor + open-defect threshold); environments + test data specified; each case has preconditions + steps + observable result (a metric-threshold-on-a-dataset for ML) + traces-to; the catalog is RISK-WEIGHTED (coverage gap, padded/thin, OR combinatorial blow-up = a finding); each warranted non-functional type (perf/security/WCAG 2.2 AA/compat/i18n) carries a target; an amend is reviewed delta-scoped; nothing fabricated. Emits exactly `VERDICT: approve|revise` + actionable findings; approves a proportionally-sized plan, revises only on a named gap. Not for authoring it, the release runbook, design-review, or the test scripts.