Product & Planning

cikichen Bundle

Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.

syntax-syndicate Bundle

When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch-strategy. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

compozy Skill

Perform comprehensive research and analysis using multiple discovery and analysis tools to provide a solid foundation for complex tasks.

khazp Bundle

Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".

dmytri Skill

Use this skill to run the Shipshape Captain role: human-facing discovery, durable specs and assets, Captain-only notes, blocker resolution, and outbound decisions. Default entry for new product intent and any user conversation.

duckduckgo Skill

Use this skill to update Android library dependencies via refreshVersions. Invoke when the user asks to update, bump, or refresh dependencies or a specific library version, asks what updates are available, or hands over a dependency-update task from the Asana backlog. Covers running refreshVersions, judging which bumps are safe, handling libraries blocked by the project's Kotlin version, running the E2E suite, and the PR/Asana conventions for the change.

duckduckgo Skill

Use this skill to execute a task from the Android Agentic Maintenance Backlog. Invoke when the user provides an Asana task URL from that backlog and asks to run, start, execute, or work on it. Also invoke when the user says things like "run the next maintenance task", "work on this backlog item", or "pick up a maintenance task". Requires the Asana MCP to be configured.

duckduckgo Skill

Use this skill to interactively scope a maintenance idea into a properly formatted task for the Android Agentic Maintenance Backlog. Invoke when the user wants to add a task to the maintenance backlog, scope a new maintenance idea, or says things like "I want to add something to the backlog", "help me scope a maintenance task", or "can we add this as a maintenance item".

kkokosa Skill

Plan the implementation of a roadmap step — reads the issue, relevant docs, and enters plan mode

ksmyl Bundle

How to write and manage ASPICE-compliant requirements. Use this skill when creating stakeholder requirements (STR), system requirements (SYSRS), or software requirements (SWRS). Also use when analyzing requirements for quality (atomicity, testability, ambiguity), establishing bidirectional traceability, writing verification criteria, performing consistency checks, or when you see references to SYS.1, SYS.2, SWE.1, or any requirement-related base practices (BP1-BP8). Especially important for the SWE.1.BP6 cross-link requirement between SWRS, SYSRS, and SYSARCH.

kweaver-ai Bundle

Generate complete Chinese PRD documents from rough product requests. Use when the user asks to create, refine, or standardize a PRD, turn ambiguous requirements into an Agile-friendly product requirements document, or fill a PRD template by first asking focused clarification questions and then saving the final markdown file.

kweaver-ai Bundle

Generate complete Chinese implementation design documents from a product PRD. Use when Codex needs to turn PRD content into a High-Level Design plus Low-Level Design document, ask focused clarification questions for missing implementation details, follow a fixed design template, apply C4-based architecture design, and save the final result as a markdown design file.

linuxlewis Bundle

Run Ralph Wiggum autonomous coding loops. Use when user asks to run ralph, start autonomous coding, execute a PRD, implement features from a task list, or wants Claude Code to work through user stories iteratively.

linyindong Bundle

Build or improve professional PRDs, BRDs, requirement sections, and product decision artifacts from rough Chinese/English notes, prototypes, historical PRDs, meeting notes, or early ideas. Use when the user is ready to write, rewrite, translate, structure, enrich, or polish requirement content, especially for platform capability, workflow, configuration, governance, cross-system, or fintech product work. Invoked internally by platform-product-orchestrator, or directly when the user names this skill; for a natural-language request that does not name a skill, platform-product-orchestrator is the entry point.

linyindong Bundle

Model cross-system product flows, state transitions, exception paths, callbacks, retries, rollback, reconciliation, migration, and manual fallback for platform, workflow, back-office, and fintech requirements. Use when creating, clarifying, or reviewing flows before PRD writing, scope decisions, product direction, or PRD review. Invoked internally by platform-product-orchestrator, or directly when the user names this skill; for a natural-language request that does not name a skill, platform-product-orchestrator is the entry point.

linyindong Bundle

