Product & Planning

bm629 Bundle

Use when authoring a user-flows document — the map of the paths a user takes through a product to accomplish each goal: entry points + the navigation/IA frame, the happy path, decision branches, error/recovery + edge states (incl. loading + success), interaction resilience (undo/resume/system-status), flow-level accessibility, and the screens/states traversed, each flow traced to a goal/persona job. Guides the METHOD, not the outline: deriving flows from upstream goals + prior-art patterns (never inventing them), enumerating every branch + error path so no path dead-ends, judging flow quality with objective heuristics, rendering each flow as a synced diagram + numbered narrative, and amending an existing doc as a scoped versioned delta. Composes with a separate user-flows template tool and a research capability. Assumes an approved PRD as upstream input — never a blank page. Not for reviewing a finished user-flows doc, not for screen layout/wireframes, and not for authoring the PRD itself.

bm629 Bundle

Use when reviewing/judging a finished user-flows document to decide whether a downstream wireframing pass can enumerate every screen and whether each path is complete, walkable, resilient, accessible, and sound — an acceptance gate, not authoring. A user-flows doc is the navigation/interaction graph: entries + IA frame, happy path, branches, error/recovery + edge states, resilience, flow-level accessibility, screens traversed. Judges it against a single-sourced bar: goals map to flows (no orphans), entries+exits defined, branches resolve, no dead ends, states (incl. loading+success) covered, irreversible actions guarded, every path keyboard/ AT-completable, the flow objectively sound, notations synced, screens enumerable; plus a delta-scoped review when amending. Emits exactly `VERDICT: approve|revise` with actionable findings. Approves a doc meeting the bar (no false-revise on a thin one), revises only on a named gap. Not for authoring, not for wireframes, not for the PRD.

bm629 Bundle

Use when running a systematic open-source prior art survey for a software idea — deriving a keyword map (typed search vocabulary) or executing one search angle of repository discovery across code hosts, package registries, curated catalogs, code search, alternative directories, and community channels. Produces schema-validated artifacts: a keyword-map file or a per-angle search-output file with reproducible coverage records and candidate repositories — or deep-reading one candidate into an EXTRACTION (a 10-section analysis + a machine-readable verdict/score/license/deps block). Keywords: prior art, open source search, repository discovery, keyword map, code extraction, competitor alternatives. Covers the survey's SEARCH wave (keyword-map derivation + angle execution), the EXTRACT wave, and the SYNTHESIS wave (aggregating extractions into a report + a borrow-index).

bm629 Bundle

Use when authoring a feature specification (functional spec) — elaborating the features a PRD names into implementable, testable detail. Guides the METHOD, not the outline: tracing each feature to a PRD goal; specifying observable behavior (use-case flows, EARS); enumerating I/O, a state-transition table, and decision tables for combinatorial rules; covering edge cases + errors with their handling; writing testable Given/When/Then (or metric-threshold, for probabilistic/ML) acceptance criteria; applying a per-feature non-functional-requirement taxonomy keyed to the feature archetype (UI/API/data-ML/batch/integration/CLI); and amending an approved spec as a versioned, ripple-analyzed delta — to a bar an engineer can build and a tester can verify each feature from. Composes with a feature-spec template tool + a deep-research capability. Assumes the approved PRD as upstream input — never a blank page. Not for authoring the PRD, reviewing a finished feature spec, or engineering design docs (ADR/RFC).

bm629 Bundle

Use when reviewing/judging a finished feature specification to decide if engineering can plan and build from it — an acceptance gate, not authoring. Below the PRD. Judges it against a single-sourced 10-condition implementability + testability bar: each feature traces to a PRD need (no orphans/gaps); behavior unambiguous + observable; I/O + states complete (a state-transition table where stateful); each edge case names its handling; acceptance criteria testable (Given/When/Then, or a metric-threshold for a probabilistic/ML feature); singular + consistent; load-bearing non-functional requirements carry numeric targets; an amend reviewed delta-scoped; open questions surfaced. EARS, decision tables, and archetype overlays are authoring aids judged by outcome, never demanded. Emits exactly `VERDICT: approve|revise` plus findings — approves a spec meeting the bar (no false-revise on a thin one), revises only on a real, named gap. Not for authoring, the upstream PRD, design docs (ADR/RFC), or other types.

