Product & Planning

serialexperimentslainnnn Skill

Standards for managing technical debt and refactoring legacy code. Use when writing or triaging a technical debt register or TODO/FIXME backlog, deciding what debt to pay and how to fund it (fixed capacity slice, boy scout rule, dedicated cleanup project), refactoring code smells (long method, god class, feature envy, primitive obsession, shotgun surgery), adding characterization or golden-master tests to untested legacy code, running large-scale migrations with strangler fig, branch by abstraction, expand/contract and parallel change, debating a full rewrite, reading SonarQube/CodeScene/Code Climate reports, cyclomatic complexity and maintainability index thresholds, change-coupling and hotspot analysis over git history, or separating a refactor commit from a behavioural change.

serialexperimentslainnnn Skill

Reactive network fault diagnosis method — bisecting the path, forming a falsifiable hypothesis and proving root cause. Use when something "doesn't connect", is intermittent, slow or hangs mid-transfer and you are reaching for ping, traceroute, mtr --report, ss -tin, ip route get, ip neigh, arping, ethtool -S, tshark or dumpcap, capturing pcap simultaneously at both endpoints, curl -v --resolve, openssl s_client, nc -zv, socat, iperf3 -R with -P and -u, /proc/net/nf_conntrack and ephemeral port exhaustion, PMTU blackhole with ICMP fragmentation-needed filtered, TIME_WAIT and listen-backlog overflow, keepalive versus middlebox idle timeout, IP address conflict or MAC flapping, broadcast storms and layer-2 loops, ARP/ND caches, IPv6 preferred over working IPv4 and Happy Eyeballs, TLS-inspecting proxies, tail-latency percentiles versus averages, bpftrace, bcc tools, pwru, hubble observe, kubectl debug --image=nicolaka/netshoot across pod and node netns, or VPC flow logs — and when you must record what was tried,

montgomery-pixel Bundle

