Product & Planning

lidessen Bundle

Guide for authoring effective Agent Skills using principle-based approach (Progressive Disclosure, Respect Intelligence, Enable Discovery). Covers creating, improving, refactoring, and reviewing skills. Use for skill authoring, design questions, best practices, anti-patterns, or structure decisions.

devenkhatri Bundle

Use this skill whenever the user wants to create or improve a presentation — academic OR corporate/professional. Academic triggers: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'grant proposal', 'make slides for my paper'. Corporate triggers: 'solution proposal', 'sales pitch', 'executive briefing', 'strategy deck', 'roadmap presentation', 'client presentation', 'business case', 'QBR', 'corporate deck', 'proposal'. Also triggers for any request to 'make slides' or 'build a deck' regardless of context. This skill governs CONTENT, STRUCTURE, and DESIGN decisions for both modes. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md.

davideast Bundle

Survey a whole Firebase application as a senior Firebase engineer, use Pyric's analyzers, sandbox, captured journeys, and verification engines as evidence, then produce a prioritized audit and self-contained implementation plans without changing application source. Use when the user asks to improve, audit, secure, optimize, or production-harden a Firebase app; find Firestore indexes; review Security Rules, auth boundaries, data models, queries, listeners, Firebase AI Logic, Pyric integration configuration, or supported Functions; explain denials; or wants a Firebase improvement roadmap rather than an immediate fix.

editor-code-assistant Bundle

Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.

farming-labs Bundle

Use the Farming Labs docs website through standards discovery, AGENTS.md, markdown routes, search, llms.txt, OpenAPI schema discovery, and MCP.

farming-labs Bundle

Use the @farming-labs/docs CLI to scaffold projects or Agent Skills, upgrade, downgrade, deploy, audit, review, export or compact agent docs, validate code blocks, generate discovery files, sync search indexes, and run MCP. Use for init, deploy, upgrade, downgrade, doctor, review, agent export, agent compact, skills scaffold, codeblocks validate, agents generate, sitemap generate, robots generate, search sync, mcp, and their flags.

foogunlana Skill

Create a single well-refined ticket from a rough idea or description, or rewrite an existing ticket's description. Use when the user wants to create a ticket, write a task, file a bug, add a story, turn a rough idea into a task, or reformat/rewrite an existing ticket. Triggers on "create ticket", "new ticket", "new task", "file a bug", "add a story", "create a task", "rewrite ticket", "reformat ticket", or any request to turn an idea into a single ticket. Also used by the backlog-grooming skill to create individual subtasks within an epic.

foogunlana Skill

Break down an epic into well-refined subtasks. Use when the user wants to groom a backlog, create subtasks from an epic, break down an epic into tickets, or refine tasks from user stories. Triggers on "groom", "backlog grooming", "break down epic", "create subtasks from epic", or any request to turn an epic's user stories into individual tickets.

foxminchan Bundle

**WORKFLOW SKILL** - Top-level router for Aspire 13.4 distributed apps. Detects the AppHost, enforces safety guardrails, and routes to the right sub-skill. USE FOR: Aspire AppHost detected, aspire CLI, distributed app, cloud-native .NET, aspire start, aspire stop, aspire resource, aspire deploy, aspire destroy, aspire publish, aspire init, aspire new, aspire add, aspire integration list/search, aspire wait, aspire describe, aspire ps, aspire dashboard run, aspire doctor, aspire update, aspire logs, aspire otel, --include-hidden, aspireify, WithBrowserLogs, custom dashboard/resource commands, .aspire/modules recovery, Playwright URL discovery. DO NOT USE FOR: non-Aspire .NET projects (use dotnet directly), Azure provisioning without Aspire (use azure-prepare), container-only repos with no AppHost, ordinary build/test tasks. INVOKES: aspire-init, aspireify, aspire-orchestration, aspire-deployment, aspire-monitoring. FOR SINGLE OPERATIONS: Route directly to the matching sub-skill.

lpalbou Bundle

Create, audit, update, and enforce ADRs as durable cross-task engineering policy. Use when Codex needs to write a new ADR, revise or deprecate an existing ADR, derive an ADR baseline for a project, check whether a code or design change conflicts with accepted decisions, or keep backlog, docs, and validation aligned with architecture and process rules. Do not use ADRs for ordinary task sequencing or one-off implementation details; keep those in backlog unless they establish a rule that should outlive the task.

