Product & Planning

herchila Skill

Builds a founder presence on TikTok through short-form video strategy and content planning. Use when you want to grow on TikTok, need video content ideas, want to reach a younger audience, need to plan a TikTok content strategy, or want to use short-form video for product discovery. Triggers on: "TikTok strategy", "short-form video", "TikTok content ideas", "grow on TikTok", "video content plan", "TikTok for business", "viral video ideas", "reels strategy"

herchila Skill

Builds genuine presence on Reddit for founder distribution and community engagement. Use when you want to use Reddit for marketing, need to identify which subreddits your users are in, want to engage authentically without getting banned, need to research competitors through Reddit, or want to do customer discovery on Reddit. Triggers on: "Reddit marketing", "find my users on Reddit", "post on Reddit", "subreddit strategy", "Reddit community engagement", "launch on Reddit", "customer discovery Reddit"

herchila Skill

Tracks growth experiments, A/B tests, and product bets in a structured way so learnings accumulate over time. Use when you're running multiple experiments, need to design a test with clear success criteria, want to review what you've tried and learned, or feel like you're running experiments but not learning from them. Triggers on: "track this experiment", "set up an A/B test", "what experiments are we running?", "review our learnings", "design a test", "did this experiment work?", "experiment backlog"

jackneil Skill

Roadmap advisor — weighs a coverage-matrix read plus plans, issues, commits, and lifecycle to decide the single highest-leverage initiative and forge a ready-to-run /goal brief. (repo)

jackneil Skill

Use when asked to analyze product completeness, find gaps, figure out what to build next for best-in-class coverage, audit feature depth across user types, or create a prioritized roadmap for a product. Triggers on "what's missing", "gap analysis", "10/10", "best-in-class", "coverage audit", "feature completeness", "what should we build", "is it actually easy to use", "workflow friction", "how automated are we really".

jovd83 Bundle

Stakeholder-reporting skill for Cypress execution results. Use when Codex needs to turn raw Cypress runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.

evan-daruwalla Bundle

READ-ONLY roadmap rollup for PRD_ROADMAP.md conventions: parses "- [ ]" checkboxes, ☐/☑ table glyphs, ~~struck~~ items (dropped, NEVER open), milestone headings; per-milestone done/open/struck, overall %, first open item as "next:". Fork-aware — a CURRENT DIRECTION section scopes by default, --all covers the whole file. Use when: "milestone status", "roadmap rollup", "how much of the PRD is done", "what's next on the roadmap". Never edits the PRD. Zero deps.

hainrixz Skill

Opt-in fixer (the /claude-seo-ai:fix command). Applies the safe, deterministic SEO/AI-search fixes from a persisted audit to the user's site — meta viewport/charset/lang, JSON-LD, robots.txt AI directives, hreflang, sitemaps, OG/Twitter cards, image dimensions, canonical, AI discovery files — through the adapter that matches the platform (local files, Shopify theme/Admin, WordPress REST/WP-CLI, page APIs, or step-by-step instructions). Dry-run preview by default; writes only after explicit per-change confirmation. Runs only when the user invokes it — never auto-triggered.

hainrixz Skill

Analyze and score only a page's AI-search visibility (GEO/AEO) — answer extractability, fact density, AI-crawler access and Google AI-feature snippet eligibility, entity linking, AI discovery files, and agent-readiness — and report an AI Visibility score with a citability breakdown, plus optional unscored probes (web-search presence, Search Console generative-AI impressions). Read-only. Use for "will AI engines cite this?", GEO/AEO, or ChatGPT/Perplexity/Google AI Overviews/Gemini optimization.

hainrixz Skill

Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured data/schema, meta tags, Core Web Vitals, robots.txt, sitemaps, or AI discovery files, or how it ranks in Google and is cited by AI engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude).

hainrixz Skill

