策划、销售、财务、法务、项目管理（3889 个）
Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized.
中文简介正在准备中。当前显示原文说明。
Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one.
中文简介正在准备中。当前显示原文说明。
Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.
中文简介正在准备中。当前显示原文说明。
Use when reviewing a contract clause-by-clause from your party's side — buyer/seller/vendor/licensee. Triggers on 'review this contract', 'redline this MSA', 'is this clause a problem'.
中文简介正在准备中。当前显示原文说明。
Use when editing AGENTS.md (package root) or templates/AGENTS.md (consumer) — enforces Thin-Root contract: hard char ceilings, ≥40% pointer ratio, mandatory emergency-triage block.
中文简介正在准备中。当前显示原文说明。
Ground a brand strategy from the corpus — archetype, opposable positioning, voice and tone, messaging framework. Use to decide who a brand is for, what it stands for, and how it sounds.
中文简介正在准备中。当前显示原文说明。
Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.
中文简介正在准备中。当前显示原文说明。
Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.
中文简介正在准备中。当前显示原文说明。
レビュー専用サブエージェント(fable-reviewer・opus-reviewer等)を起動する反復レビュー・ループが共有する起動契約と手順の正本。Agentツールでの同期起動、2ラウンド目以降の同一エージェント継続、レビュー指示文の追加要件、失敗の扱い、1ラウンドを回して結末を出すまでの流れを定義する。内部専用でユーザーが直接使うものではない。
中文简介正在准备中。当前显示原文说明。
Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.
中文简介正在准备中。当前显示原文说明。
Finalize an implemented rolling-wave slice for user review. Use when the user wants Codex to review the current branch state against a ready-for-review or in-review slice contract, confirm and fix required findings, repeat review and verification until no required findings remain, ask before accepting findings that materially change project shape or contradict project assumptions, record review state, and leave the clean slice in review for complete-slice.
中文简介正在准备中。当前显示原文说明。
Use when spawning an agent()/workpool() subagent with an outputSchema, or a task agent whose frontmatter sets structured: true, to reduce yield retry failures by stating the exact result envelope and required fields in the prompt.
中文简介正在准备中。当前显示原文说明。
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
中文简介正在准备中。当前显示原文说明。
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
中文简介正在准备中。当前显示原文说明。
Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
中文简介正在准备中。当前显示原文说明。
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
中文简介正在准备中。当前显示原文说明。
Skill for the Workflow-contracts area of paddock. 51 symbols across 11 files.
中文简介正在准备中。当前显示原文说明。
[Content] Use when a workflow step or the user asks for marketing strategy: positioning, channels, messaging, campaigns, budget and KPIs.
中文简介正在准备中。当前显示原文说明。
[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.
中文简介正在准备中。当前显示原文说明。
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
中文简介正在准备中。当前显示原文说明。
Work leads in Telegram: find prospects by topic, keep only those who self-mentioned it, resolve their handle including through shared groups, pitch personalized and grounded in real templates, run a two-step scheduling close, triage follow-ups, and capture everyone in the CRM. Triggers: "find leads for <topic>", "pitch this prospect", "run outreach".
中文简介正在准备中。当前显示原文说明。
Вычислить нашу тёплую аудиторию в Facebook — кто регулярно лайкает и комментирует НАШИ посты — и превратить её в актив: дедуп, перелинковка с CRM, заведение карточек новым людям, промоушен постоянных в лайк-ростер и в очередь… Триггеры «/fb-audience», «кто нас лайкает», «собери аудиторию», «кто наши постоянные», «вычисли аудиторию», «кто чаще всего реагирует», «fb audience», «who likes our posts»
中文简介正在准备中。当前显示原文说明。
Pull fresh follow-up call notes from a dedicated Telegram group into the CRM layer of a vault. Incremental and idempotent by message id, safe to re-run, and the manual counterpart of the weekly scheduled job. Triggers: "/faaa-sync", "pull the follow-up notes".
中文简介正在准备中。当前显示原文说明。
Найти человека и его каналы связи по нашим ЖЕ данным: архив ТГ 16.7 млн сообщений, CRM, книга чатов, почта, досье. Триггеры: /find-person, найди хэндл, как с ним связаться, найди контакт, где он есть, кто это, найди телеграм <имя>, найди человека. НЕ путать: /find = поиск по волту; /triage = кого касаться; этот = где у человека дверь и что мы о нём уже знаем.
中文简介正在准备中。当前显示原文说明。