Product & Planning

quocbao201104 Bundle

Evidence-informed marketing and founder-led sales decisions and execution. Use when the user needs to understand customers or markets; choose audiences, positioning, value, pricing, packaging or offers; diagnose weak or changing performance; create or critique marketing communication or brand identity; prioritize founder-led sales; plan or diagnose marketing channel execution across pages, email, social, paid media, search, or commerce; test, localize, or retain learning. Also use when symptoms imply these jobs, such as unclear differentiation, uncertain targeting, weak conversion, conflicting marketing signals, unclear commercial fit, or stalled buyer progress. Do not use for generic writing, mechanical content operations, product-roadmap, legal, finance/accounting, CRM administration, or unrelated technical work.

kesslernity Bundle

Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Builds a DRAFT stakeholder map for one project from the charter, organisation chart, RACI, governance terms, steering minutes, meeting notes and messages the user provides: a stakeholder register, interest and influence ratings each with its stated basis, stance as evidenced by a verbatim fragment with source and date, gaps, and a proposed engagement plan per stakeholder, every line traced to a source and every missing fact marked UNKNOWN. Use when the user asks to "build the stakeholder map", "who are the stakeholders on this project", "map interest and influence", "where does each stakeholder stand", "draft the stakeholder engagement plan" or "refresh the stakeholder register". Do not use for a customer account's stakeholders, use account-plan-builder instead; for a one-page brief before one meeting, use meeting-prep-onepager; for logging decisions and risks against the project, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

kesslernity Skill

Scores inbound leads against the qualification rubric the user supplies (criteria, scale, weights, thresholds and disqualifiers as given): one DRAFT scorecard per lead with the evidence quoted per criterion, UNKNOWN wherever the lead's information is missing, totals shown with and without the UNKNOWN criteria, a ranked list and a suggested next step such as a qualification call, a request for missing details, nurture or a courteous decline. Use when the user asks to "score these inbound leads", "qualify this lead against our rubric", "run the web form submissions through our lead criteria", "which of these leads should sales call first" or "build a lead scorecard". Do not use for preparing the first call with a lead, use discovery-call-prep instead; for an existing account's growth plan use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Builds a DRAFT proposal skeleton from a discovery summary (call notes, discovery brief, CRM record, emails) and the organisation's own proposal template: every template section in order, pre-filled only where the discovery material supports it with the source beside each line, and every section still needing a human input marked HUMAN INPUT with the owner role and the question to answer. Use when the user asks to "start the proposal for <prospect>", "build the proposal skeleton from the discovery notes", "pre-fill our proposal template", "what do we already have for the proposal" or "first cut of the proposal". Do not use for answering a formal RFP, RFQ or tender question set, use rfp-response-drafter instead; for turning a priced estimate into a statement of work use estimate-to-sow. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Triages a batch of customer support tickets (helpdesk export, shared mailbox, chat transcripts, web forms) into one row per ticket with category, urgency graded on the evidence in the ticket, suggested next action and owner, plus a DRAFT customer reply for every ticket that needs one, returned as one Markdown pack. Use when the user asks to "triage these tickets", "sort the support queue", "what needs an answer first", "categorise this backlog", "draft replies for these tickets" or "build today's queue review". Do not use for internal requests from colleagues, use request-intake-triage instead; for one long thread that needs handing over, use escalation-summary; for a personal mailbox, use inbox-triage. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Prepares a discovery call brief from what the user has on a prospect (CRM record, inbound form, emails, notes, public material the user supplies): what is known with sources, gaps against the qualification dimensions, hypotheses to test, questions in priority order and what to listen for. Returns a DRAFT Markdown brief in the chat. Use when the user asks to "prep me for the discovery call with <prospect>", "what should I ask on this first call", "intro call brief", "questions for the qualification call" or "what do we know before we speak to them". Do not use for scoring leads against a rubric, use lead-qualification-scorer instead; for an existing customer's account review use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.

kesslernity Skill

Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

kesslernity Bundle

Drafts an account plan from the CRM notes, emails, meeting notes and contracts the user provides: situation, stakeholder map, opportunities as recorded, risks, open commitments and proposed next actions, every line traced to a source and gaps marked UNKNOWN. Returns a DRAFT Markdown document in the chat. Use when the user asks to "build an account plan", "refresh the key account plan", "what do we know about this account", "account review for <customer>" or "what should happen next on this account". Do not use for preparing a first call with a prospect, use discovery-call-prep instead; for scoring inbound leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