Audit and generate sitemaps and discovery files — validate XML sitemap presence/size/extensions/lastmod, check robots.txt referencing and sitemap-to-canonical consistency, reconcile orphans against the link graph, and produce repaired sitemap entries plus a robots.txt Sitemap line. Module M17. Feeds the Search SEO score.

hainrixz Skill

Audit AI discovery files and agent endpoints at the site root — /llms.txt and /llms-full.txt structure and link health, /agents.md, the UCP merchant profile at /.well-known/ucp (only when no ecommerce module owns it), the ARD /.well-known/ai-catalog.json, and /sitemap_agentic_discovery.xml — plus a robots cross-check that these files are not blocked for the bots meant to read them. Module M21 "AI discovery & agent endpoints" (weight 0 — reported, never scored). Appears in the AI Visibility report only.

hainrixz Skill

Acquire a page or site into the shared PageSnapshot every audit module reads — real HTTP status chain, headers, robots directives, raw HTML on disk, parsed document, optional headless-Chrome render with a raw-vs-rendered delta, and once-per-run site artifacts (robots, sitemaps, AI discovery files). Acquisition is done by the bundled scripts (snapshot.mjs / crawl.mjs), never by WebFetch. Records the data tier reached.

realdougeubanks Bundle

Holistic codebase audit that auto-detects the stack and produces a prioritized improvement roadmap with level-of-effort estimates.

mokhtarabadi Skill

Migrates a flat tasks/ directory into the V6 Kanban folder structure (backlog, in-progress, qa, completed, archive).

mingyuepop Skill

项目开发路线图规划。基于产品概述和模块依赖，规划功能的开发顺序和里程碑。

yuriyarhat-cyber Bundle

Plan a strong discovery call. Use when Codex needs to structure a sales discovery call, define the call goal, prepare questions, sequence the conversation, and identify what must be learned before moving forward.

yuriyarhat-cyber Bundle

Write a short sales follow-up sequence. Use when Codex needs to create follow-up messages after a lead conversation, proposal, missed reply, or discovery call, including timing logic and message progression.

stark-ai-de Bundle

Interview fuzzy Claude Code coding requests into user-verified implementation specs with source challenge, ADR gate, validation plan, and execution prompt. Use when the user asks for /claude-spec-interviewer, a Claude Code implementation plan, PRD, requirements, plan before coding, Plan Mode planning, persisted spec, ADR decision, CLAUDE.md evidence, or .claude/rules evidence. Do not use for direct implementation, pure brainstorming, memory cleanup, or authoring Claude instruction files only.

stark-ai-de Bundle

Interview fuzzy Cursor Agent coding requests into user-verified, Cursor-ready implementation specs. Use when the user asks for a spec, implementation plan, PRD, requirements, or a plan before coding for a feature, bugfix, refactor, migration, repo-wide change, or architecture task, or needs acceptance criteria, validation commands, ADR decisions, or rollout notes. Saves the spec and a Cursor execution prompt. Do not use for fully specified tasks or direct implementation requests.

stark-ai-de Skill

Write a concise PRD or implementation brief from current context, separating problem, solution, user stories, decisions, testing, rollout, and out of scope. Use when the user asks for a PRD, product brief, implementation brief, or spec handoff.

stark-ai-de Skill

Convert a spec, roadmap item, or rough plan into independently implementable issue slices with scope, dependencies, acceptance criteria, and validation. Use when the user asks to split work into GitHub issues, local markdown tasks, or agent-ready implementation chunks.

wso2 Skill

Use for a scoped change to an existing PRD — adding a feature, adding an actor, or going deeper on a feature. The instruction names the scope; touch nothing outside it.

wso2 Skill

Use when kicking off a project from its idea, or re-running /start on a project that already has a PRD.

wso2 Skill

Use when generating a project's design from its PRD — the /design flow that turns specs/requirements/prd.md into the cell-first design under specs/design/, then mints the validation criteria. Also the flow for converging an existing design onto an amended PRD.

wso2 Skill

