Product & Planning

sizovoleg Bundle

Workflow protocol для пары architect (Claude.ai) + Claude Code в DNA/RNA проектах. Используй ВСЕГДА при: формулировании команд и DevPrompt'ов для Claude Code, ревью workflow между сессиями, обнаружении систематических ошибок, планировании phase transitions. Триггеры: «напиши команду Claude Code», «напиши DevPrompt», «как дать задачу», «почему architect ошибается», «как валидировать решение», «верификация спеков», «verification protocol», «error budget», «assumptions section», «отчёт от Claude Code», «агент врёт что готово», «confidence markers», «raw artifact review», «когда прерывать», «как часто отчитываться», «тесты для скилла», «регрессия промпта». Кодифицирует защиты от структурных ошибок обеих сторон: architect-side (~10% error rate) и CC-side (самоотчёт о завершении, числовая слепота, дрейф контекста), плюс runtime observability и regression suite для самого скилла. НЕ для DNA creation (project-dna), PRD (prd-coauthoring), научной методологии (research-with-ai).

skillmedev Skill

Configures a Linear team end to end - team structure, minimal workflow states, cycles, a small label taxonomy, a daily triage rotation, and priority SLAs with breach views. Use when someone asks "set up Linear for my team", "how should we structure teams and labels in Linear", "our Linear backlog is a mess", or "how do we handle inbound bugs in Linear". Do NOT use for writing the tickets themselves - acceptance criteria, story points, Definition of Ready - use jira-ticket-writer instead (its ticket anatomy applies to Linear issues too). For deciding sprint scope and capacity, use sprint-planning.

syniox5334 Bundle

Manage Dash docsets and cheatsheets on macOS. Use when tasks involve Dash search and discovery, installing missing docsets, or generating guidance when a docset is unavailable.

vincentk1991 Bundle

Use this skill to teach an LLM how to discover, validate, and iteratively improve an ontology and SPARQL inference rules from unstructured text using a user-in-the-loop workflow and measurable quality gates.

vincentk1991 Bundle

Use this skill to iteratively discover, enrich, and validate an OWL ontology + Ontop OBDA semantic binding over virtualized SQL data (no materialization, no ETL). Uses ontop bootstrap as a starting point, then applies agentic SQL pattern discovery and 4-dimension richness metrics with a user-in-the-loop workflow.

jazz1x Bundle

Autonomous implementation engine (the "harnish" engine). PRD to task decomposition, ralph loop autonomous execution, cross-session context preservation, experience accumulation. Triggers: "impl", "harnish", "harnish 시작", "harnish 돌려", "harnish 이어서", "구현 시작", "start implementation", "태스크 분해", "decompose tasks", "루프 돌려", "run loop", "이어서 진행", "continue", "다음 태스크", "next task", "진행 상태", "progress status", "자산 현황", "asset status", "자산 압축", "compress assets", "이 패턴 기억해", "remember this pattern", "스킬로 만들어", "make it a skill", Request to resume work when harnish-current-work.json exists.

jazz1x Bundle

Planning-based implementation spec PRD generator. Converts planning requirements into an implementation-ready spec. Triggers: "drafti-feature", "drafti", "drafti 피쳐", "이 기획서로 PRD 만들어", "create PRD from this planning doc", "피쳐 PRD", "feature PRD", "기획서 기반 구현 명세", "implementation spec from planning doc", "피쳐 설계", "feature design", or when a planning document is attached/referenced. Distinction from drafti-architect: planning document exists → feature, does not exist → architect.

jazz1x Bundle

Technical design PRD generator. Creates an implementation-ready PRD from a technical problem definition alone, without a planning document. Triggers: "drafti-architect", "drafti", "drafti 설계", "설계해", "design this", "아키텍처 PRD", "architecture PRD", "이 문제 어떻게 해결할지", "how to solve this problem", "기술적으로 어떻게", "how to technically", "PRD 만들어", "create PRD" (when no planning doc is provided). Distinction from drafti-feature: no planning document → architect, has planning document → feature.

