Product & Planning

kalyvask Skill

Turn customer-discovery notes into a defensible, falsifiable problem statement (Stage 03). Forces specificity on the desperate customer, the single pain, the trigger, frequency, magnitude, alternatives, and behavioral evidence of desperation. Use when the user has finished a batch of discovery and needs to crystallize what they found before designing a solution.

kalyvask Skill

Track and steer a customer-discovery sprint across many interviews — surface recurring patterns, score desperation across the batch, and flag when the user is talking to needy vs. desperate customers or has stopped too early. Use when the user is in the middle of customer discovery (Stage 02), running multiple interviews, and wants to know what the data is telling them so far.

kalyvask Skill

Help the user write a PMF-grade value hypothesis — three components (what / who / how) plus a separate leap-of-faith statement. Pushes back on vague *whos*, compound *whats*, and confusing the value hypothesis with the leap of faith. Use when the user is in Stage 04, when they say "help me write my value prop / hypothesis," or when they've finished customer discovery and need to commit to a specific bet.

miles990 Skill

產品管理：PRD撰寫、用戶故事、OKR設定、路線圖規劃

momentmaker Bundle

Author a PRD-style spec before writing implementation. Use when the user says "write a spec", "PRD", "design doc", "spec out", "let's plan this", or invokes /spec. Produce a written, reviewable artifact (problem, scope, non-goals, acceptance criteria, open questions). End with `jutsu swarm doc-review <spec.md>` to surface gaps before declaring done.

vemodalen-x Bundle

Design structured diagnostic or tutoring prompts and agent workflows that interview the user, locate constraints, configure style/depth, produce a plan, and loop through assessment and feedback. Use when asked to create or improve a Human 3.0-style self-discovery prompt, a Mr. Ranedeer-style tutor prompt, a coaching/custom GPT prompt, an onboarding interview, a diagnostic agent, a personalized learning flow, or any multi-turn prompt that must ask questions before advising.

xucroyuri Bundle

仅有粗略想法、图像、主题或情境，需要提炼出值得开发的立意时使用。

bsamiee Skill

Orchestrates two-round parallel agent research with Exa orientation, breadth-first discovery, and depth-focused synthesis. Use when conducting comprehensive research, exploring complex topics requiring multi-source validation, or synthesizing findings from distributed investigation streams.

immamdouhaboammar Bundle

Use when the user needs to design creator roles across discovery, media, affiliate, and commerce with clear economics and measurement; route here only when this decision boundary is the clear owner.

immamdouhaboammar Bundle

Use when the user needs to improve retrievability and truthful representation across AI answer surfaces; route here only when this decision boundary is the clear owner.

jdchi Skill

Helps harness natural curiosity as a tool for learning, discovery, and avoiding errors from other psychological biases.

kerberosclaw Skill

Use when a durable technical decision was just made in conversation and should be recorded, or when user asks to write/record an ADR (開 ADR / 記個決策 / 這要不要 ADR). Runs a three-gate check FIRST and actively talks the user out of writing one when the decision doesn't qualify — then writes a lightweight (title + 1-3 sentences) ADR following the repo's own ADR conventions if any exist. Repo conventions always override this skill's defaults. NOT for requirement specs (spec / prd-create) or for rewriting history (superseded ADRs get a new ADR, never an edit).

kerberosclaw Bundle

Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from fuzzy idea or existing active spec through requirements, technical plan, tasks, implementation, verification, and closure report. Auto-detects project/spec state, writes persistent files under specs/, asks one grounded question at a time when requirements are ambiguous, and stops at stage gates. NOT for stakeholder PRDs (prd-create), ADO ticket breakdown (prd-breakdown), single architecture-decision records (adr), or already-frozen tasks that should simply be implemented.

kerberosclaw Skill

Use when the user says 先討論 / wants to align on a fuzzy idea before building, or before any non-trivial implementation whose requirements are still ambiguous — interviews the user until shared understanding is confirmed, one question at a time, each with a suggested answer; facts answerable from the filesystem/code are looked up, never asked. Optionally maintains the repo's CONTEXT.md glossary when vocabulary settles during discussion. Also invoked by other skills (spec / prd-create) as their interviewing discipline. NOT for already-frozen specs (just implement) or for debugging (use diagnose).