lpalbou Bundle

Create, audit, normalize, and maintain backlog artifacts that track execution-planning work, implementation history, and follow-up triage. Use when Codex needs to set up a backlog system, write or revise backlog items, update backlog overviews or ledgers, move work between planned/proposed/completed/deprecated states, run backlog hygiene, preserve post-completion follow-ups, or join hub-coordinated work (work-item ids, pointer claims, evidence-bearing receipts). Do not use backlog alone to define durable cross-task policy; cite or escalate relevant ADRs instead.

iabstergo1 Skill

Work the Review-Queue and review_proposals items one by one (lint failure lists, cross-domain promotion candidates, overwrite-protection-rejected change proposals), giving analysis and fix suggestions; the final accept/reject is the user's. Use when the user says "work the review queue / look at the pending items / what's in the Review-Queue / walk me through the review backlog".

iabstergo1 Skill

Distill a recurring ingest/lint failure into a bounded improvement to one skill — read the skill-mine backlog → write a bounded SKILL.md edit on an isolated branch → run skill-gate (pytest + dual-tree parity + gate-integrity) → skill-stage the candidate, leaving skill-adopt to a human. Use when the user says "distill this failure into the skill / evolve a skill / let a skill self-improve / handle skill backlog item N". Only for improving this project's own skills; "summarize this / explain this / translate this / add this book to the KB (that is ingest)" must never trigger it.

iabstergo1 Skill

Post-publish retrospective on one ingested source — collect deterministic proxy metrics (ingest-stats), refresh the failure-signal backlog with increment context (snapshot the old backlog.yaml BEFORE skill-mine, then diff), read the digest routing deviations, and write one standardized report with recommendations only (skill-evolve triggers, gate/truth updates, proposals-resolve dry-run commands). Use when the user says "postmortem this ingest / 复盘这次入库 / how did this book's ingest go / ingest retrospective for <source>". Only for a source already published; "run a KB QA / audit coverage" is kb-qa, "semantic health check" is wiki-lint-semantic, and "distill this failure into the skill" is skill-evolve — none of those trigger this.

heathwang Skill

Use when creating or publishing a PRD from the current conversation context, especially after requirements, implementation decisions, or product scope have already been discussed.

chidekina Skill

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

chidekina Skill

Convert PRD or requirements into structured YAML spec with effects, constraints, and outputs. Pact-lang inspired. Triggers on: create spec, spec for, convert to spec, yaml spec, structured spec.

gendosu Skill

Use when adding a new task to the backlog — collects title, body, tags, priority, and parent task, then creates it with agkan.

gendosu Skill

Use when reviewing icebox tasks to decide whether to promote them to backlog or close them as no longer needed.

gendosu Skill

Use when reviewing backlog tasks to assess decomposition, implementation readiness, and priority ordering before development begins.

gendosu Skill

Use when reviewing a single icebox task to decide whether to promote it to backlog or close it.

gendosu Skill

Use when reviewing a single backlog task to assess decomposition, implementation readiness, and priority ordering.

commentary-dev Bundle

Operate source-backed Commentary Research Studies through MCP and Draft Review. Use for capability discovery, typed workflow proposals, study and session inspection, participant-event observation, step-scoped comments, evidence and result reads, findings proposals, and review handoff while preserving human control over launch, consent, access, destinations, acceptance, and publication.

cherryhq Skill

Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).

choegyumin Bundle

Use when reviewing a blueprint (PRD, spec, implementation plan, design/architecture doc, or product scope and technical decisions from the current session) right after it is written or before implementation, to check whether its implementation cost is economical and rational. Not for reviewing already-implemented code.

chusimin Bundle