jneaimi Skill

PM-focused planning skill based on Bloom's AI Collaboration model. Use when the user says /plan, wants to plan a project, build a roadmap, scope an initiative, set milestones, or break work into phases. Also trigger on phrases like "plan the work", "build a roadmap", "scope this project", "milestones", "RACI", "who owns what", "phase this out", or "PM plan". Heavier than /prebuild, tighter than /think — focused specifically on product/project planning discipline.

kyleamathews Bundle

Find ambitious bakeries producing from raw components on-site, resist par-bake and discovery bias, and return an evidence-grounded shortlist for a requested location.

lanfuli Bundle

Apply @aleabitoreddit ("Serenity")'s distilled stock-analysis method to ANY ticker, sector, or situation — critical-chokepoint / supply-chain-OSINT idea discovery, first-principles value-chain decomposition, a Buffett-style quality gate (moat / profitability / customer-replacement risk, all default unverified), and narrative-vs-fundamentals hygiene. Produces a beginner-friendly Chinese analysis (她的观点 / 小白解释 / 第一性原理 / Buffett 直接判断 / 当前结论) that classifies an idea as 研究地图 vs 可投资结论. Trigger on "analyze like Serenity / 用 aleabito 的方法分析 / 用 Serenity 框架 / critical chokepoint 分析 / 第一性原理 + Buffett 判断这只股 / supply-chain bottleneck thesis". Never emits buy/sell calls.

criptogus Skill

Produce and edit Word documents in HermesOffice Docs — block editing, tracked changes, reports, and the templates/docs library (meeting notes, business plan, PRD, decision memo, and more). Load for any request that creates or restructures a document.

cynthiaschomp Bundle

Use this skill whenever a client requests work that may fall outside their contracted project scope. Triggers on: "scope creep", "out of scope", "client wants more", "they're asking for extra", "not in the contract", "new request on existing project", "change request", "additional work", "they added to the list", "this wasn't in the original scope", or any situation where a client email, message, or conversation includes a request that needs to be checked against project scope. ALWAYS use this skill before writing any scope analysis, PRD, change order, or ticket for scope-related work. This skill covers detection, documentation (PRD), ticketing, and the full approval workflow through to client quote.

devotts Bundle

The single front door for every Claude Code session close — and the ship stage of the *-it lifecycle (plan-it plans it, build-it builds it, review-it reviews it, conclude-it concludes it). A mechanical Step-0 triage detects ship-shaped sessions (deploys run, feature work merged, DoD met without prod verification) and runs the ship pipeline first: local test gate → merge+deploy → prod gate → archive plan docs → backlog → PM board. Then the session-close core every session gets: knowledge debrief with a supersession sweep (old docs get updated or deprecated, never left "current"), session-history ledger card, mid-flight + controlled-sessions verification, idle-subagent reaping, own-footprint sweep including secrets at rest, a local CONCLUDE_REPORT.html double-check report, and an honest safe-to-exit verdict. Fail-closed gates, no fake greens. First run in a repo: a five-question setup interview (docs home, second brain + scope, deploy skill, debrief skill) saved INSIDE the repo — once per repo, global only on e

longranger2 Skill

Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.

mathisarends Skill

Control Philips Hue lighting with the openhue CLI, especially room-first on/off control, absolute and relative brightness, scene discovery and activation, and read-only zone discovery. Use whenever the user asks to inspect or control Hue lights, rooms, zones, brightness, or scenes from the terminal.

gaznil Skill

When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.

get-convex Skill

Create a PRD

steph-frtech Skill

Use this skill to triage GitHub issues — surface stale issues, propose labels, identify blockers, list PRs awaiting review, and draft responses. Triggers on "issues", "backlog", "triage", "PRs to review", "stale".

aso-skill Bundle

Query ASO Skill for current Apple App Store search rankings, autocomplete suggestions, keyword difficulty and popularity, app metadata, credit balances, and credit-pack checkout discovery. Use for live App Store keyword or competitor research through ASO Skill. Do not use for Android data, download or revenue estimates, historical rankings, or predictions of future ranking performance.

