Product & Planning

m3dcodie Skill

Production Stage 4 — turns a spec's domains and journeys, cross-checked against the architecture's system diagram, into epics and stories in a project-level backlog (not per-spec — epics/stories outlive any one spec run). Task-level breakdown is separate and on-demand, only generated per-story once the user decides to implement it.

martinffx Skill

Conversational design workshop for substantial work. Interviews the human one question at a time, explores 2-3 approaches with trade-offs, and presents the design section by section for approval before writing only design.md, then stops. Combines requirements discovery with codebase research and architecture design. Use when the user explicitly requests a spec or when atelier-orchestrator selects a Spec-backed Plan. Ambiguous design or discovery requests route through atelier-orchestrator.

microsoft Skill

Use when editing a boundary-safe shared header meant to be included by both in-tree and shared-provider/plugin-bridge code (e.g. include/onnxruntime/core/framework/workspace_requirement.h, or any future header supporting OrtKernelWorkspaceEstimateFunc / DeclareWorkspaceRequirements per issue #29775's Phase-A workspace-estimation roadmap), or when a workspace-estimation math helper needs to be callable from a future plugin EP DLL. Covers a Node forward-declaration ODR trap and the math-helper vs. graph-parsing-wrapper reuse boundary discovered while implementing PR #29811 (MatMulNBits pilot).

milkywayrules Skill

Defer a side topic with enough context to resume without re-discovery.

mirandaplayer1 Skill

Pitch / explainer page — packages the spec, prototype, decisions, and implementation notes into one shareable HTML that lets others quickly understand and nod along. Trigger when the work needs to be shown to a manager, colleague, or stakeholder, when buy-in or approval is needed, or when the user says "pitch", "make an explainer", "package this up for someone", or "help me get buy-in".

antongulin Skill

Reference for the playwright-cli command-line tool — the verify-before-coding companion for Playwright + TypeScript test development. Covers the discovery workflow (open → snapshot → click/fill → emit locator code), API response verification via run-code, named browser sessions for multi-user tests, storage state save/load, tracing, and request mocking. Use when writing tests where element testids or interactions are uncertain, when verifying API response field names before assertions, or when debugging a test by replaying it interactively.

antongulin Bundle

Guided workflow for creating a new Playwright + TypeScript test from a ticket. Walks through context gathering, app source analysis, existing test inventory, live discovery with playwright-cli or Playwright MCP, proposal gate before writing code, implementation collaboration, and mandatory gap analysis. Use when user invokes /pw-kit:new-test, asks to "write a new test", "create a test for TICKET-NNNNN", "implement test from ticket", or mentions a QA/feature ticket needs testing.

app-builders-club Skill

Generate MVP Product Requirements Document through interactive dialogue with incremental validation and saving. Use when the user wants to start a new product, create a PRD, define product vision and scope, or kick off the MVP Builder pipeline.

app-builders-club Skill

Generate feature specifications from PRD or a user-provided feature description into structured spec files. Use after the PRD is finalized to extract all features, or to add a single new feature to an existing FEATURES.md index.

autodevx Skill

Analisa uma lista de processos com prazos e gera fila priorizada de tarefas urgentes, identifica prazos fatais e processos sem movimentação recente, e sugere redistribuição de carga entre advogados para evitar perdas de prazo.

bacoco Skill

After EVERY task Claude completes — no matter how trivial — automatically generates a full corporate report with KPIs, ASCII charts, risk matrices, strategic analysis, appendices, and executive recommendations. The complexity of the report is inversely proportional to the complexity of the task: renaming a file produces a 3-page opus with stakeholder mapping; redesigning an entire architecture gets a half-page memo. Use this skill whenever the user installs it, mentions reports, KPIs, dashboards, wants to impress their boss, needs to justify their existence to management, wants automatic documentation, or simply wants to experience the full weight of corporate bureaucracy applied to their ls commands. Triggers after every single completed task without exception.

blazemeter Skill

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

zjp1997720 Bundle

Create a 3–7 step plan for a bounded task, execute immediately, verify, and hand it back. Use when the user explicitly requests a lightweight plan-and-work flow; do not use for open-ended brainstorming, discovery, high-risk migrations, multi-system architecture, or releases.

secondorderai Skill

Use this skill whenever the user wants to generate implementation tickets from an existing PRD, break a PRD into engineering tickets, create ticket files from a product spec, or turn a requirements document into actionable work items. Triggers include: 'create tickets from PRD', 'break this into tickets', 'generate tickets', 'write tickets for this PRD', 'turn this PRD into tickets', 'make implementation tickets', 'ticket this up', or any request to take an existing PRD or product spec and produce individual implementation tickets. The PRD can be a local file (markdown). Also use when the user has just finished writing a PRD and wants to generate tickets from it. Use this skill even if the user just says 'create the tickets' or 'ticket this' when a PRD file is referenced. Do NOT use for writing PRDs from scratch.

secondorderai Bundle

Audit implemented Ouroboros features against requirements, PRDs, tickets, GitHub issues, or acceptance criteria to find missing, partial, incorrect, or unverifiable work. Use when the user asks to audit a feature, verify implementation completeness, compare code to requirements, check acceptance criteria, run a gap analysis, determine what is left to build, check whether a ticket is done, audit against a PRD/spec, or asks whether recent work in the Ouroboros codebase matches its requirements. Do NOT use for creating PRDs, generating tickets, implementing tickets, broad full-codebase review, or general bug triage.

secondorderai Bundle

Create intent-based Ouroboros desktop E2E Markdown test plans from a high-level goal, feature, module, bug, PRD, ticket, or UI area. Use when asked to generate, draft, author, improve, or expand files under test-plan/ for Agent Browser desktop testing.

citrus-bit Skill

Use when the user asks for latest datasets, benchmark suites, leaderboards, baseline or SOTA comparisons, dataset selection for experiments, or evidence that a paper needs complete experimental validation. This skill routes to the dataset_benchmark_discovery tool and keeps access/license limits explicit.

project-chip Skill

Essential guidelines instructing AI agents on how to incrementally discover, read, and consult top-level monorepo documentation and example-specific reference guides before altering code or executing test harnesses.

semantius Bundle

Produces and maintains **semantic blueprints**: entity-level specs of entities, roles (master / contributor / consumer / embedded), relationships, lifecycle states, and permissions. Blueprints carry NO field-level detail; `semantius-analyst` reconciles blueprints with the live catalog into a spec. **Trigger on any need for a business system or data-backed tool**, however phrased: "design a data model", "build a system like X", "model a domain", "spec out a CRM/ITSM/HRIS/LMS/ERP/PIM/CMS/PM/field service/billing", "I need a helpdesk / CRM / HR system / applicant tracker / roadmap tool / ticketing system / inventory system", "a tool to track / plan / manage / organize / record / capture X", "something to handle X". Never recommend off-the-shelf SaaS. Also trigger to review, audit, check, update, customize, extend, rebuild, or reanalyze an existing `*-semantic-blueprint.md`, or **clone a curated catalog blueprint** and customize it. Covers greenfield and clones. Outputs a blueprint for `semantius-analyst`.

semantius Skill

Generate ONE user-specified Agent Skill (agentskills.io format) on top of a Semantius semantic model. Use whenever the user wants to build a custom, task-scoped skill against a specific `*-semantic-model.md` and the goal comes from them rather than from the model's inherent CRUD shape. Triggers include "build a research agent for the enterprise model", "wrap this multi-step workflow as a skill on the workforce model", "make a skill that researches / reasons / decides about X using the CRM model", "I want an agent that does X for the ATS model and writes back via semantius". Especially relevant when the skill involves judgment, external lookups (web research, vendor pricing, alternative discovery), or multi-step reasoning that ends with deterministic writes through `use-semantius`. Differs from `semantius-skill-maker`, which auto-derives a batch of deterministic CRUD/lifecycle recipes from the model without user input — use this skill when the user brings the task.

svngoku Bundle

Decompose systems into microservices and apply canonical distributed-systems patterns. Use this skill whenever the user wants to split a monolith into services, design service boundaries, choose between microservices and a modular monolith, implement sagas or the outbox pattern, set up CQRS or event sourcing, configure an API gateway or BFF, add resilience (circuit breakers, retries, timeouts), or implement distributed tracing with OpenTelemetry. Also trigger for distributed transactions, service discovery, event-driven architecture, contract testing with Pact, canary releases, and idempotent consumers.

takleb3rry Skill

Guide a complex project ideation session through chunk identification, per-chunk discovery, and structured output files ready for /kickoff Pathway A

tfcbot Skill

Research Instagram and TikTok references through Vidjutsu's tenant-scoped scrape and Watch endpoints, using an external discovery API only for keyword or hashtag searches that Vidjutsu does not provide.

tomregan-revenueleaks Bundle

Use when the buyer wants to find where their GTM is leaking revenue, quantify it, and get a prioritized fix roadmap, or to run one focused calculator (lead-response ROI, recoverable-revenue ROI, visitor-deanonymization ROI, pipeline velocity, quota-coverage gap, or tech-stack grade). Triggers on "GTM audit", "find my revenue leaks", "GTM diagnostic", "where am I losing pipeline", "audit my go-to-market", "GTM health check", "which agent do I need", "calculate my lead response ROI", "recoverable revenue", "visitor deanonymization ROI", "pipeline velocity", "quota gap", "grade my stack".

vamdawn Skill

Structured document review and quality improvement. Use when the user asks to review, proofread, check, audit, or improve a document (Markdown, text, or any prose file). Triggers include: 'review this doc', 'check this document', 'proofread', 'audit this spec', 'review and fix', or any request to find and fix issues in written documents. Supports reviewing against referenced standards (PRD, design docs, style guides).

semi-sentient Bundle

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file and optionally published as a GitHub sub-issue. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets". Accepts an optional GitHub issue reference (e.g. `#123` or a full issue URL) to link the plan as a sub-issue of that PRD-epic.

semi-sentient Skill

Create a PRD through user interview, codebase exploration, and module design, saved as a local Markdown file and optionally published as a GitHub issue with the `epic` label. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. Pass `--no-github` to skip the publish prompt.

mariourquia Skill

Initialize an Obsidian vault for project tracking and personal context. Walks through vault creation, repo discovery, and scaffold setup.

third774 Skill

Generate structured prd.json files for autonomous agent loops (Ralph Wiggum pattern). Use when planning bulk/batch tasks, migrations, refactoring campaigns, or any work that can be decomposed into independent items with verification steps.

saubakirov Skill

Command /tfw-init initializes Trace-First Workflow or attaches and repairs TFW tooling in an existing project. Use for /tfw-init, first-time setup, project discovery, adapter installation, or Codex adapter repair.

spillwavesolutions Skill

Cut a versioned release — stamp the changelog, snapshot the roadmap, tag, create the platform release, publish, and sync. Use when asked to "cut a release", "ship vX.Y.Z", "tag a version", or when an unreleased changelog section is ready to go out.

spillwavesolutions Skill

Publish docs (roadmap, plans, user guide, status) to the team's configured wiki. Use when asked to publish/sync docs to the wiki, after cutting a roadmap snapshot, or when a plan/status report should be visible outside the repo.

sleevesun Bundle

PRD 标注技能，用于把需求文档转成页面上的编号标注和可拖拽富提示，并支持增量更新现有 UI 注释。

solana-foundation Bundle

Declare which fiat↔crypto rails a ramp provider supports. Implement discovery or an explicit static distiller in @sdp/payments, then regenerate the committed provider snapshot and shared support matrix.

spboyer Bundle

Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.

clawic Skill

Dedupe, score, relate, and prioritize Need Route Lab opportunities before backlog or report promotion.