完整项目规范（PRD）生成器——把一个产品想法转化成可直接喂给 Claude Code / Cursor 的 10 模块完整规范文档。自动检测并继承 BRD.md / MRD.md 的交接区数据，避免重复提问。当用户提到"帮我写个PRD"、"我想做一个XX"、"帮我梳理需求"、"我要vibe code一个产品"、"帮我写项目规范"、"coding spec"时立即触发。也适用于"帮我把这个想法变成可执行的文档"、"我想vibe code一个产品出来"、"帮我理一下做什么"等表达。即使用户只说"我想做个XX"或"帮我想想这个怎么做"，只要最终目的是产出一份可供 AI 编程 Agent 执行的 PRD，都应触发此 skill。与 ai-agent-prd-writer 的区分：ai-agent-prd-writer 是工作场景的正式 PRD（给开发团队看），本 skill 是给 AI 编程 Agent 看的项目规范（用户直接拿去 vibe coding）。

chusimin Bundle

AI Agent 产品 PRD 全流程撰写工具。当用户提到"帮我写PRD"、"写需求文档"、"梳理产品需求"、"PRD"、"产品需求文档"、"功能设计文档"、"帮我做产品设计"、"需求梳理"时立即触发。覆盖所有类型的 AI 产品 PRD（工具型、Agent型、对话型、平台型），支持从需求模糊到需求清晰的全场景。无论用户说"帮我理一下这个需求"还是"直接帮我输出PRD"，都应触发此 skill。即使用户只提到"功能设计"或"需求分析"，只要涉及 AI 产品，也应触发。

clairem0 Skill

Create a concise product requirements document or specification from conversation and repository evidence. Use when the user asks for a PRD, feature definition, product spec, or product-and-engineering plan before implementation breakdown.

clairem0 Skill

Turn a PRD, specification, active plan, or implementation proposal into an ordered set of independently provable tracer-bullet work units. Use when the user asks for implementation slices, autonomous and user-review boundaries, or a plan ready for execution.

cmj-hub Skill

Adaptive router for the pricing skill pack. Detects the operator's current state (brand-config present? SOUL.md present? current tiers documented? WTP discovery done? PSP defined? value-metric chosen? reference anchor set? pocket-price waterfall built? quarterly review scheduled?) and picks the next-best step. Loaded by the main pricing skill on bare invocation ("/pricing") or when the operator asks "where do I start" / "what's next" / "first time using this."

curie-eng Skill

Answer questions about production health and investigate incidents using live Kubernetes and observability data. Invoke whenever someone asks whether something is broken, slow, erroring, or down; asks what happened during an outage or time window; asks about alerts, logs, metrics, traces, or error rates; asks why a service is misbehaving; or asks for a status check on production. Also invoke for any question about the Kubernetes cluster and what is happening inside it -- pods, nodes, namespaces, deployments, statefulsets, daemonsets, jobs and cronjobs, restarts, CrashLoopBackOff, OOMKills, pending or unschedulable pods, evictions, rollouts, replica counts, resource requests and limits, CPU throttling, node pressure or readiness, and persistent volume capacity. Also invoke for catalog and discovery questions about the observability stack itself -- which metrics, log streams, dashboards, datasources, or alert rules exist, what a given metric or label is called, or where some signal lives.

teklabsdigital Skill

Use when starting an X2 project, when the problem domain has no approved epic story set, or when new scope needs stories added to an existing set. Runs problem discovery and produces epic-level stories, then requests gate 1 (stories approved). Do not use to author acceptance criteria or a requirements document, and do not use for anything downstream of gate 1.

timi-ty Bundle

A project-local development harness that compiles a ROADMAP.md into phased, validator-backed autonomous execution. Commands - create, invoke, update, state, sync, clear, inject-issues. Use when the user says 'create development harness', 'create dev harness', 'invoke harness', 'continue from harness', 'harness state', 'sync harness', 'update harness', 'clear harness', 'inject issues', or similar.

tjcages Bundle

Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile tracking, audit this project, fix a messy board, revive a parked project, or score readiness with the rubric. Runs discovery + confirmation before writes; never silent reorganize. NOT for first-time bootstrap (use linear-setup) or one-off CRUD.

aleksander-dytko Bundle

Structure product discovery with Teresa Torres' Opportunity Solution Tree - outcome, opportunities, solutions, experiments

apache Bundle

Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and embedded content (attachments, macros), risk indicators (PDF JavaScript actions, encryption), and content digests. Evidence gathering, not verdicts: Tika reports what the file asserts and what parsing observed; it does not attribute authorship or validate signatures. Use for triaging suspicious files, provenance questions, e-discovery-style review, or "is this file what it claims to be."