Product & Planning

arozumenko Bundle

Use when a TMS test case needs manual execution, selector discovery, or defect investigation before automation — "analyse SCRUM-T101", "run this case and emit an AFS", any pre-automation case exploration. Produces an Automation-Friendly Spec (AFS); does not write test code.

arozumenko Bundle

Use when a stakeholder conversation, customer meeting, or user session is being planned or has just happened — even if the user only says 'I'm meeting them Thursday' or pastes raw notes. Runs two modes — PREPARE aggregates every open question, untested critical assumption, and unresolved escalation across the workspace into a themed, value-of-information-ordered guide filtered to what THIS interviewee can answer; SYNTHESIZE turns raw notes or a transcript into a durable evidence file and propagates the answers into the hypotheses they touch (evidence links, assumption verdicts, resolved questions). Trigger phrases — 'prep the interview', 'what should I ask', 'here are my notes', 'synthesize this interview', 'we talked to the customer'. NOT for triaging raw feature asks (intake-triage), NOT for team-internal meeting minutes, and NOT for fact-checking a document (deep-research factcheck mode).

arozumenko Bundle

Use when journeys and the backlog need reconciling — 'turn my journeys into hypotheses', 'map the journeys to the backlog', 'what do my journeys cover', 'convergence pass', 'where are the gaps in the backlog' — or proactively whenever new journey files exist that no hypothesis or epic references. Runs a convergence pass over every user journey (maps, list, BDD), every existing hypothesis, and (where one is configured) the project's issue tracker, classifying each journey COVERED / GAP / OUT-OF-SCOPE, regenerating the journey-coverage board, and on confirmation authoring the missing problem statements and hypothesis stubs with house frontmatter and collision-free IDs. NOT for authoring journeys themselves, NOT for promoting hypotheses, and NOT for breaking epics into stories.

swyxio Bundle

Diagnose, improve, or operate person-centered face matching across photo libraries, video, social profiles, directories, events, and other media when reference discovery, identity verification, detection failures, unknown people, or safe face-to-person assignment are involved. Use for face recognition and face-reference sourcing; not for generic image editing, image generation, or galleries without an identity-matching problem.

ivy00johns Bundle

Document and set up the living-plan convention: a front door (START-HERE.md), a strategic roadmap, tactical ledger, done-archive, and frontier doc, wired to an intake loop so reports become tracked entries instead of rotting. The ledger trio is often named by file — the "remaining" / "completed" / "future" set (REMAINING-WORK / COMPLETED-WORK / FUTURE). Use when the user says "set up a living plan", "make this plan a living doc", "stop my docs from rotting", "set up the remaining/completed/future files", "where are my remaining/completed/future md files", "my ledger is full of done rows", "sweep done rows to the archive", or wants a report-to-ledger intake loop. Key disambiguation: if the user asks for their "remaining / completed / future" files and THIS project lacks them, set the convention up HERE — never hunt across other repos; reading or editing one existing file is a normal file operation, not this skill.

ekinoxis-evm Skill

The x402 HTTP payment standard — charging for API access with HTTP 402, USDC settlement on Base, buyer and seller SDKs, facilitators, and agent-to-agent payments. Use when building a paid API endpoint, when an agent needs to pay per request, or when integrating the Bazaar discovery layer.

agentik-os Bundle

Forensic SEO content audit of a URL or site — on-page (title/meta/headings/images/internal links/URL), content quality (E-E-A-T), keyword + search-intent fit, technical SEO (robots/sitemap/canonical/CWV), content-gap analysis, featured-snippet + schema opportunities, and a prioritized strategy roadmap. Produces SEO-AUDIT.md with a /100 health score. Use when the user gives a URL and asks to audit/improve SEO, organic rankings, or search visibility — EN: "seo audit", "audit this page's seo", "why am I not ranking", "improve organic traffic", "on-page seo check", "content gap analysis"; FR: "audit seo", "audite le seo de cette page", "pourquoi je ne ranke pas", "améliorer mon référencement", "trafic organique", "analyse de contenu seo". Also triggers on: market-seo, /market seo <url>. NOT for ad copy, social posts, or generic marketing strategy (use market-ads / market-social / market). For deep technical-only SEO use /seoaudit.

agentik-os Skill