bm629 Skill

Use when anyone (user or agent) is about to author any structured content — RFC, ADR, runbook, spec, plan, PRD, README, retrospective, blog post, PR description, issue body, ticket, multi-paragraph commit message, announcement, or any other shape — regardless of destination (local file, GitHub, Jira, Linear, Slack, email, Confluence, Notion, Google Drive, etc.). This skill is the gate every content-authoring action passes through. It (1) identifies content-type + variant from intent via research, (2) checks docs/templates/<content-type>/<variant>/ for an existing template, (3) if it exists, returns it plus a hard-refusal directive that you MUST follow, (4) if missing, forges a new one via research, then returns it under the same directive, (5) on "advise:" intent, helps place content that doesn't fit (maps to sections or proposes new variant). Modes: use-or-create (default), force-regenerate, force-new-variant. Self-contained: prefers a research-capable skill if available, else built-in WebSearch + WebFetch.

bm629 Bundle

Use when authoring or amending developer-tool documentation — the adoption + integration narrative for an SDK, library, CLI, framework, or API platform: the guide a developer reads to install, integrate, and operate the tool. Guides the METHOD, not the outline: developer GOALS not endpoints; a signposted start-here + a fast verifiable first success; concepts before recipes; goal-named runnable recipes; an end-to-end tutorial; grounded best-practices; a troubleshooting path; archetype-aware emphasis (API/SDK/CLI/framework); POINTERS into — never a copy of — the api-reference; and amending a guide as a versioned delta that sweeps the tool's changes for stale samples. Full Diataxis correctly typed, every sample runnable + accurate to the tool, nothing fabricated. Composes with a template tool + deep-research. Consumes the handed-in feature-spec + api-reference + PRD — never a blank page. Not the api-reference catalog, the end-user user-guide, engineering docs, or reviewing one.

bm629 Bundle

Use when authoring a software/system architecture document — the whole-system structure: context and scope, the major components/services and their responsibilities, the interaction topology and integration boundaries, the significant technology choices and their rationale, and how the system realizes its non-functional/quality targets. Guides the producer through the METHOD, not the outline: scoping the boundary first, naming a responsibility per component, justifying each significant tech choice, giving every NFR target a realization, and recording each key decision as a STANDALONE, LINKED ADR file (the doc carries only a decisions index). Composes with a separate architecture-doc template tool AND an ADR template tool (section structure), plus a deep-research capability. Assumes the approved PRD + product direction as input — never a blank page. Not for reviewing a finished architecture doc, not for one feature's implementation design (a technical-design doc), and not for the API contract or data schema.

bm629 Bundle

Use when authoring (or amending) a technical-design document (a TDD / engineering design doc / design RFC) for one feature or component — the detailed implementation design for building it within an existing system. Guides the METHOD, not the outline: grounding the design in established practice and the project's real constraints, tracing every decision bidirectionally to a requirement, comparing at least one real (non-strawman) alternative with a stated decision criterion, referencing the architecture-doc / API spec / data-model rather than duplicating them, naming the failure modes, the observability signals, the testing, and the rollout — and amending an approved design as a versioned, ripple-analyzed delta — to a bar where an engineer can implement without re-deriving the design. Assumes the approved PRD + feature-spec as upstream input, never a blank page. Not for system-wide architecture, not for the API contract or data schema, and not for reviewing a finished TDD.

bm629 Bundle

Use when deciding which documents a software or product project needs to produce — classifies across 10 dimensions, identifies product capability areas (4-signal algorithm), and produces a proportional, capability-scoped manifest with all five sections populated (documents, roles, skills, tools, capabilities). Re-tailors when the project changes (amend). Covers the full SDLC universe (seven lifecycle bands + four domain overlays). Returns a three-key JSON payload; caller writes two files from it (capability-map.yaml + manifest.yaml) — never assumes scope_root. Discovery only: decides which documents and what it takes to produce them, not how to author them. Keywords: document discovery, documentation plan, SDLC documents, document manifest, capability map, proportional docs, manifest completeness.

bm629 Bundle