Review PRDs, product requirement drafts, platform designs, prototypes, and requirement sections with PRD-quality-first judgment, document-specific findings, product-logic closure, and artifact-size calibration. Use when the user asks to check, review, validate, score, find gaps, help a PM improve the next PRD version, assess whether logic is closed-loop, compare small-feature vs 0-to-1 platform readiness, or decide whether a PRD is ready for product review, engineering review, RFC follow-up, or further scope clarification. Invoked internally by platform-product-orchestrator, or directly when the user names this skill; for a natural-language request that does not name a skill, platform-product-orchestrator is the entry point.

linyindong Bundle

Core collaboration and routing layer for complex product, platform, and fintech mid-platform work. Use when direction is unclear, a business problem needs to be abstracted into platform capability, a request needs decision support before writing, cross-system ownership or operational risk must be reasoned through, or the user needs routing among PRD building, scope governance, and PRD review. Invoked internally by platform-product-orchestrator, or directly when the user names this skill; for a natural-language request that does not name a skill, platform-product-orchestrator is the entry point.

microck Skill

Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP. Use when the user needs bulk processing, scheduled discovery, change detection, or a stable integration surface.

ludo-technologies Skill

Discover candidate JavaScript/TypeScript, Go, Rust and C++ repositories for polyscan false-positive auditing via WebSearch. Rotates languages and themes, mixes popular and obscure projects. Appends new candidates to `.polyscan/audit/queue.md`. Designed for periodic invocation.

mehdiforoozandeh Skill

Evolve crux itself — add a capability or fix a recurring flaw in the crux tool, end to end: ideate → build → validate → ship. Turns a feature idea or a "crux keeps doing X" annoyance into a signed-off PRD, a tests-first implementation, a hard validation gate (selftest green · stdlib-only · existing vaults still load · version/migration), and a pull request. Works for anyone contributing to crux, not just the maintainer; the maintainer self-merges and cuts releases. Use when working ON crux — adding to the engine/CLI/skill, picking up a backlog epic from `.spec/` (UI, wiki, marketing), or fixing an engine bug. Triggers: "evolve crux", "add a feature to crux", "crux keeps <doing X>", "improve crux", "contribute to crux", "send a crux PR", crux roadmap, crux backlog, wiki/GUI/autoresearch for crux.

mergemat Bundle

Writes a durable implementation brief for an agent without overfitting to current file paths. Use when user wants to turn context, a bug report, PRD, plan, or conversation into an agent-ready issue, task brief, or implementation contract.

rodri-oliveira-dev Skill

Use this skill when changing project discovery, MSBuild evaluation, .NET SDK/framework detection, project classification, normalized inspection results, fixture repositories, or the JSON inspection contract in DotNetRepoInspector. Do not use it for unrelated repository documentation or generic C# refactoring.

rohitgehe05 Bundle

Use before drafting any non-code knowledge-work deliverable, including strategic memos, business reviews, OKR defences, PRDs, decision docs, briefing docs, exec talking points, Slack messages to leadership, frameworks, post-mortems, one-pagers, BRDs. Triggers on asks like "help me write up X", "draft this memo", "what should I say to Y", even casually phrased. NOT for software implementation; for creating features, components, or code changes use superpowers:brainstorming instead; for authoring the PRD document itself, use this skill. For non-code deliverables this skill supersedes generic brainstorming. Do not skip for simple asks; simple tasks hide the costliest assumptions.

rohitgehe05 Bundle

Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it ships, such as "review this doc", "poke holes in this", "is this ready to send". Works on any doc, not just mindpowers-drafted ones. Not for code review.

rohitgehe05 Bundle

Use when a user wants to test, sharpen, frame, or gather evidence for a customer or business problem before pitching a direction, prioritising work, or writing a PRD.

romiluz13 Bundle

Discover the documentation needed for a coding task's behavior and constraints. Use for documentation discovery only, including relevant language rules and interactions between technologies.

romiluz13 Skill

Use only when explicitly asked to manage a waiver, goal, or open obligation in the optional experimental Proofline CLI. Missing documentation in an ordinary coding task is handled by DDD discovery.

runkids Bundle