Marketing Report Generator (Markdown). Compiles audit + analysis outputs into one client-ready scored report: 6-category scorecard (/100), category deep-dives, competitor matrix, SEO snapshot, revenue-impact estimates, prioritized action plan, 30-60-90 roadmap. Use when the user wants a full marketing report / scorecard / assessment, or to consolidate prior /market audit results. Triggers (EN): "market-report", "/market report", "marketing report", "marketing scorecard", "marketing assessment", "compile the audits", "client report". Triggers (FR): "rapport marketing", "rapport de marketing", "bilan marketing", "scorecard marketing", "compile les audits", "rapport client". Do NOT trigger on running an individual audit (that is /market audit, /market seo, etc.) — this skill consolidates and scores their output.

agentik-os Skill

Offensive security pipeline for professional penetration testing. Passive recon, subdomain discovery, port scanning, vulnerability scanning, secret extraction, injection testing, auth bypass, attack-chain analysis, CVSS scoring, and automated PDF reporting. Use when user says "/hack", "/hack domain.com", "pentest", "pentest this", "security scan", "recon", "vulnerability assessment", "hack this", "scan this target", or in French "pentest", "test d'intrusion", "scan de securite", "reconnaissance", "evaluation de vulnerabilites", "audit offensif", "attaque ce domaine". Supports --recon, --osint, --scan, --deep, --inject, --report, --full flags. For web app security testing, see /secaudit. For code-level security audit, see /codeaudit + /apiaudit.

agentik-os Bundle

Research any topic from the LAST 30 DAYS across Reddit + X/Twitter + Web, synthesize what people are actually saying right now, then write copy-paste-ready prompts for the user's target tool. Handles recommendations (best/top X), news (what's happening with X), prompting (X prompts/techniques), and general discovery. Use when the user says '/last30days', 'recherche sur les 30 derniers jours', 'what are people saying about X', 'best/top X right now', 'latest on X', 'quoi de neuf sur X', 'trending X', 'X prompts examples', or wants a current, community-grounded answer instead of stale model knowledge.

agentik-os Skill

A/B Testing Plan Generator for paid ads. Creates structured testing roadmaps with prioritized test sequences, duration/sample-size calculators, statistical significance thresholds, hypothesis templates, and 90-day testing calendars for Meta, Google, and LinkedIn. Use when the user says "/ads testing", "ads A/B test plan", "creative testing roadmap", "what should I test next", "test priority", "split test plan", "plan de test ads", "roadmap de test publicitaire", "que tester en premier", "calendrier de test", "test A/B Meta/Google/LinkedIn".

agentik-os Bundle

Use when a founder, CAIO, solopreneur, or engineer has a 1-page PRD (or a chosen bet from vision-os, or a feature spec from company-ai-os) and needs to lock scope, decide the stack, scaffold, build ONE core loop, deploy, and record a LIVE deployed URL. The deliverable is a clickable deployed URL, never a plan or "next steps". EN triggers ship MVP, build my MVP, PRD to app, scaffold Next.js Convex Clerk Stripe, deploy to Vercel, weekend prototype, one-day MVP, week sprint, refactor to ship, deploy-only, build-os, ship it. FR triggers construis mon MVP, lance mon MVP, mets en prod, déploie sur Vercel, prototype du weekend, MVP en un jour, transforme ma PRD en app, refactor pour shipper. NOT for pure planning/strategy (use ideation-and-vision-architect), NOT for forensic audits (use /secaudit, /perfaudit, /a11yaudit).

agentik-os Skill

Interactive project scaffolding wizard with stack selection, theme, tokens, and ecosystem integration. Use when user says "/new-project", "scaffold project", "setup new repo", "create project structure", "bootstrap a project", "scaffolde un projet", "nouveau projet", "initialise un repo", or "crée la structure d'un projet". For scaffolding + full product pipeline (vision, PRD, brand, UX, build), see /new. For pipeline on existing projects, see /build. For rapid idea-to-MVP, see /team.

agentik-os Bundle

Concevoir un OS AgentikOS de bout en bout — interrogatoire de la vision et de la cible, recherche marché, primitive, modèle économique, matrice de parité concurrentielle, features en input/action/output, automatisations, couche IA et system prompts, modèle de données Convex, layout Stax, positionnement et séquence de release. Produit un blueprint markdown plus un artefact HTML navigable. Fonctionne pour un OS personnel (LiveOS, KnowledgeOS, ALT) comme pour un OS professionnel (ClubOS, Business OS). À utiliser dès que l'utilisateur mentionne un OS, veut concevoir un produit, lister des features, réfléchir à des automatisations ou à des agents IA, définir un modèle de données, un pricing ou un positionnement, ou parle de construire sur le stack Next.js / Convex / Clerk / Stripe / Stax. Déclencher même si l'utilisateur ne dit jamais le mot « OS » — toute demande de conception produit, de blueprint, de PRD, de liste de features, de modèle économique ou d'architecture produit passe par ce skill.

