Product & Planning

jperezduerto Skill

Build, extend, and operate Sherlock — an OSINT tool for hunting usernames across social networks and online platforms. Use when the user asks about Sherlock, OSINT username enumeration, social media footprinting, account discovery across platforms, or building a digital profile of a target. Covers installation, single and bulk username searches, output formats (text, CSV, XLSX), filtering by site, proxy and Tor support, NSFW site inclusion, false positive mitigation, and integration with theHarvester and SpiderFoot for comprehensive OSINT investigations.

jperezduerto Skill

Operate AutoRecon — a multi-threaded network reconnaissance tool that automatically runs appropriate enumeration tools based on detected services. Use during OSCP labs, CTF initial enumeration, or real-world external/internal network pentests to automate the discovery phase. Covers installation, target specification, port scan profiles, per-service tool execution, custom plugins, output structure, concurrency controls, and a full OSCP/CTF enumeration workflow.

jperezduerto Skill

Use and operate Subfinder — a fast passive subdomain enumeration tool by ProjectDiscovery that queries dozens of passive DNS data sources simultaneously. Use when performing subdomain discovery during recon, configuring API keys for maximum source coverage, integrating passive enumeration into recon pipelines with httpx and nuclei, or chaining with active tools for full-spectrum recon-to-exploit workflows. Covers installation, all flags, provider-config.yaml setup with all supported API key providers, output formats, recursive enumeration, rate limiting, silent mode, stdin/stdout piping, and complete pipeline integration. GitHub: https://github.com/projectdiscovery/subfinder (13.4k stars).

jperezduerto Skill

Operate Feroxbuster — a fast, recursive content discovery tool written in Rust for brute-forcing files, directories, and endpoints against web servers. Use when performing web content enumeration, finding hidden paths, discovering API endpoints, or recursively walking directory structures. Covers installation, wordlists, extensions, filtering, recursion, rate limiting, output formats, auto-tune, scan resumption, and comparison with ffuf, gobuster, and dirsearch.

oldwinter Bundle

帮助用户养成定期与客户互动的可持续习惯，以确保产品开发是由现实需求而不是内部假设驱动的。

oldwinter Bundle

通过识别干系人的激励、通过联系消除冲突以及利用共同创造来建立共享所有权，帮助用户掌握无需正式授权的领导艺术。

oldwinter Bundle

通过应用严格的评分、财务建模和投资组合平衡，帮助用户从被动的功能构建转向战略性的资源分配。

drmoisan Skill

Invoke the prd-feature worker to produce feature-document outputs from issue and research inputs.

drmoisan Skill

Umbrella sequencing skill for the domain-neutral legacy discovery and parity-definition workflow. Use when onboarding or running the end-to-end discovery workflow across inventory, coverage, runtime characterization, parity, behavior reconciliation, and the validation gate, and when reconciling upstream analyzer and agent contract names. Holds the canonical Referenced Contracts registry.

drmoisan Skill

Produce or refresh the parity matrix in the discovery workflow. Use when building the parity matrix from feature contracts and runtime characterization evidence and routing parity reasoning to the parity role. Fifth stage, after runtime characterization and before behavior reconciliation.

drmoisan Skill

Drive the language-neutral repository and project inventory analyzer for the discovery workflow. Use when running the inventory stage against the domain profile source and target roots, recording analyzer outputs under the profile artifacts root, and running stack-specific analyzers generically per the profile technology stack. Second stage after profile load.

drmoisan Skill

Produce feature contracts and the coverage ledger from inventory output in the discovery workflow. Use when deriving the feature contract set and the migration coverage ledger from the repository inventory and routing coverage review to the coverage role. Third stage, after inventory and before runtime characterization.

drmoisan Skill

Canonical validation-gate mechanics for the discovery workflow. Use when running the per-artifact discovery validators after each stage and the completion gate at the end, interpreting the empty-error-list pass semantics, and routing any validator error back to the owning stage skill. Seventh and final stage.

drmoisan Skill

Capture unspecified or contradictory behavior and reconcile it into product decisions in the discovery workflow. Use when recording unspecified-behavior findings from the parity matrix and reconciling them into product-decision records via the reconciler role. Sixth stage, after parity and before the validation gate.

drmoisan Skill