Use when reviewing/judging a finished whole-system architecture document (+ its linked ADR files) to decide if an engineer can grasp the system and place a feature's TDD within it — an acceptance gate, not authoring. Judges a single-sourced 10-condition bar: boundary + external deps + concerns; components single-responsibility at whole-system altitude (not api-spec/data-model or feature-TDD detail); diagrams ⇄ narrative agree; every significant decision a standalone LINKED, immutable ADR (one per file, index in sync, supersede not edit); decisions traced + justified; NFR targets realized + tradeoffs named; cross-cutting (resilience/security/privacy/observability) addressed; ASRs covered; nothing fabricated, claims consistent with the code; amend delta-scoped. C4/arc42/ATAM/4+1 are aids judged by outcome. Emits exactly `VERDICT: approve|revise` (no false-revise on a thin doc). Not for authoring, the PRD, api-spec/data-model, a feature's TDD, or generic design docs/RFCs/standalone-ADRs (use design-review).

bm629 Bundle

Use when reviewing/judging a finished technical-design document (a TDD / engineering design doc / design RFC) for one feature, deciding whether an engineer can implement it without re-deriving the design. An acceptance gate, not authoring. Judges a single-sourced 11-condition implementability bar: every decision traces bidirectionally to a requirement; scoped to one feature; approach and decomposition implementable, diagram synced to narration; interfaces an api-spec or data-model owns are referenced, not duplicated; one real alternative with a decision criterion; failure modes carry handling; observability signals named; testing covers failures and contract conformance; rollout and rollback with measurable triggers; nothing fabricated; an amend reviewed delta-scoped. Emits exactly `VERDICT: approve|revise` plus findings, and does not false-revise a thin-but-complete TDD. Not for authoring, the upstream PRD or feature-spec, the api-spec or data-model, or generic design docs and RFCs.

bm629 Bundle

Use when judging a produced document PLAN — a manifest of which documents a project will produce, each with producer/tools/skills/depends_on — to decide if it is sound enough to produce from. An acceptance gate, not authoring. Judges a fourteen-condition bar single-sourced with project-document-discovery's Self-check (v6.0.0): proportional; load-bearing present; production reqs + depends_on per doc; acyclic graph; no orphan (leaf deliverables like LICENSE/README exempt); no padding; open-ended preserved; change-scoped amend delta; skills carry purpose/requirements; capability_map + product_capabilities keys valid; manifest nested with fan-out entries matching flags; all five manifest meta-sections populated (capabilities/roles/skills/tools not empty, no build-level capabilities); capability scalar on every document entry (not array). Emits exactly one terminal VERDICT: approve|revise. Review-only — not a document's internal quality, not the coherence of finished documents (reviewing-document-set).

zju-real Bundle

需求分析、PRD编写、产品需求文档、详细设计、BRD、MRD、PRD模板、用户故事、用户访谈、需求挖掘、痛点分析、功能设计、KANO模型、Y模型、5W1H、优先级排序、需求池管理、写过需求、写PRD、做需求分析、产品设计、产品策略、SWOT分析、波特五力、PESTLE、安索夫矩阵、商业模式画布、价值主张、产品愿景、OKR制定、Sprint规划、回顾会、发布说明、干系人管理、竞品分析、市场调研、用户研究、机会解决方案树、指标看板、测试场景、头脑风暴、假设验证

hassan-mohiddin Bundle

Use when writing or revising a spec, PRD, issue, API contract, technical design, migration contract, decision artifact, or similar durable document.

nledford Bundle

PHP engineering guidance for PHP source, Composer manifests and lockfiles, runtime and extension discovery, PHP 8.4 implementation or migration, PHPUnit/Pest configuration, PHPStan/Psalm, PHP-CS-Fixer/PHP_CodeSniffer, PHP templates, packaging, and project quality commands. Use for ordinary PHP implementation and project mechanics; use php-design-patterns for pattern choice, php-antipatterns for smell-focused review, and php-testing-quality for test-lane work.

nledford Bundle

Use the Hound MCP server for public web research, source discovery, URL or PDF retrieval, bounded same-domain crawling, OCR, and evidence capture with smart_search, smart_fetch, smart_crawl, screenshot, cache_clear, or version. Use when current external evidence is needed. Do not use for repository-local facts, structured GitHub platform objects, signed-in browser interaction, checked-in Playwright tests, private or sensitive resources, or Hound installation and upgrades unless explicitly requested.

