Product & Planning

huruikagi Skill

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

huruikagi Skill

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.

huruikagi Skill

Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.

ctsstc Skill

Insert a phase into the roadmap

ctsstc Skill

Remove a phase from the roadmap

danhvb Skill

Plan the business analysis approach, stakeholder engagement, governance, and information management for a project

davidlee Skill

Use when the user wants to create, survey, triage, tag, or transition a doctrine backlog item (issue / improvement / chore / risk / idea) — `doctrine backlog` is the CLI surface; use this skill to drive the correct verb for the intent.

davidlee Skill

Use when authoring, revising, normalising, or reviewing a doctrine product specification/PRD - the durable product intent, requirements, success measures, behaviours, and verification basis for an evergreen capability. use before creating or scoping slices that descend from shared product intent. use when a request asks for product requirements, functional requirements, non-functional requirements, product scope, acceptance gates, out-of-scope boundaries, success measures, or agent-readable product context. do not use for one-off change planning, implementation design, technical architecture, or phase execution.

davidlee Skill

Use when a named subsystem, capability, or code surface needs governance coverage assessed before authoring a spec — deciding what is already governed by an existing PRD / tech spec / ADR, what is dark, and where new spec boundaries should fall by product altitude and C4 level. Use before creating or scoping a product or technical spec for an unfamiliar or partially-governed surface. Use when a request asks to "assess coverage", "find governance gaps", "what's already specified", "where should this spec's boundary sit", "one spec or several", "what needs a PRD vs a tech spec", or "is this subsystem properly documented". Produces a reviewable coverage-map artifact that feeds `/spec-product` and `/spec-tech`. Do not use when the target spec and its boundary are already known and unambiguous — go straight to `/spec-product` or `/spec-tech`. Do not confuse with `doctrine coverage` — unrelated CLI verb for requirement verification.

serhiy-bzhezytskyy Skill

Use when you need to FIND work in an unfamiliar repo rather than pick it off a tracker — a new house, or one whose issue backlog is claimed faster than you can read it. Four probes cost minutes each and need no domain knowledge: does any test fail when run alone, does the suite survive a shuffled order, does the race detector fire, does a fuzz target crash. Each one asserts on the SELECTOR'S YIELD, never on the exit code, because every runner treats "matched nothing" as success. And the yield of these probes is a function of the codebase's age and hardening, not of your effort: four probes over a thirteen-year-old repo with OSS-Fuzz integration found nothing in an hour, and the same shuffle probe found a real defect on a three-year-old fork in one run. Trigger terms: new repo, where do I start, find a bug, no good first issues, backlog is claimed, flaky, test isolation, order dependent, -shuffle, -race, go test, cargo test, runtest.

theseus-run Skill

Use when creating, updating, reviewing, or promoting Theseus roadmap items, including public roadmap notes, internal roadmap status maps, planning lanes, GitHub issue readiness, and OSS roadmap hygiene.

dynatrace-oss Skill

First test skill for discovery testing

dynatrace-oss Skill

Second test skill for discovery testing

dynatrace-oss Skill

Second occurrence of duplicate skill

lee-to Skill

Load the essential AI Factory project context before work begins. Reads configured DESCRIPTION, ARCHITECTURE, ROADMAP, RESEARCH, RULES, and applicable AGENTS.md files, then returns a compact session handoff suitable for continuing or forking. Use at the start of a new session or after context loss.

lee-to Bundle

Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".

lee-to Skill

Create or update a project roadmap with major milestones. Generates the configured roadmap artifact (default .ai-factory/ROADMAP.md) — a strategic checklist of high-level goals. Use when user says "roadmap", "project plan", "milestones", or "what to build next".

moonlight-lupin Bundle

BM25-based skill retrieval plugin for Hermes Agent. Replaces the full skill list in the system prompt with a names-only compact view (~2K tokens) and injects top-K relevant skill descriptions per turn via BM25 retrieval (~300 tokens). Saves ~9K tokens/turn. Use when system prompt token overhead from skills is a concern, or when skill discovery quality matters.