alaimo-labs Skill

Have your synthetic personas critique a spec, PRD, or product idea — individual in-character reviews plus a panel synthesis

alaimo-labs Skill

Structure and quality bar for evidence-grounded feature specs — problem, user journey, critical user stories with acceptance criteria, and a falsifiable hypothesis. Use when writing a feature spec or PRD, defining user stories or acceptance criteria, mapping a user journey, or turning insights into a spec.

alaimo-labs Skill

Start product discovery — place the product on two axes (new/existing, commercial/internal) and capture its context plus a tagged, ranked list of unverified beliefs into product/overview.md, the context every other skill reads

loveliunian Bundle

把'完备性优先'的机器版 PRD 降维重排成'重点优先'的开发交接版(PRD-Lite)。事实零改动:字段/规则/阈值/流程语义逐一保留,只删冗余、改组织、压措辞。切片→按规则卡改写→装配守恒自检→独立反向对账,四阶段闭环,对账不过禁止交付。触发词:prd-lite、PRD转可读版、PRD瘦身、开发交接版、PRD降维。

loveliunian Bundle

读一份 PRD/需求文档（如 ch-07.md），两阶段产出：先做 PRD 预检并单独生成问题清单（prd_issues.json + issues.md，交付裁决）；blocking 问题全部裁决回填后，才生成详设（detail_design.json + 详细设计.md，只含定稿内容，机器强制零问题残留）。内置系统架构基线（技术栈/接口规范/全局规则，详设直接继承）；大 PRD 支持主会话+多 subagent 按 chunk 并行，输出过大时按 part 分片产出+merge_chunks.py 机器合并。触发词：PRD转详设、生成详设、问题清单、裁决回填。

loveliunian Bundle

读一份 PRD/需求文档（如 ch-07.md），两阶段产出：先做 PRD 预检并单独生成问题清单（prd_issues.json + issues.md，交付裁决）；blocking 问题全部裁决回填后，才生成详设（detail_design.json + 详细设计.md，只含定稿内容，机器强制零问题残留）。内置系统架构基线（技术栈/接口规范/全局规则，详设直接继承）；大 PRD 支持主会话+多 subagent 按 chunk 并行，输出过大时按 part 分片产出+merge_chunks.py 机器合并。触发词：PRD转详设、生成详设、问题清单、裁决回填。

alaimo-labs Skill

How to run a persona critique — a synthetic persona reviews a spec, PRD, or product idea in character and returns a structured rating with strengths, concerns, and suggestions. Use when critiquing a spec with personas, getting user feedback on a document, running a review panel, or stress-testing a PRD from the user's perspective.

alaimo-labs Skill

Interview one of your synthetic personas — exploration mode (open discovery) or validation mode (feedback on an idea)

alaimo-labs Skill

How to do secondary research and benchmarking for product discovery — provenance discipline, source hierarchy, research lanes (competitors, alternatives, pricing, trends), and mapping findings back to your unverified beliefs. Use when researching a market, benchmarking competitors, sizing an opportunity, or gathering existing knowledge about a product space.

alaimo-labs Skill

How to create rich, diverse synthetic user personas (archetypes) for product discovery — structure, design principles, and diversity requirements. Use when creating personas, user archetypes, synthetic users, or when the user asks to model their target users, segments, or audiences.

alaimo-labs Skill

How to frame a product opportunity — a problem for a segment, backed by signals, with no solution chosen yet — and keep it apart from solutions. Opportunity vs. solution vs. outcome, signals vs. proof, the value and viability beliefs of an opportunity, the research agenda, and the Opportunity Solution Tree as a file layout. Use when framing an opportunity, deciding whether something is a problem or a solution, working with an opportunity solution tree, or when an idea arrives as a solution and you need the problem underneath it.

alaimo-labs Bundle

How to roleplay a synthetic persona in a product-discovery interview, with two modes — exploration (open discovery of pains and workflows) and validation (structured feedback on a specific idea or solution). Use when interviewing a persona, simulating a user interview, roleplaying a user, or running discovery/validation conversations with synthetic users.

hi-donwi Bundle

Select the smallest set of available skills for a task. Use at task start or when the kind of work changes. Do not turn skill discovery into a mandatory sequence for simple edits.

hi-donwi Skill