Use for settling an unsettled point in an existing PRD — challenging an assumption the agent flagged, or answering an open question nobody has filled. The instruction names the point; a bare instruction means the whole Open Questions list.

wso2 Skill

The shape of specs/requirements/prd.md — its sections in order, the story-numbering rules, and what the PRD deliberately excludes. Use whenever writing or amending the PRD.

carlos-algms Skill

Load before any Jira interaction or mcp__atlassian__* call. Holds required field values (team ID, sprint IDs, custom field mappings) unavailable elsewhere; skipping causes missing fields on created tickets. Triggers: Jira URLs, ticket keys (e.g. ABC-123), MCP tools mcp__atlassian__*, acli, or keywords create/read/edit/search/transition, ticket, Jira, issue, sprint, backlog, refinement, work item.

domengabrovsek Skill

Breaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when the user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

hjewkes Bundle

Jira and Confluence integration for Atlassian Cloud. Use when the user needs to search issues, manage sprints, read Confluence docs, create/update pages, work with epics and backlogs, or any Atlassian workflow. Triggers include "jira", "confluence", "sprint", "backlog", "ticket", "issue", "epic", or references to Atlassian content.

hjewkes Bundle

Use when creating, finding, installing, reviewing, or managing Claude Code skills — covers skill authoring, discovery, conventions, and lifecycle management

mimukit Skill

Turn a rough feature or change into a structured plan document (docs/plans/plan-<slug>-YYYY-MM-DD.md) before any code: brainstorm the approach, settle the big decisions, and write a plan that can be hardened and turned into issues. Use when the user says "plan this feature" or "brainstorm a plan/PRD/spec", the front of the plan → grill → file workflow. It stops at the plan document; it files no issues and writes no code.

mimukit Bundle

Own the GitHub issue lifecycle in five modes: create issues from a plan or description, start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle, priority, and title gaps. Use when the user says "create issues from this plan", "file an issue", "open a GitHub issue", "log this as a task", "add this to the backlog", "make issues for these TODOs", "start issue #42", "close #42", "sync my issues", "triage the backlog", "set the priority on #42", "relabel #42", "rename issue #42", or "fix the titles on these issues". It runs the tracker only; it writes no plan and no code.

tech-leads-club Skill

Generate code using Nx generators — scaffold projects, libraries, features, or run workspace-specific generators with proper discovery, validation, and verification. Use when user says "create a new library", "scaffold a component", "generate code with Nx", "run a generator", "nx generate", or any code scaffolding task in a monorepo. Prefers local workspace-plugin generators over external plugins. Do NOT use for running build/test/lint tasks (use nx-run-tasks) or workspace configuration (use nx-workspace).

akachandan1 Skill

Content strategy and 90-day roadmap specialist. Builds content pillars, CEP matrix, competitor whitespace analysis, and channel strategy. Use when user wants a content strategy, 90-day plan, content roadmap, pillar map, or mentions "content strategy", "content pillars", "90-day plan", "content roadmap", "channel strategy", "what to create", or "content planning".

akachandan1 Bundle

Designs a complete, brand-specific GTM (go-to-market) engineering system — lead collection, enrichment, segmentation/scoring, nurturing, outbound infrastructure, outbound management, social listening, community-led growth, referral/advocacy loops, partnerships, paid/ABM, PLG motion, tool stack, budgets, and a 90-day build roadmap. Use this whenever the user wants a GTM plan, GTM engine, outbound system, sales pipeline machine, lead-gen system design, cold email infrastructure, signal-based prospecting, social listening system, referral program design, or asks "how do I get leads/meetings/pipeline for {brand}" — even if they don't say "GTM". Also use when the user injects brand details and asks for a custom go-to-market or growth-engineering plan. Do NOT use for writing a single email/post/sequence (content skills), for closing-stage sales work like proposals and objection handling (sales skills), or for pure content/SEO strategy — this skill designs the pipeline SYSTEM, not individual assets.