kerberosclaw Bundle

Use when user wants to draft a PRD (Product Requirements Document) from raw input (meeting transcripts, hand-waved descriptions, scattered decisions). Workflow: load org's PRD Guideline + writing discipline → lock execution mode (human-run vs unattended-agent-run) → ingest raw input → quiz user numbered-list iterate to fill §1-§15 → draft v0.1 → handle stakeholder merge (review feedback, surface conflicts) → lock v1.0 + sanitize per ADO publication contract → publish to ADO Wiki. For an agent-run PRD, §13 carries the unattended-execution discipline (machine-checkable AC + traffic-light + 3-exits + stop-and-ask), aligned with goal-engineer's loop-run-protocol. NOT for packaging an ALREADY-FROZEN build spec (approved ADR / locked design / machine-checkable AC) into an unattended dispatch — that is goal-engineer's lean build dispatch. Pure prompt-driven — Claude is the runtime, no Python helper. Trigger phrases: 寫 PRD / PRD 撰寫 / prd-create / 初版 PRD / 起 PRD.

kerberosclaw Bundle

Use when the user wants to AUTHOR an unattended dispatch for either: (1) a goal-driven evaluator-optimizer loop of the GENERATE-AND-SELECT kind (generate candidates → grade against a rubric → iterate by reason-code → keep the best; the human picks the final selection), or (2) a lean build-to-spec run whose build spec is ALREADY FROZEN (approved ADR / locked design / accepted machine-checkable AC) and the only missing piece is the unattended-execution wrapper. A fresh-session agent runs the dispatch hands-off while the human only watches traffic-light push notifications. Interview-style forcing questions lock the spec, then it emits a self-contained dispatch markdown + a channel-agnostic notification protocol. This is the upstream SPEC AUTHOR, NOT a runtime: the dispatch is run by Claude Code's /goal, a headless `-p` session, or any unattended agent — /goal is the engine, this writes what you feed it. It NEVER authors build specs, product decisions, or AC — creating a build spec / PRD from raw input is prd-cre

kerberosclaw Bundle

Use when user wants to break a PRD into Azure DevOps work items via vertical-slice plan. Workflow: read PRD → quiz user to lock durable decisions → draft slices with HITL/AFK + blocked_by → call az CLI directly via Bash to create items + Predecessor relations. Idempotent re-runs via fingerprint markers embedded in description. Pure prompt-driven — Claude is the runtime, no Python helper, no install ceremony. Trigger phrases: prd-breakdown / 拆 PRD / 切 vertical slice / 推 slice 到 ADO.

kerberosclaw Skill

Use when the user is unsure which kc_ai_skills workflow skill to use, or describes work involving PRD, SD/software design, FR, AC/acceptance criteria, ADR, tickets, implementation, debugging, release checks, or unattended agent execution. Triage the request with at most one clarifying question when needed, explain the route in plain language, then hand off to the right specialist skill. This is an entry router only: it does not write PRDs, specs, ADRs, tickets, or dispatches itself.

sahirvhora Skill

Use when you need to turn a list of config debt findings into a phased, client-ready 90-day remediation plan with sprint-by-sprint actions.

sahirvhora Skill

Use when you need to generate structured discovery questions for a new or existing SF client -- adapted to what is already known about their tenant.

sahirvhora Skill

Use when you need to run a complete SAP SuccessFactors EC config debt workshop -- discovery questions, assessment, scoring, and 90-day roadmap -- from a $metadata XML or live tenant.

sahirvhora Skill

Use when you need to turn sap release notes into a tenant-specific test plan and stakeholder briefing.

allenai Bundle

Create, configure, and monitor AutoDiscovery runs — either via the hosted service (`asta autodiscovery`) or via the local CLI (`asta-autodiscovery`). Use when the user asks about their runs, experiments, discoveries, wants to check status, or wants to start a new discovery run.

andysolomon Skill