Generate user-facing changelogs, release notes, upgrade notes, and internal change summaries from git history, PRs, issues, commits, or diff context. Use before releases or stakeholder updates. Do not use for code review, version control operations, or marketing copy unrelated to actual changes shipped.

first-touch-inc Skill

Convert a completed demo or discovery call into same-day follow-up, stakeholder expansion, and momentum touches without sounding automated. Drafts the buyer follow-up, champion thank-you, stakeholder intro, and a 3-day momentum touch from real meeting context; includes a no-show recovery path. Use right after a demo or discovery call, when the user says "we just had the demo," wants to multi-thread after a meeting, or needs to recover a no-show.

first-touch-inc Skill

When a champion or strong contact changes jobs, run a warm reactivation into their new company and protect the old account relationship. Drafts the congratulations note, the reconnect-when-settled follow-up, and the old-account stakeholder handoff; updates HubSpot when connected. Use when the user learns a champion moved - via a LinkedIn notification, a bounced email, an enrichment refresh, or a HubSpot update. This skill reacts to a known job change; FirstTouch does not monitor for job changes automatically.

kirrito-k423 Bundle

通过多轮对话，从童年经历、无意识胜任区、能量模式、顽固缺点和羡慕对象中寻找可迁移的底层天赋。用户希望认识自己的优势、寻找职业方向、理解怪癖或高耗能能力，或明确要求挖掘隐藏天赋时使用。

felipelobomotta-blip Skill

Builds 3-5 reader personas representing the book's target audience segments. Each persona has reading habits, emotional triggers, deal-breakers, discovery channels, and comp title preferences. Used by writer (voice calibration), evaluator (4-reader simulation), and packager (marketing targeting).

mohitagw15856 Skill

Stress-test a plan, strategy, PRD, or launch by simulating hostile expert personas who attack it from every angle. Use when asked to red-team, stress-test, pre-mortem, pressure-test, play devil's advocate, or find the blind spots in a plan before committing. Produces a per-persona critique, a ranked list of the most dangerous risks, a pre-mortem, and the specific changes that would most strengthen the plan.

mohitagw15856 Skill

Extrae y clasifica por riesgo las suposiciones ocultas en un brief de producto o PRD. Úsalo cuando te pidan revisar un brief de producto para identificar suposiciones, auditar un PRD para detectar riesgos, encontrar suposiciones ocultas, validar planes de producto o ejecutar un análisis de suposiciones. Produce un mapa de suposiciones priorizado con puntuaciones de confianza e impacto, métodos de validación recomendados e indicadores de suposiciones críticas.

affaan-m Skill

Use for file-driven multimodal image, video, and 3D-asset discovery; taste interviews; distill or apply workflows; style-pack validation; editable EDL/FCPXML export; provenance audits; and offline planning that must fail closed before provider generation.

mohitagw15856 Skill

Construye un marco de métricas para cualquier producto, equipo o negocio. Úsalo cuando se solicite un árbol de métricas, marco de KPI, métrica North Star, embudo AARRR, marco HEART, u OKR de métricas. Produce una jerarquía de métricas estructurada desde North Star hasta indicadores adelantados, con orientación sobre medición.

mohitagw15856 Skill

Transforma una lista de iniciativas priorizadas en una narrativa de roadmap estratégico convincente. Utiliza esta skill cuando se te pida redactar una narrativa de roadmap, explicar la hoja de ruta del producto a stakeholders no técnicos, conectar elementos del roadmap a objetivos empresariales, o producir una historia de roadmap compartible con ejecutivos. Produce una narrativa temática con contexto estratégico, arco de progresión trimestral, un resumen ejecutivo y una sección de 'qué no está en el roadmap'.

mohitagw15856 Skill

Escribir historias de usuario bien estructuradas con criterios de aceptación y casos extremos. Úsalo cuando te pidan escribir historias de usuario, crear tickets a partir de un resumen de características, convertir un PRD en historias o redactar criterios de aceptación. Produce historias listas para estimar en formato estándar con criterios de aceptación claros, casos extremos y definición de hecho.

mohitagw15856 Skill

Estructura y facilita sesiones de planificación de sprint. Úsalo cuando se te pida planificar un sprint, organizar elementos del backlog, asignar story points, crear objetivos de sprint o preparar agendas de planificación de sprint. Produce un objetivo de sprint, un backlog calibrado por velocidad, un plan de capacidad, señales de riesgo y una agenda estructurada de reunión de planificación de sprint.