nledford Bundle

MCP server engineering guidance. Use when creating, updating, refactoring, testing, or reviewing Model Context Protocol servers, tools, resources, prompts, capability discovery, stdio transport, Streamable HTTP, or legacy HTTP+SSE compatibility. Do not use merely to operate an existing MCP server; use the applicable provider or service skill instead.

fatih-developer Bundle

Perform read-only GEO, AEO, technical SEO, AI-search visibility, citation-readiness, AI-question mapping, and repeatable visibility-measurement audits of public websites without source-code or repository access. Use when the user provides a domain or public URL and wants analysis, benchmarking, AI mention/citation measurement, recommendations, or a developer/content/operations action plan for ChatGPT Search, generative answer engines, Google, Bing, Perplexity, or similar discovery systems. Also use for public competitor or third-party site audits. Do not use when the user asks to edit code, change a repository, deploy fixes, access private pages, or implement the recommendations; use an implementation skill instead.

fatih-developer Bundle

Analyze, implement, and verify technical SEO, GEO, AEO, AI-search visibility, citation-readiness, AI-question coverage, and repeatable visibility measurement for web projects. Use when creating a new website or web application; when the user asks to improve or measure visibility in ChatGPT Search, generative/AI answer engines, Google, Bing, SEO, GEO, or AEO; or when a code or content change may materially affect crawling, indexing, metadata, structured data, answer extraction, internal linking, analytics, or search-visible content. Do not invoke for unrelated changes that cannot affect public discovery or search presentation.

vanducng Bundle

Manage Jira issues via CLI and REST. View, create, update, transition, assign, comment, and run sprint ops, including evidence follow-ups, native mentions, inline images, structured ADF comments, and board-column moves. Use when user mentions issue keys (PROJ-123), tickets, follow-ups, sprints, or keywords like jira/ticket/backlog.

vanducng Bundle

Generate comprehensive edge cases and test scenarios by decomposing a feature or file across 12 risk dimensions, or blast-radius review a change with --diff: what breaks beyond the diff, proven by running real code. Use for pre-implementation risk discovery, QA planning, regression design, exhaustive edge-case enumeration, and change-safety review. Triggers: 'edge cases for X', 'what could break', 'blast radius', 'what could this break beyond the diff', 'test scenarios', 'QA plan', 'risk discovery', 'enumerate failure modes'.

vanducng Bundle

Threat-modeled security audit using STRIDE + OWASP (incl. the OWASP LLM Top-10 lens for AI/agent code), scanning code from multiple attacker perspectives, with optional red-team discovery loop and an autoresearch-style fix loop. Use for defensive security review, vulnerability discovery, threat modeling, prompt-injection / LLM security, and authorized remediation. Triggers: 'security audit', 'STRIDE', 'OWASP', 'find vulnerabilities', 'threat model', 'red-team this', 'is this secure', 'prompt injection', 'LLM security'.

vanducng Bundle

Operate the `smartsheet` CLI for bounded sheet discovery and reads, explicitly authorized bulk row additions or updates, structured JSON automation, and verified write workflows. Use when the user says "smartsheet", asks to list sheets, read or add/update rows, or script Smartsheet through its JSON contract.

peiiii Bundle

仅当用户明确要求 AI 从产品方向、愿景、真实现状或用户信号中主动发现值得解决的问题、形成候选需求，或降低对详细需求输入的依赖时使用；负责形成有证据、可验证的需求假设，不负责实现、排期或自动纳入路线图。

peiiii Bundle

Curate NextClaw skill resources, including OpenClaw and community sources. Use when expanding NextClaw skills, planning reuse/adaptation, or building a skill roadmap.

tommylower Bundle

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

island-dev-crew Bundle

Routes each work item by Brooks's 1986 split - accidental complexity, the difficulty our tools impose, goes to agents at full speed, while essential complexity, the difficulty of the thing itself, gets a recorded human decision before any agent touches it. Reach for it when handing a backlog to agents, when an agent has just decided something nobody chose, or on "can the agent take this one", "essential vs accidental complexity", "what has to stay human", "no silver bullet". Differentiator - this island owns the classification and the routing only, so whether the thing should exist at all, who owns the design, and what a human reads afterwards are three neighbouring seats, each named below.