agentik-os Skill

Plan a content strategy — decide WHAT content to create and which topics to own (not how to write a single piece). Fires on "content strategy", "what should I write about", "content ideas", "blog strategy", "topic clusters", "content planning", "editorial calendar", "content marketing", "content roadmap", "content pillars", "what content should I create", "blog topics", "I don't know what to write" — and FR equivalents "stratégie de contenu", "quoi écrire / sur quoi écrire", "idées de contenu", "calendrier éditorial", "piliers de contenu", "plan de contenu", "feuille de route contenu". For writing individual pieces, see copywriting/mk-copywriting. For SEO-specific audits, see seo-audit. For social-media-specific content, see social-content.

jhamidun Bundle

Совместное написание дока: контекст → структура → тест свежим читателем. Триггеры: «напиши документ», «помоги написать RFC». НЕ PRD → feature-spec.

jhamidun Bundle

PRD и спеки фич: user stories, требования, критерии приёмки, метрики. Триггеры: «PRD», «напиши спеку». НЕ: RFC→doc-coauthoring; роадмап→roadmap-management.

jhamidun Bundle

Свежий B2B-список лидов по ICP (РФ): discovery → ЛПР → скоринг Hot/Warm/Cold. Триггеры: «поиск компаний», «список лидов». НЕ досье на одну компанию→account-research.

jhamidun Skill

Продуктовые метрики: OKR, north star, дашборды, еженедельные разборы. Триггеры: «продуктовые метрики», «собери дашборд метрик».

jhamidun Bundle

Внутренние коммуникации: статус-репорты, 3P-апдейты, рассылки, FAQ, инциденты. Триггеры: «апдейт для руководства», «письмо команде». НЕ апдейт под стейкхолдера→stakeholder-comms.

jhamidun Bundle

Продуктовый роадмап: RICE/ICE/MoSCoW, Now/Next/Later, capacity. Триггеры: «приоритизируй бэклог», «что пилим в квартале». НЕ спека фичи→feature-spec.

jhamidun Bundle

Апдейты для стейкхолдеров под аудиторию: статусы, отчёты, анонсы, риски. Триггеры: «апдейт для руководства», «недельный статус», «письмо про риск». НЕ рассылки/FAQ→internal-comms.

jhamidun Bundle

Свежий B2B-список лидов по ICP (РФ): discovery → ЛПР → скоринг Hot/Warm/Cold. Триггеры: «поиск компаний», «список лидов». НЕ досье на одну компанию→account-research.

majiayu000 Bundle

Convert tasks.md to prd.json with smart routing classification. Use after creating tasks. Triggers on: convert to prd, generate prd.json, convert tasks.

majiayu000 Bundle

Creates or advances sprints in prd.json. Use when starting new work cycles or closing completed sprints.

majiayu000 Bundle

Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs

majiayu000 Bundle

Interactive vision planning using Socratic method. Use when user asks to "ralph plan vision", "plan a vision", "ralph plan roadmap", "ralph plan stories", "ralph plan tasks", or needs to define product vision/roadmap/stories/tasks through guided dialogue.

majiayu000 Bundle

Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.

majiayu000 Bundle

Generate comprehensive Product Requirements Documents (PRDs) for product managers. Use this skill when users ask to "create a PRD", "write product requirements", "document a feature", or need help structuring product specifications.

majiayu000 Bundle

Order backlog items using RICE, MoSCoW, or Value-Effort frameworks. Use when prioritizing backlog, ranking features, or ordering work items. Triggers on keywords like "prioritize", "RICE score", "MoSCoW", "rank backlog", "order by value".

majiayu000 Bundle

Interactive review of auto-generated Ralph artifacts. Use when user asks to "ralph review stories", "ralph review tasks", "ralph review roadmap", or needs to validate planning artifacts against their intent.

majiayu000 Bundle

Generate technical implementation plan and task list from PRD and architecture documents

majiayu000 Bundle

This skill should be used when generating implementation tasks from PRDs, decomposing features into atomic tasks, inferring dependencies, or mapping PRD content to task metadata.

majiayu000 Bundle

PRD generation knowledge, templates, and compilation guidance for creating AI-optimized Product Requirements Documents

majiayu000 Bundle

SpecFlux REST API for creating and managing projects, PRDs, epics, tasks, and acceptance criteria. Use when running /prd, /epic, /task, or /implement commands to create or update entities in SpecFlux via HTTP API. Use when creating PRDs, epics with tasks, adding acceptance criteria, updating task status, or marking criteria as complete.

majiayu000 Bundle

[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].