Product & Planning

vamfi Skill

This skill should be used when the user asks to "shape stories", "create a backlog", "break this epic into stories", "write user stories with acceptance criteria", "define the product backlog", "estimate stories", or needs to convert a PRD or delivery plan into an executable sprint backlog.

vamfi Skill

This skill should be used when the user asks to "create a delivery plan", "build a roadmap", "plan the phases", "define milestones", "map the critical path", "estimate the timeline", or needs a structured phased plan for delivering an initiative.

10cg Bundle

同步 User Story 与 Forgejo Issue，发布 PRD 到 Wiki。 使用场景："同步 Story 到 Forgejo Issue"、"发布 PRD 到 Wiki"

10cg Skill

从 PRD 生成 System Architecture 文档骨架，自动提取关键信息并填充模板。 使用场景："从 PRD 生成架构文档"、"创建系统架构骨架"

lidessen Bundle

Estimate the necessary work before converting it into agent tokens, time, or money. Use when comparing implementation options, setting an agent budget, choosing estimate granularity or error tolerance, planning a discovery probe, or asking "how much work is this really?" / "预算怎么估？" / "工作量评估" / "误差容忍度". Do not use to invent a token price, approve spend, or replace strategic choice, execution, or calibration evidence.

lidessen Bundle

Use this Skill, not a named task Skill, when that Skill or capability is the object of user-level setup, installation, migration, or configuration. An installed or runtime-discovered copy is target evidence, not a desired source. If the human has not supplied the selected capability's source, return `NEEDS_INPUT` before reading it, inventory, lookup, planning, or action; never inspect secret values. Use for "set up my agents on this machine", "migrate my AI coding setup", "新设备配置 Codex/Cursor/Claude Code", "update my global agent workflow", or reconstructing selected skills, harness guidance, plugins, MCP, hooks, permissions, runtimes, and authentication prerequisites. Setup does not imply marketplace discovery, CLI/provider installation, or full-toolbox adoption. Do not use for project-local agent workflow design, fleet policy, sessions/caches, or unrelated dotfiles.

deanpeters Bundle

Convert evidence-based operating-model findings into an owned 30-, 90-, 180-, and 365-day sequence of interventions, learning milestones, dependencies, and decisions.

jonhill90 Bundle

Author or review a Product Requirements Document — the problem being solved, who it's for, the goals and explicit non-goals, and the success criteria a stakeholder would use to judge whether the problem is actually solved. Use when asked to write, update, or review a PRD, or to define what a product or feature should do and why before any technical approach is chosen. Not for how it will be built — that is spec, which a PRD hands off to once the problem and goals are settled. Not a general project plan or pre-flight checklist — see close-the-loop for that.

jonhill90 Bundle

Author or review a technical specification — architecture, interfaces, data flow, and the implementation approach engineers will build against, plus the trade-offs behind the choices made. Use when asked to write, update, or review a technical spec or design doc, or to decide how something will be built once what it should do is already settled. Not for defining what a product should do and why, or who it's for — that is prd, which a spec is written against. Not an in-session pre-flight checklist for a single change — see close-the-loop for that.

jovd83 Bundle

Use when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.

celestialdust Skill

Turn a prd.md into acceptance.md — the Given/When/Then prose contract that is the human-anchored oracle for THIS feature's behavior across the entire autonomous run — the only human-anchored oracle the run has. Reach for this the MOMENT a prd.md exists (on a UI feature, once frontend-design has explored the interface) and BEFORE any planning, TDD, or QA — test-driven-development and quality-verification REFUSE to run without a signed acceptance.md. If you are about to write "acceptance criteria", "definition of done", test scenarios, or Given/When/Then for a feature, you need this first. Behavioral-only: keep ALL design floors out (those belong to frontend-design's contract).

celestialdust Skill

Capture every external thing the autonomous run needs — API keys, MCP servers, services, runtime deps, test fixtures, accounts — as a typed-kind manifest with NO values and NO commands. Use during Spec right after the PRD lands, and again during Plan once slices exist. ALWAYS run this before an AFK/autonomous wave so preflight-readiness can refuse to start on a missing dependency. If you are about to paste a secret value or a check command into a config file, STOP and use this instead.

codejunkie99 Skill

Use when the user wants to draft Objectives and Key Results for a team, individual, or company with measurable targets and confidence levels. Triggers include "write OKRs", "OKR planning", "set quarterly goals".

dbc-oduffy Bundle

Review a plan/design doc, a code diff, or a roadmap spine/sprint slice — findings land on the artifact.

dbc-oduffy Skill

The EM's first move on any PM ask — size it, then route to plan, shape, roadmap, or dispatch. Fires whenever novel engineering work is asked of the EM, by any combination of words: this is a shape test, not a phrase list. Mutually exclusive with pickup.

dbc-oduffy Skill

EM-PM ceremony to review and prioritize the technical debt backlog.

dbc-oduffy Skill

PM-GATED. Turns raw vision into ratified OKRs plus roadmap-seed stubs.

dbc-oduffy Bundle

PM-GATED. Shape research into ratified, graphed roadmap batons.

dennydkt Bundle

调用受用户配置约束：高自动、中先确认、低须明确开启；用户指定其他技能时禁止接管。分析跨部门与多方协作中的权力、利益、影响、支持和阻力，设计推进顺序。用于跨部门推动、资源争取、多人意见不一、项目政治复杂。触发：$xb-stakeholder、谁会反对、怎么推动跨部门。

deuxksy Bundle