Turn a sales-call transcript or rough call notes into two files. CALL NOTES (facts with verbatim quotes, every number the prospect gave on its own line, the ICP in the prospect's own words, deal economics, what the seller promised, open questions) and a next-call SKELETON (standalone fact bullets the seller can read aloud, not a script). Use when the user says "discovery sheet", "call notes from this transcript", "debrief this call", "what did they actually say", "prep the next call", "skeleton for the follow-up", "ICP in their words", "what did I promise on the call", or drops a transcript, recording export or notes file after a sales, discovery or intro call.

ontology-of-everything Bundle

Transcribes a confirmed concept model into traceable PRD and colocated specification files only when the user explicitly invokes $concept-prd. Use to preserve purposes, behavior, synchronizations, assumptions, exclusions, open decisions, and acceptance provenance without redesigning the model.

ontology-of-everything Bundle

Generates PRD files from a confirmed concept model only when the user explicitly invokes $concept-prd-cn. / 仅在用户显式调用 $concept-prd-cn 时转录概念 PRD。

zerofaultlabs Bundle

Find, evaluate, and adapt timely social content ideas for Spring Hills Church from current Instagram accounts, trend roundups, discovery feeds, hashtags, or other web sources. Use when Codex needs fresh carousel, graphic, reel, story, invitation, weekend, community, Scripture, or non-sermon content ideas; a short trend brief; source-backed inspiration; or an assessment of whether an outside format fits Spring Hills. Use the installed write-spring-hills-social skill for voice and copy, and never copy another church's wording or identity.

peterson-benhame Bundle

Turns decided work — a PRD, design doc, RFC, or thread — into tasks a builder can act on without guessing. Finds slices that each prove something, grounds them in the code, and writes intent, observable criteria with concrete values, the boundary, what the change disturbs, and only the decisions that are hard to reverse. Walks every surface the work exposes and sweeps the nine unwritten requirements, recording each landing as a criterion already in the source, existing behaviour, n/a, or Unresolved — never as a criterion the walk invented. Defaults to one task per source. Use when the user says "write the task", "cut this PRD into tasks", "turn this design doc into work", or "pbs-plan". Do NOT use for discovery itself or to implement — a one-line ticket is a decision; a blank wish is not.

peterson-benhame Bundle

Interviews an unshaped idea into a verdict and a design document with literal decisions for pbs-plan. Use when the user says "research this", "help me understand this problem", "should we build this", "discovery", "explore this problem", or "pbs-discover". Do NOT use when the shape is already decided (pbs-plan), or to implement.

peterson-benhame Bundle

Scores how completely an implementation fulfills a PRD/spec, case by case, and produces a single comparable final grade. Invoke only when explicitly named (e.g. run spec-driven-eval); do not auto-trigger. Use when benchmarking spec-driven implementations, grading acceptance criteria, evaluating whether a feature was 100% implemented, comparing multiple implementations of the same PRD, or auditing implementation and test coverage (unit and e2e) against product requirements. Do NOT use for planning or building features (use pbs-spec-driven), writing PRDs, or general code review unrelated to a spec.

eminboydak Skill

Use when testing serial communication with real hardware (Arduino, ESP32, USB-UART adapter). Guides loopback test, port discovery verification, signal line testing. Triggers on hardware test, serial test, loopback, Arduino, ESP32.

rmazrim Skill

Auto-discovers project verification surface (test/lint/typecheck configs), runs the minimal verification suite, and gates every completion claim on machine-parsed exit codes and assertion output. Returns UNVERIFIED rather than silent on discovery failure.

johnson68878-ops Bundle

Software supply chain security reference for OpenSSF Scorecard, SLSA, Sigstore, SBOM, and posture/backlog taxonomies.

shivani26singh Skill

Generate enterprise-grade QA artifacts from requirements: manual test cases, BDD scenarios, automation assessment, a Requirement Traceability Matrix (RTM), and coverage gap analysis. Use when a tester provides a user story, acceptance criteria, PRD/BRD, specification, wireframe, screenshot, or supporting document and wants traceable Story → Acceptance Criteria → Test Case coverage. Produces only evidence-supported artifacts and flags missing information as clarification gaps rather than inventing behavior.

shivani26singh Skill

Triage a batch of defects instead of grinding through them one by one. Use when a lead says "triage these bugs", "prioritize the defect backlog", or pastes a list of open issues that need sorting. Groups likely duplicates, proposes severity/priority, routes each to a component or owner, flags reports missing information, and summarizes backlog health. Every duplicate and routing is a suggestion for a human to confirm — it never auto-closes, merges, or reassigns silently.

steffencarlsen Bundle

Creates and maintains an agent-owned goal ledger that pairs with long-running coding work, compaction recovery, chained engineering goals, or codebase status tracking. Use when the user says "$goal", "/goal mode", "start a goal", "continue this goal", "chain goals", "agent progress ledger", "flight recorder", "implementation notes", or asks the agent to save progress separately from a PRD. When the runtime exposes a native goal tool (for example Codex `/goal`), couple the file ledger to the runtime goal objective. Keeps `GOAL.md` as the contract and `implementation-notes.html` as the canonical readable state for progress, decisions, validation, compaction resume, blockers, and next-goal links.

steffencarlsen Bundle

Turn the current conversation, repository findings, issue discussion, or feature plan into a Product Requirements Document. Use when the user invokes to-prd, asks for a PRD, wants a feature spec, or needs implementation decisions captured before issue breakdown.

steffencarlsen Bundle

Break a PRD, feature spec, plan, or issue into independently implementable vertical-slice issues. Use when the user invokes to-issues, asks to split work into tickets, wants a Kanban-ready breakdown, or needs implementation tasks with dependencies.

cnproduct Bundle

Safely set up, diagnose, and verify OpenAI Secure MCP Tunnel connections from ChatGPT or another supported OpenAI surface to a private or local MCP server. Use when the user asks to connect localhost or an internal MCP server to ChatGPT, configure tunnel-client, troubleshoot tunnel discovery or readiness, or review a WebCodex-style wrapper. Do not use for ordinary public MCP endpoints, subscription-quota workarounds, or unsupported claims about model access or billing.

samraddhashrivastavatech Skill

Discover connected Android devices (USB, Wi-Fi, emulator), report serials, states, and capabilities, and confirm uniqueness before a session starts. Use when a device list is needed or a device is not visible.

samraddhashrivastavatech Skill

Android Debug Bridge engine — server, device discovery, connect/pair, and transport-level diagnostics. Use for any ADB server lifecycle work, device pairing, connectivity checks, or transport troubleshooting.

samraddhashrivastavatech Skill

Build and validate search query families — operator-aware variants tuned per intent (discovery, exact, technical, verification, contradiction…). Use whenever a topic needs more than one good query.

samraddhashrivastavatech Skill

Extract outbound links from a page. Use to discover hubs, citations, related resources, or the frontier of a crawl.

prince-vince Skill

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

prince-vince Skill

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

prince-vince Skill

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

prince-vince Bundle

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, and registry discovery.

samraddhashrivastavatech Skill

link-discovery

orcaqubits Skill

Set up a UCP project — scaffold a merchant server or platform client with discovery profile, SDK installation, and project structure. Use when starting a new UCP implementation.

rlawoals0529 Skill

Work backlog tickets unattended until each one converges - no duplication, no bugs, no tech debt - committing on a real branch and never pushing. Use when stepping away from the machine and wanting the backlog worked rather than parked, or when a ticket needs iterating to "as good as it gets" rather than merely finished. Triggers on "going afk", "work the backlog", "run the backlog on ABC-82", "iterate this ticket until it is clean", "/unattended-run".

breroz Skill

Run a comprehensive codebase cleanup audit and produce a detailed technical debt report — without modifying any code. Use this skill whenever a user wants to audit a codebase, identify dead code, find unused assets, surface technical debt, review dependencies, check for duplicate logic, or create a cleanup roadmap. Triggers include: "audit my codebase", "find dead code", "what can I delete", "cleanup report", "technical debt", "what's unused", "dependency review", "find duplicates in my code", "codebase health check", "what should I refactor", "find legacy code", "what can I remove safely", "cleanup roadmap", or any request to analyze a codebase for improvement opportunities — even if the user doesn't use these exact words. Always use this skill when the user shares a codebase and asks what can be simplified, removed, or improved.

breroz Skill

Use this skill when a user wants to turn a validated product idea or market research document into a full technical implementation guide. Triggers include: "build a blueprint for", "create a PRD", "implementation guide", "technical spec", "system design", "how do I build", "turn my market research into a plan", "create a product spec", or any request to go from idea/validation to a structured build plan. Always use this skill when the user uploads a Market Validation Document (PDF, DOCX, or MD) and wants to generate a technical blueprint, PRD, or implementation plan from it. Also triggers when the user pastes market research findings and asks what to build or how to build it.

breroz Skill

Use this skill whenever a user wants to validate a product idea, research market demand, analyze customer pain points, or understand what real users are saying about a problem space. Triggers include: "validate my idea", "is there a market for", "what do people on Reddit say about", "market research", "customer discovery", "do people actually want", "Reddit intelligence", "voice of customer", or any request to evaluate product-market fit using online conversations. Always use this skill when the user mentions a product, startup idea, SaaS concept, or tool they are building or considering — even if they don't explicitly say "market research."

breroz Bundle

Produce a comprehensive, read-only technical-debt and cleanup audit of a codebase — dead code, duplicate logic, legacy features, architectural issues, unused dependencies, database cruft, and security risks — delivered as a structured Markdown report with per-item confidence/risk ratings and a phased cleanup roadmap. Use this skill whenever the user wants to clean up, audit, or analyze a codebase for technical debt, asks "what can I safely delete", or mentions dead/unused code, unused dependencies, unused exports or imports, duplicate utilities, legacy or deprecated code paths, refactoring opportunities, code reduction, or wants a cleanup plan or roadmap — even if they never say the word "audit". The skill NEVER modifies, patches, or deletes code; it only reports. It traces dynamic imports, route and DI registrations, reflection, framework conventions, and config references before flagging anything, so it is the right tool any time accuracy about what is actually unused matters.

breroz Skill

Run a full organic distribution intelligence analysis for a product launch — no ad budget, no audience, founder-led growth. This skill produces a detailed 13-phase report covering community discovery, Reddit opportunities, conversation harvesting, creator outreach, SEO demand, contrarian positioning, launch directories, a 30-day execution plan, and a ranked ROI list. Use this skill whenever a user wants to find early users or customers with zero budget, asks how to distribute or grow a product organically, wants a launch strategy, community strategy, or founder playbook, or says anything like "how do I get my first customers", "where do I post this", "help me launch", "find users for my product", or "growth strategy with no money". Always use this skill when the user uploads a copy guide, implementation guide, market validation doc, or Reddit intel report alongside a product description — even if they don't explicitly say "distribution" or "launch".

samber Bundle

Designs an open-source project's ongoing distribution mix after the launch window - registry metadata, code-host discovery surfaces, curated lists, downstream packaging, extension and connector marketplaces, the release stream, dependency-graph position, creator seeding, and procurement trust signals - ranked against real maintainer capacity. Use whenever a maintainer asks how people will keep finding the project, which registries or awesome lists to target, why adoption flattened after launch, how often to release for visibility, or how to spend limited maintainer hours on distribution - even if they only say nobody is using it. Not the launch itself - use samber/developer-relations-skills@oss-launch. Not the build-in-public practice.

alanpai Bundle

開發進度全貌視覺化——讀專案的 progress.md 與路線圖文件（如 docs/sdd-roadmap.md），畫出三層式進度地圖（已完結階段橫幅／里程碑軌道＋「你在這裡」／當前里程碑步驟放大鏡），並搭配固定四段白話敘事。只要使用者問「進度到哪」「全貌」「現在什麼階段」「完成了哪些」「後面還有什麼」「路線圖現況」「幫我看專案狀態」，或在多里程碑的開發專案裡要求視覺化現況，就使用本 skill——即使對方沒說「圖」或「視覺化」這些字。