moonlight-lupin Bundle

Use when you need to discover an API's surface — poke a base URL to find its type (REST, GraphQL, SOAP, JSON-RPC), auth scheme, available endpoints, rate limits, and CORS policy. Also probes MCP servers (HTTP and stdio) to discover tools, resources, and prompts with full input schemas. Runs a Python probe script that checks well-known discovery paths (OpenAPI/Swagger, GraphQL introspection, health, .well-known), fingerprints the server, sends OPTIONS for CORS, detects auth from 401/403 responses, and guesses common REST resources. For MCP, performs JSON-RPC initialize handshake then tools/list, resources/list, prompts/list. Feed it a base URL or MCP server URL, optionally with auth credentials.

moonlight-lupin Bundle

Convert Claude Code plugins into self-contained Hermes plugins — discovery analysis then full conversion

anothersava Bundle

Capture an off-task idea to the project's memo backlog, or list and act on existing memos

saitarrun Skill

This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story estimation".

saitarrun Skill

Design docs, RFC (Request for Comments) process, ADR (Architecture Decision Records), code comments (WHY not WHAT), documentation structure, knowledge discovery and search, cross-team communication. Use when documenting decisions, writing design docs, or improving knowledge sharing.

timsmykov Bundle

Create, rewrite, adapt, shorten, expand, audit, and polish evidence-bounded Russian or English text across academic, professional, essay, copywriting, and creative modes. Use when asked to draft or revise text, calibrate voice, turn notes into prose, or diagnose writing quality. Do not use for literature discovery, citation retrieval, peer review, statistical analysis, or document-file manipulation without a writing task.

huangqianqian120 Skill

User research and customer discovery methods. Use when: - Understanding customer needs - Designing interview questions - Finding product opportunities - Validating assumptions

armelhbobdad Bundle

Design a skill scope through guided discovery. Use when the user requests to "create a skill brief" or "brief a skill."

armelhbobdad Bundle

Pre-code stack feasibility verification against architecture and PRD documents. Use when the user requests to "verify a tech stack" or "verify stack."

randallliuxin Skill

Game Design Document phase for one tag. On the first ever run, runs the full Socratic interview, produces GDD.md, and derives ROADMAP.md (split into SemVer-tagged release tags). On every subsequent run, focuses the conversation on the current tag (the earliest entry in ROADMAP.md without a git tag), optionally updates GDD.md / ROADMAP.md, then generates the current tag's PLAN/STRUCTURE/SCENES/STYLE/ASSETS at the project root. Explicit invocation only — use /gm-gdd.

maragudk Bundle

Guide for working with XBRL, the standard for digital business and financial reporting -- reading and writing instance documents, Inline XBRL (iXBRL), xBRL-JSON and xBRL-CSV, taxonomies and linkbases, dimensions, contexts, units, and facts. Use this skill whenever the user touches XBRL in any form -- parsing or generating an instance, extracting figures from a filing or annual report, handling `xbrli:context`, `contextRef`, `unitRef`, `decimals`/`precision`, `ix:nonFraction`, `ix:nonNumeric`, `ix:hidden`, `xbrldi:explicitMember`, `xbrldi:typedMember`, hypercubes, DTS discovery, taxonomy or report packages, or the Open Information Model. Triggers even when the word "XBRL" never appears -- ESEF, iXBRL, SEC EDGAR company facts, `us-gaap:`/`ifrs-full:`/`dei:` prefixed tags, financial statement tagging, or a file arriving as `.xbrl`/`.xbri`/`.xbr` are all enough.

ctsstc Skill

Workflow for project discovery phase

charliedream1 Skill

Correlation and cointegration analysis — co-movement discovery, deep return-correlation analysis, sector clustering, realized correlation, Engle-Granger / Johansen cointegration, half-life, Kalman dynamic hedge ratio, cross-market linkage analysis, and pair-trading signal generation