GUI, web, app 제품 아이디어나 초기 기획 자료를 단계별 Deep Research 산출물(benchmark research, feature 추출, screen design, 기술 선정, 실행 가능 AI agent 문서)로 발전. Use when screen 기반 디지털 제품 기획, 탐색적 research를 MVP 계획으로 전환, 또는 검증된 기획 결과에서 AGENTS.md, CONTEXT.md, ROADMAP.md, DESIGN.md 생성 시.

googlecloudplatform Skill

Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.

ryanmaclean Skill

Run Auto-Claude AI-powered roadmap generation for any project directory. Analyzes project structure, target audience, and existing specs to produce a strategic feature roadmap. Use when planning milestones, phases, or strategic direction for a project.

uipath Bundle

UiPath StudioAdmin AOps (`uip aops`) — SourceControl discovery plus CICD pipelines. Drives `aops connection` / `repo` / `project` / `solution` to resolve a GitHub or Azure source binding, `aops pipeline processes` to pick an already-published Orchestrator process, then composes a PipelineDto for `pipeline create` / `save-and-run` and follows runs via `aops execution logs --follow`. Replaces the retired `uip sc` and `uip cicd` tools. For AOps governance policies (`uip gov aops-policy`)→uipath-governance. For `uip solution pack/publish/deploy`→uipath-platform. For workflow authoring (.xaml/.cs)→uipath-rpa.

uipath Bundle

UiPath Insights job monitoring and read-only inspection via `uip insights` — job execution metrics, failure analysis, and process performance; filter discovery of Insights-active folders, processes, queues, and machines; real-time alert definition, history, delivery, and entitlement reads; Insights user, role, and group reads. Alert and RBAC writes are not covered. For Orchestrator job start/stop/logs→uipath-platform, root-cause analysis of specific errors→uipath-troubleshoot, RPA workflow authoring→uipath-rpa, org-level users, groups, or roles→uipath-admin.

uipath Bundle

UiPath automation discovery — mines Slack/email/wikis/CRM/HRIS/ERP for repetitive work, SPOFs, and replicable models; produces a 4-tier prioritized opportunity report with UiPath implementation paths, then sizes build effort (complexity band → pack-hours → contingency). Use to discover automation opportunities, find what to automate, estimate/size a delivery, or run an internal automation audit across an organization. For building a specific automation→uipath-rpa, authoring a Flow→uipath-maestro-flow, working with agents→uipath-agents.

uipath Bundle

Maintain build-time skill flavors in the UiPath skills repository. Use when adding or editing skill-flavor marker blocks, sparse flavor overrides, generic flavor discovery, marker-free default or custom npm packages, package inspection, flavor CI, or composer/package tests. Preserve SKILL.md as the complete default, keep overrides exceptional, and validate finished trees and tarballs.

kiku-jw Bundle

Default execution-planning skill for almost any non-trivial repo task. Turn a raw task, feature request, PRD, or project brief into durable plan, status, and test-plan files, then hand back a concise ready-to-execute proposal.

kiku-jw Bundle

Build an implementation-ready spec bundle when a plain PRD is no longer enough: minimum useful contracts, schema, test plan, blueprint, gates, ADRs, boundaries, and GitHub-ready task breakdown. Use when ambiguity or architecture risk would otherwise slow execution.

kiku-jw Bundle

Validate a raw product idea before PRD or implementation: buyer, pain, workaround, promised outcome, smallest wedge, distribution path, proof sought, kill criteria, and the next honest lane. Use when an idea still needs market or wedge truth.

kiku-jw Bundle

Run a multi-lens council when a product decision is fuzzy, risky, or high-impact and one answer is not enough. Use for wedge selection, pricing, launch readiness, roadmap trade-offs, go/no-go calls, or other decisions where blind spots matter more than speed.

kiku-jw Bundle

Turn a GitHub Issue into a clean human-agent control loop with canonical issue state, deterministic PRD intake, explicit machine markers, and clear handoff points. Use when GitHub should be the durable control surface instead of chat alone.

kiku-jw Bundle

Build a Codex execution pack from a raw task or PRD: `AGENTS.md` plus `docs/PLAN.md`, `docs/STATUS.md`, `docs/TEST_PLAN.md`, and `docs/BACKLOG.md`, with optional prompt surfaces and a spec companion when the work is large enough to justify them.

lgtm-hq Skill

Interactive dispatcher for backlog work. Asks one routing question — drive PRs to merge, or implement issues to open-PR state — then follow-ups based on the answer, and hands off to implement-issues / babysit-pr with standing policy applied. Use when asked to work the backlog or run /backlog.

lgtm-hq Skill

Promote a quick-and-dirty prototype to an lgtm-hq-standard repo - commit WIP lint-clean, grill the design, spec the backlog as milestone/epic/issue tree, then implement issue by issue. Use when asked to properize, productionize, or turn a prototype into a proper project.

lgtm-hq Skill

Implement a set of GitHub issues in parallel - triage or take an explicit issue list, group by file-conflict, create a worktree per lane, delegate to sub-agents, open a PR per lane; never merges. Use when asked to implement issues, work the backlog, or pick up multiple issues in parallel.

murphytrueman Skill

Generate visual output — charts, dashboards, and trend graphs — from audit findings, session history, or system health data. Produces an interactive HTML dashboard or a set of SVG/Mermaid charts that make design system health visible at a glance. Trigger when someone says: visualise the findings, show me a chart, create a dashboard, graph the trends, make this visual, health dashboard, show me the data, I need charts for the stakeholder meeting, turn this into a visual report, or anything about producing visual representations of design system data. Do NOT trigger for producing a written stakeholder brief without visuals — use stakeholder-brief for that. Do NOT trigger for running an audit — run the audit skill first, then use visual-report to visualise the output.