l3-igrant Skill

How to find a credential schema or a DCQL query for the iGrant.io Organisation Wallet Suite. Start with the iGrant.io verifiable data registry (claim path pointer schemas and DCQL query templates). If the credential type you need is not there, check the WE BUILD attestation rulebooks catalog for a rulebook that defines it, and build the claim path pointer document from the rulebook. Use this skill when no igrantio-credential-schema-* or igrantio-dcql-query-* skill matches the credential you must issue or verify.

zju-real Bundle

8年品牌营销总监决策大脑——整合20+经典分析模型，提供「诊断→策略→执行→复盘」全链路工作流。 **触发场景**： - 市场分析、竞争分析、环境分析 → 调用战略分析模型（五力/SWOT/PESTEL/BCG/安索夫/3C/蓝海） - 问题拆解、决策分析、方案设计 → 调用思维方法模型（MECE/金字塔/SCQA/六帽/5W2H/决策树/脑暴/因果图） - 品牌定位、品牌战略、价值主张 → 调用品牌定位模型（定位三角/Kapferer/Aaker/价值主张/PMM/护城河/原型） - 营销策略、传播策略、市场进入 → 调用营销传播模型（4P/STP/AIDA/PAS/GTM/ICP/SOSTAC/IMC） - 用户增长、增长黑客、裂变策略 → 调用用户增长模型（AARRR/AIPL/AISAS/AIPS/北极星/飞轮/Hook/裂变/漏斗） - 用户洞察、行为设计、体验优化 → 调用消费者心理模型（BJ Fogg/COM-B/EAST/Nudge/KANO/CJM） - 数据分析、效果评估、指标体系 → 调用数据分析模型（RFM/HEART/NPS/LTV-CAC/A/B测试/GA4） - 运营执行、项目管理、团队协作 → 调用运营执行模型（PDCA/OKR/RACI/敏捷营销/SOP） - 销售流程、定价策略、客户管理 → 调用销售变现模型（销售漏斗/MEDDIC/定价/客户成功/变现模式） **关键词**：品牌营销、市场分析、营销策略、增长黑客、用户增长、品牌定位、销售策略、定价策略、营销总监

kastalien-research Bundle

Start a Unified Loop Controller session via Ralph Wiggum. Autonomously works through backlog, dispatches agents, and explores via QD when idle.

martin65536 Bundle

帮助用户梳理求职意向、生成目标岗位画像，并维护一份结构化的"岗位投递追踪表"。当用户说"我想换工作 / 不知道投什么岗 / 帮我看看我适合什么岗位 / 帮我管理投递进度 / 我投了好几家但记不住状态了 / 想做一个求职 OKR / 整理一下求职方向"，或上传简历但没说要改简历时，应该主动触发本 skill。本 skill 也适用于实习生、应届生、转行候选人在求职启动阶段做"自我盘点 + 目标画像 + 投递管理"三件事。

martin65536 Bundle

Team operations dashboard template — Linear/Asana-clean hybrid with sprint status hero, 4-segment progress bar, workstream cards, chronological activity stream with colored event badges, right-rail with today's schedule + team-presence + upcoming milestones. For team status snapshots, OKR reviews, "team this week" all-hands views.

martin65536 Bundle

Hand-drawn paper-wireframe template — white paper background, monochromatic ink palette, SVG turbulence "wobble" filters for pen-quiver authenticity, handwritten fonts (Caveat / Kalam / Ma Shan Zheng / Long Cang), wavy dividers, sketch-rect overlays, marginalia annotations. For PRD illustrations, IA flow docs, low-fidelity layout exploration, "draft / not final" stakeholder communication. Three skeletons (single-page editorial / app multi-screen flow / IA sitemap) — pick one up front based on the artifact, do NOT inherit only the brush strokes.

ldilov Bundle

repository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.

ldilov Bundle

plan and supervise low-overlap parallel work across git worktrees or stacked branches. use when a backlog could be split safely, when multiple small dependent changes need reviewable sequencing, or when merge-blocking risks must be made explicit before parallel execution.