rabbit-ivan Bundle

Produces a PRD recommendation, draft, or document-level diagnosis: decides whether a PRD is even needed (vs a goal, design doc, or task), drafts one from a product problem, audits/repairs an existing PRD for drift and unverifiable acceptance, or judges whether to split / merge it. Use whenever the user mentions a PRD, product requirements, requirements doc, or spec — writing, rewriting, refining, auditing, scoping, or splitting/merging one — even if they never say "PRD". Be pushy: trigger on casual asks like "turn this into a spec", "draft requirements for X", "is this PRD too big", "this PRD is a mess", "do we even need a PRD for this", "one PRD or two". Also on 写 PRD, 帮我写需求文档, 需求文档, 产品需求文档, PRD 拆分, PRD 合并, 这个 PRD 要不要拆, PRD 粒度, 帮我改需求文档.

rabbit-ivan Bundle

Audits whether each requirement, workflow step, role, field, state, module, layer, abstraction, or rule deserves to exist and returns a razor verdict: a Keep/Merge/Defer/Delete/Replace/Prove-first classification of every concept, the strongest survival argument for anything cut, and a concrete cut/proof list. Use whenever the user wants to apply Occam's razor, simplify or trim a PRD / architecture / workflow / data model / state machine, challenge whether something is necessary, or spot fake requirements, premature abstractions, or over-engineering — even if they never say "razor." Trigger on 用奥卡姆剃刀, 剃刀一下, 砍需求, 砍掉没用的东西, 收一收复杂度, 这个字段/状态/模块/分层有必要吗, 这个抽象是不是多余, 是不是伪需求, 是不是过度设计, 这步能不能去掉, 这些角色/状态是不是太多了, and English like "is this over-engineered", "do we really need this layer", "this feels bloated, what can we delete", "too many fields".

rabbit-ivan Bundle

Verifies a drifted, patched-over document block by block — against the current conclusions, the codebase, and anything else checkable — then rewrites it around the evidence: blocks that survive verification keep their original wording, blocks that fail are removed (never repaired into a plausible-looking fix), and the result ships as the rewritten document plus a disposition table (keep / delete / undecided, each citing the check) and an open-questions list. Use whenever a document has accumulated messy, doubtful claims through rounds of discussion and the user wants it verified and cleaned, not patched again. Trigger on 重写这份文档, 这文档已经烂了, 文档已经不对了, 逐条核实这份文档, 把不对的内容删掉, 按最新结论重写, 文档跟讨论结论对不上, 别再缝缝补补了, 推倒重写, and English like "rewrite this doc", "verify this doc and strip what's wrong", "this doc has drifted". For a findings report without a rewrite use hai-audit-docs-internally; if the document is a PRD use hai-prd; if it is a plan or goal document use hai-goal.

rabbit-ivan Bundle

面向产品需求整合与 PRD 产出。当用户提供多份需求文档/口述记录/图片/思维导图/录音转写，需要抽取关键信息并按 PRD 模板生成需求文档时使用。本技能覆盖多格式输入整合、缺口澄清与 PRD 输出。

rabbit-ivan Bundle

Generates a complete, self-contained multi-section HTML report — header + one-line verdict, Mermaid structure map, decision matrix, risk/proof table, and next-move block — from an idea, requirement, PRD, goal, review, architecture topic, plan, or proposal, and returns the generated file path. Use whenever the user wants content turned into a visual report, visualized page, HTML report, webpage version, dashboard, or slides/PPT-like web artifact — and trigger even on casual phrasings: 可视化一下, 做个可视化, 做成网页, 做个网页版, 把这个评审做成网页, 做成一页 HTML, 输出 HTML, 做个汇报页/展示页, 做成 PPT 样子的网页, 弄个好看点的报告, 整理成一份报告页面, 带 mermaid 图的报告, render this as a page/webpage, make it visual/interactive, turn my analysis into slides-like html, dashboard of this. When the user wants a single shareable card instead of a multi-section report, use create-visual-card.