agentpostmortem Bundle

Exercises extensionless script discovery

joseluisamado Bundle

Crystallize a project-design conversation into a complete project scaffold. Reads the current session for project name, principles, milestones, stack, and audience; writes the docs/ quintet (PROJECT, ARCHITECTURE, ROADMAP, PROGRESS, DEPLOY), CLAUDE.md, Makefile, CI workflow, pre-commit config, VERSION, LICENSE, CHANGELOG, and supporting files. Supports stack profiles for Python, Node, Go, Rust, polyglot, and Nix flakes; deploy models for docker-compose, single binaries, artifacts (OS images / appliances), and libraries. Use this when the user says "bootstrap this project", "scaffold the repo", "now write all of this down", or invokes /bootstrap-project. The skill is a finalizer — it assumes the design conversation has happened in this session and extracts spec from context. It will ask only the minimum follow-ups (license, optional add-ons, profile-specific questions, anything missing). Do NOT use this for: existing projects (the skill refuses to clobber files); greenfield brainstorming (have the design conve

joseluisamado Bundle

Crystallize an investigation-design conversation into a complete investigation/documentation project scaffold. For projects whose deliverable is *understanding and a record* — recoveries, reverse-engineering efforts, forensics, research write-ups, post-mortems — NOT software built from source. Reads the current session for project name, subject, principles, phases, and audience; writes the docs quintet (PROJECT, FOUNDATION, SUBJECT, WRITEUP, PRIVACY), the plan under docs/plan/ (PROCEDURE, ROADMAP), a dated append-only logbook/, an evidence/ directory, CLAUDE.md, LICENSE, CHANGELOG, and supporting files. Asks an artifact-provenance policy (private-archive / public-writeup / none) and offers optional add-ons: a go/no-go GATES decision-log, a docs/COMPONENTS.md flat inventory, and an evidence/netlist/ structure map. Use this when the user says "bootstrap this investigation", "scaffold this recovery/research project", "set up the documentation project", or invokes /bootstrap-investigation. The skill is a finalize

juscribe Skill

Non-negotiable behavioral guardrails for Juscribe work — every-ticket lifecycle, COMMIT-IMMEDIATELY rule, no lint/test suppression, stakeholder-verbatim ticket descriptions (agent additions kept current), no false deliveries, external blockers when waiting on user input, where a new ticket gets filed, splitting a ticket blocked on a third party, steps-as-subtasks, no `git push`, and the document-discoveries protocol. Auto-invoke before committing, before editing a ticket description, before transitioning to finished/delivered, before filing or placing a new ticket, when work turns out to depend on someone outside the team, and on hitting an unfamiliar error or workaround. In a Juscribe-wired project, generic ticket and board language means Juscribe — not another issue tracker.

juscribe Bundle

The single load-bearing Juscribe SOP skill — the full ticket lifecycle from pickup to delivery, plus estimation, ticket types, labels, metadata, testing gates, and the complete `jus` CLI / API reference in bundled files this skill points at. Use when working any ticket — picking one up, transitioning state, investigating, sizing, labeling, writing tests, running pre-commit gates, calling `jus api`, committing, self-reviewing, finishing, delivering, handling rejections, processing batches, or resolving dependency blockers. Auto-invoke whenever a ticket ID (`#N`) or "work on this ticket" / "pick up backlog" / "deliver" / "rejected" appears. In a project wired to Juscribe (a `.jus/` directory or the `jus` CLI), bare ticket language — `#123`, the board, the backlog, deliver — always means Juscribe tickets, so this skill is the one to invoke for them, never a skill for any other issue tracker.

k97 Bundle

Generate Apple platform app icons (iOS, iPadOS, macOS, visionOS) from one source image, with Apple's Human Interface Guidelines as the north star and first-class Tauri support. Validates the source first — square aspect, >=1024px, alpha, sRGB/P3, 8-bit — then generates AppIcon.appiconset (with dark/tinted variants), .icns via iconutil with Apple's rounded-rect margins for legacy macOS, visionOS layered image stacks, and Tauri's full icon set including the dock-icon margin fix. Dependency-free on macOS (sips, iconutil, Swift/CoreGraphics). Use for "generate app icons", "app icon from this image", "make an .icns", "AppIcon.appiconset", "tauri icon", "dock icon looks too big/square", "App Store icon". Roadmap: Flutter, React Native, Ionic.

kornia Skill

Use when interacting with a Bubbaloop deployment via its MCP server — guides the discovery → control → automation workflow and prevents the most common mistakes (MCP polling for streaming data, missing Bearer token, ignoring RBAC tier).

dsebastien Bundle

Monitor arXiv for new papers matching saved queries/categories. Manages a watchlist with deterministic "seen" tracking so subsequent checks return only new material. Use when the user says "watch arxiv", "track arxiv", "new papers on", "arxiv monitor", "check my arxiv watches", or wants periodic discovery. Depends on arxiv-search (must be installed as a sibling skill).

ehmo Bundle

Use when an agent needs Google API discovery, gum CLI calls, OAuth setup, or catalog-backed workflows.

entr0pia Bundle

Use this skill to manage Windows packages via Scoop. Trigger this skill whenever the user mentions installing software, or whenever you need to execute a CLI tool that is not pre-installed on Windows but might have a Windows version available for discovery or installation via Scoop (e.g., git, curl, neovim, bat, etc.). This skill also helps you discover and execute the "shims" (executables) installed by Scoop, ensuring you know which command-line tools are available for use.

ertlgit Bundle

Work with existing decision records. Use this skill to check a PRD, OKR, proposal, or email for conflicts with prior decisions, search decision records by topic or owner, or surface decisions due for review. Invocation patterns: 'check decisions:', 'search decisions:', 'review decisions'.

ertlgit Bundle

Use this skill whenever the user hands the agent a document (brief, spec, PRD, RFP, requirements, case study, board ask, strategy doc) and asks the agent to act on it. Translates what each part actually asks (its intent, not its literal wording), names the traps a shallow reading hits, and stops for the user to confirm understanding before work begins. For depth-critical or intent-heavy documents, not quick lookups or summaries. Invocation: 'comprehend first:', 'comprehend this brief:'.

saltbo Bundle

Integrate and assess an existing protected API as a Realmroot Resource Server. Use when determining required, conditional, and recommended integration capabilities; implementing or validating RFC 9728 and OpenAPI discovery; selecting native, external, or brokered authorization; enforcing Realmroot token, audience, scope, actor, or DPoP requirements; registering the Resource Server; or proving end-to-end Agent access. This Skill does not design the business API or its resource model.

schemavaults Skill

Discover available email templates from the SchemaVaults mail-server `GET /api/templates` endpoint, via either the `listEmailTemplates()` helper or the `schemavaults-send-email list-templates` CLI from `@schemavaults/send-email`. Use before sending a template-based email to find the correct `template_id` and understand the expected `template_props` shape. For one-off shell discovery, prefer the CLI (`bunx schemavaults-send-email list-templates`).

shanmukhaditya Bundle

Operate a hierarchical product leadership team of up to ten agents to understand a product end to end, research its current market and users, and produce an evidence-backed, implementation-ready portfolio of new product requirements and bug fixes. Use for holistic product audits, product strategy, roadmap creation, opportunity discovery, competitive analysis, PRDs, backlog generation, product-quality reviews, or requests to make an existing product materially better; default to a 70:30 feature-to-bug investment mix and scale the roster down only for tightly bounded work.

shipshapedata Skill

Audit any website's agent readiness. Use when a user asks how AI-agent-friendly their site or product is, whether agents can find and use it, how to add llms.txt or markdown twins or an MCP server, or how to improve an agent-readiness score. Probes the standard discovery surface with plain HTTP requests and reports concrete gaps with fixes.