Picks up a bug ticket filed by arc-bug-finder (in GitHub Issues, GitLab, or Linear), critically reviews and re-validates it, then implements, verifies, and ships the fix — branch, conventional commit, PR, and ticket update. Reviewing is the core competency: it re-reproduces the defect, confirms the cited root cause still exists, and chooses the best fix rather than trusting the ticket blindly. Delegates plan formatting to arc-planning-work, commit/PR mechanics to arc-conventional-commits / arc-git-pr-check. TRIGGER when: user asks to fix/resolve/implement a filed bug, points at a bug ticket or issue number, says "fix this bug", "resolve W-######", or "work the bug backlog". DO NOT TRIGGER when: user is reporting a NEW bug or asking "why is this happening" (use arc-bug-finder to research + file first), or planning greenfield features (use arc-defining-work).

andysolomon Bundle

Destination router for new work-item creation across GitHub Issues, Linear, or Agile Accelerator. Use when asked to create stories, build a backlog, define work from codebase analysis, or convert requirements into tracked work items and the destination tracker is not yet fixed. Do not use for implementation planning of existing work.

andysolomon Bundle

Implementation planning for existing tracked work items. Use when asked to plan an existing GitHub issue, Agile Accelerator story, or PRD before coding begins. Produces ordered tasks, file-level changes, test strategy, acceptance-criteria mapping, and synchronized docs/<ID>-IMPLEMENTATION_PLAN.md plus docs/<ID>-progress.txt artifacts. Do not use to create new user-story backlogs.

andysolomon Bundle

PRD-to-GitHub-issues slicing with tracer-bullet vertical slices. Use when converting a PRD into independently grabbable GitHub issues, reviewing slice granularity, or creating implementation tickets from a PRD. Do not use for implementation plans of existing issues.

lensetek Skill

The PRD Generator takes the product scope, objectives, and user flows defined by the Product Manager and drafts a detailed, structured, and developer-ready Product Requirement Document (PRD).

lensetek Skill

The Developer Scrum Master facilitates Agile methods, manages the sprint backlog, designs sprints, translates the PRD into developer tasks (tickets), and resolves development blockers.

lullabot Bundle

Draft concise, verified issues, tickets, and bug reports that maintainers can triage and discuss. Use when filing a GitHub issue or Jira ticket, reporting a bug, writing a feature request or task, filling in an ISSUE_TEMPLATE, filing a Drupal.org issue, or grooming vague tickets in a backlog. Covers titles, descriptions, acceptance criteria, reproduction steps, and labeling.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is starting a new role in demand generation, growth marketing, revenue operations, or marketing operations. Trigger phrases include: "just started a new role," "first week," "new job," "starting as director," "inherited this function," "new company," "what should I do first," "30 60 90 day plan," or any request to build a structured entry plan for a demand gen or RevOps role. Also trigger when the user has been in a role for fewer than 90 days and is trying to diagnose what they have, figure out what to fix first, or prepare for an early stakeholder presentation. Do NOT trigger for general career advice, job search questions, or onboarding for product management or engineering roles. This skill is specifically for demand generation, growth marketing, and RevOps leaders entering a new B2B SaaS role.

weorbitant Skill

Use when the user wants to find what to learn next, explore learning topics, get project ideas for a skill gap, or add a learning idea to their backlog. Triggers on: "what should I learn", "suggest learning projects", "I want to learn X", "add to my learning backlog", or "find me resources on X".

whiteknightonhorse Skill

Publish ACP commerce discovery

whiteknightonhorse Skill

Publish OAuth/OIDC discovery metadata

zarif3624 Bundle

Create or update a strategy for a complex B2B sales opportunity. Use for deal reviews, account planning, stakeholder mapping, champion development, competitive strategy, stalled deals, executive alignment, resource decisions, or deciding the next best action for an active opportunity.

zarif3624 Bundle

Plan a buyer-specific B2B product demonstration, technical validation, proof of concept, or demo follow-up. Use when deciding what to show, tailoring a demo to discovery, mapping features to outcomes, assigning presenters, preparing questions, or preventing generic feature tours.