Produce runtime characterization scenarios and evidence references in the discovery workflow. Use when characterizing observed runtime behavior of the legacy application into scenarios with supporting evidence and routing analysis to the runtime role. Fourth stage, after coverage and before parity.

khurrummahmood Bundle

Build the human-approved project profile that complements /adapt-project discovery. Reads repository facts first, then interviews the user about purpose, maturity, critical workflows, risk posture, desired direction, intentional tradeoffs, known-bad legacy patterns, and do-not-break surfaces. Writes draft artifacts under reports/project-interview/scan-<TS>/ by default; durable .engineering/project/profile.yml, profile.md, and open-questions.md require --apply.

khurrummahmood Bundle

Walk existing prose surfaces (BACKLOG.md, lessons.md, plan files) and propose candidate ledger intakes for the items already named there. Read-only by default — emits a candidates JSON and a report. Hands off to /brainstorm-ideas (via its helper script) for the actual write, so the dedup, validation, and origin discipline stay in one place. Read .claude/docs/idea-ledger.md when authoring or debugging this skill.

khurrummahmood Skill

Arrive at an ideal or near-ideal repo folder structure and organization approach under framework/tool/human constraints. Use when a project has historical top-level folders, source/input/output dumps, KB/spec/eval/runtime boundaries, or a proposed directory map that needs recursive folder summaries, ideal-vs-constrained topology review, boundary discovery, folder-worth judgment, deterministic move-plan options, dry-run validation, and a safe implementation approach. Not for one-off file moves or Python package prefix clusters.

mr-kelly Bundle

Busabase-backed App-in-Skill idea desk that works like a business consultant — it interrogates a product or business idea until it is sharp, then carries it through professional, visual BRD, MRD, and PRD documents. Use when the user invokes $kelly-ideas or /kelly-ideas, wants to capture or shape a product/business idea, asks for a BRD/MRD/PRD, says they have a product idea but cannot describe it clearly, or wants an idea shaped into a spec that $kelly-app-skill-creator can build into a real app.

mr-kelly Bundle

Influencer/creator marketing command desk (Busabase App-in-Skill) — the agent sweeps and fit-scores creator candidates, drafts outreach and briefs, and gates content before it ships; the human reviews creator cards, approves outreach/briefs/contracts, and tracks campaign ROI. Use when the user invokes $kelly-creators or /kelly-creators, mentions influencer or creator marketing, creator discovery, fit scoring, outreach DMs, campaign briefs, UGC, sponsorship or partnership deals, content review / FTC disclosure gating, or campaign ROI, or wants to review/approve agent-drafted creator outreach before it is sent through other channels.

mr-kelly Bundle

Personal App-in-Skill voice-of-customer desk (Busabase App-in-Skill) aggregating user feedback from support email, Discord/Slack communities, X replies, app-store reviews, surveys, and interviews into clustered feature requests and a roadmap decision queue. Use when the user invokes $kelly-feedback or /kelly-feedback, or mentions user feedback, voice of customer, feature requests, roadmap decisions, feedback clustering, feedback triage, request dedupe, changelog replies, decline replies, or reviewing what users are asking for.

tmj-90 Skill

Use when writing a Product Requirements Document — to define what to build and why, with evidence-gated drafting. Refuses to draft without a real problem, user, and metric. Triggers on "write a PRD", "product requirements", "spec for this feature", "what should we build for X", or "requirements document".

tmj-90 Skill

Use when prioritising a feature backlog using RICE scoring (Reach, Impact, Confidence, Effort) or making a capacity-constrained prioritisation decision. Triggers on "prioritise these features", "RICE scoring", "what should we build first", "rank the backlog", or "capacity planning for the sprint".

tmj-90 Skill

Use to propose the next product work for a repo — on an idle factory tick (nothing ready to deliver) or when a human asks "what should we build next", for product ideas, a backlog, or PO mode. Consults Memory for product direction, inspects the repo, and files 3–5 high-leverage, anti-slop candidates into the Dispatch backlog as draft tickets with real acceptance criteria. Invoke whenever the factory needs new work proposed rather than delivered.

tmj-90 Skill

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources. Triggers on "product discovery", "validate this idea", "opportunity solution tree", "discovery sprint", "assumption mapping", or "de-risk this bet".

kirkruglov Bundle