Full-cycle feature discovery, evaluation, and prioritization. Builds a persistent knowledge base at .feature-radar/ and runs a 6-phase workflow to recommend what to build next. Modes: full (all phases), quick (scan only), evaluate (prioritize), #N (deep-dive one). MUST use this skill whenever the user asks about feature priorities, roadmaps, what to build, or wants to evaluate/compare feature ideas — even if they don't say "feature radar" explicitly. Use when the user: - Asks "what should we build next?", "what's most impactful?", or similar - Wants to prioritize, rank, or compare features or backlog items - Needs roadmap planning, project direction, or strategic feature decisions - Says "help me prioritize", "review our backlog", "what are we missing" - Mentions .feature-radar/ directory or feature tracking - Wants periodic reassessment of deferred or open opportunities

runkids Skill

Discover new feature opportunities from creative brainstorming, user feedback, ecosystem trends, and cross-project research. Writes results to .feature-radar/opportunities/. MUST use this skill when the user wants to GENERATE new ideas — not evaluate existing ones. Trigger on any request to brainstorm, explore, discover, or find new feature ideas, even casual ones like "I wonder what else we could do" or "give me ideas". Use when the user: - Asks "what else could we build?", "give me feature ideas", "what are we missing?" - Wants to brainstorm, explore new directions, or refresh the opportunity backlog - Says "scan ecosystem", "scan opportunities", "find new features" - Asks to review GitHub issues, community feedback, or adjacent tools for inspiration - Mentions "explore", "discover", or "new directions" in a feature context - Has a vague idea: "I have an idea", "what if we...", "I was thinking about..." Do NOT use for evaluating/prioritizing existing features — that's feature-radar's job.

selfxyz Bundle

Read-only queries for Self Agent ID data — look up agents by address or ID, list agents for a human, check own identity, retrieve ZK-attested credentials, reputation scores, freshness status, and A2A agent cards. Use when the user asks to "lookup agent", "agent credentials", "check agent status", "find agents", "agent discovery", "agent card", "agent info", or "list agents for human". Do NOT use for verification middleware or adding verification to APIs — use verify-agents for that.

carlvellotti Skill

Draft a stakeholder update email using past updates for tone

carlvellotti Skill

Write a specific PRD section grounded in project research and goals

avinava Bundle

Write structured technical documents — design-doc, adr, spec, api-contract, architecture, handoff, design-handoff, discovery, test-report, postmortem, proposal, runbook, onboarding, tutorial, how-to, reference, explanation, mulesoft — as Markdown in the repo by default. Use when asked to write or restructure one of those types, including RFCs, ADRs, developer handoffs, API writeups, test summaries, discovery briefs, or MuleSoft project docs. Produce designed HTML or PDF only when asked. Do not use for casual edits to existing markdown, metric-led reports (analytical-document-design), slides (presentation-design), standalone charts or diagrams, restyling a file into HTML unprompted, or Mule markdown refresh when mule-docs is installed.

build-your-sales Skill

Run the full BYS targeting methodology on the French market — Discovery (10 questions), CAB-P matrix, 10 ciblages (signal × persona × geo) backed by real French companies fetched via the data.gouv MCP and the API Recherche d'entreprises. Use after /data-gouv-bys:setup to produce the strategic brief and lead lists.

checkpickerupper Skill

Create GitHub issues from a plan, bug, finding, audit or PRD, whose titles a stranger can act on. Use when filing issues or turning work into issue-sized slices. Builds every title as what somebody wrote or did followed by what the system did with it, refuses words that exist only inside the codebase, and reads each title cold before publishing. Splits issues by whether anything visibly breaks; cuts vertically and sizes each to one fresh context window; sequences a wide refactor as expand-migrate-contract; puts the breakdown to the user before publishing anything; and wires real GitHub sub-issue edges rather than prose references.

con-benksl Bundle

Beginner onboarding for VPS networking and proxy operations. Use when the user has a first VPS, does not know where to start, or needs a plain-language explanation of domains, ports, DNS, inbound/outbound, proxies, dual stack, routes, or node protocols. This workflow teaches and routes; factual discovery belongs to netops-scan. 典型中文请求：第一次买 VPS 不知道从哪开始、这些术语是什么意思、自建和机场有什么区别、我该选哪种协议。