Draft a client proposal and quote from discovery call notes or a brief. Turns raw, unstructured notes into scope, deliverables, timeline, three pricing packages, and a cover letter. Use when writing a client proposal, preparing a quote, или отправляешь КП после звонка. Triggers: 'write a client proposal', 'draft proposal and quote', 'turn my notes into a proposal', 'напиши предложение клиенту', 'пропозал и смета'.

kirkruglov Bundle

Critical review of PRDs, feature specs, and product decision documents — acts as a devil's advocate to surface weak assumptions, missing requirements, implementation risks, and logical gaps. Use when a PM or team lead wants to stress-test a document before team review, validate a spec before development starts, or identify what's missing in a product decision. Triggers RU: «проверь PRD», «разбери спецификацию», «найди дыры в PRD». Triggers EN: 'review my PRD', 'challenge my spec', 'find holes in my PRD', 'critique my feature spec'. Do not use for writing or rewriting PRDs.

kirkruglov Bundle

Investigate metric anomalies — build a ranked hypothesis framework and stakeholder narrative from a plain-language description. Use when a dashboard number drops or spikes unexpectedly. Triggers: 'investigate metric anomaly', 'my metric dropped', 'расследуй аномалию метрики', 'у меня упала метрика'.

kirkruglov Bundle

Analyze survey CSV files and extract quantitative frequencies, qualitative themes, and Top-3 insights. No Python required — Cowork-native. Use when reviewing Google Forms/Typeform/SurveyMonkey exports, preparing stakeholder reports, or turning raw survey data into actionable findings. Triggers: 'analyze survey results', 'survey results analyzer', 'проанализируй результаты опроса', 'анализ опроса'.

kirkruglov Bundle

Transform sprint notes into a structured stakeholder doc: delivered, deferred, risks, next focus. No Jira needed. Use when preparing sprint review or stakeholder updates from free-form PM notes. Triggers: 'sprint review summary', 'summarize sprint results', 'итоги спринта', 'оформи итоги спринта'.

kirkruglov Bundle

Interpret A/B test results in plain language and get a ship/rollback/extend recommendation with a stakeholder summary. Use when you have experiment results from any analytics tool and need a clear go/no-go decision. Triggers: 'interpret experiment results', 'read my A/B test results', 'should I ship this experiment', 'интерпретируй результаты эксперимента', 'помоги прочитать результаты A/B теста'.

kirkruglov Bundle

Analyze backlog files (CSV or Markdown) to flag problematic items and generate a structured grooming agenda. No Jira API needed — works entirely with local exports. Use when preparing for sprint grooming, auditing accumulated tasks, or reviewing the backlog after a sprint. Triggers: 'groom my backlog', 'backlog grooming assistant', 'подготовь повестку груминга', 'груминг-ассистент', 'проверь бэклог на проблемы'.

kirkruglov Bundle

Synthesize a folder of mixed local files (articles, notes, excerpts) into a structured thematic report with key findings and gaps. Use when consolidating research before writing a report, PRD, or strategy doc. Triggers: 'synthesize my research folder', 'research synthesis', 'turn my notes into a report', 'синтезируй папку с исследованиями', 'синтез ресёрча', 'сведи файлы в отчёт'.

kirkruglov Bundle

Extract recurring profiles from real CustDev transcripts and generate evidence-backed persona cards. Use when synthesizing interviews into personas for product docs or roadmap. Triggers: 'synthesize personas', 'create user personas', 'extract personas from transcripts', 'синтезируй персоны', 'создай персоны из интервью', 'извлеки персоны из транскриптов'.

kirkruglov Bundle

Extract JTBD statements from custdev transcripts and interview notes. Synthesizes multiple md/txt files into a prioritized JTBD map with evidence quotes and frequency counts. Use when converting custdev notes to structured jobs, preparing for roadmap sessions, synthesizing interview patterns. Triggers: 'extract jobs to be done', 'JTBD from interviews', 'синтез custdev заметок', 'извлеки JTBD из интервью'.

kirkruglov Bundle

Synthesize user interview transcripts and feedback files into a prioritized insight report with themes, quotes, and open questions. Use when analyzing batches of user interviews, support tickets, or survey responses. Triggers: 'synthesize feedback', 'analyze user interviews', 'user feedback report', 'синтезируй фидбек', 'разбери транскрипты', 'отчёт по фидбеку'.