「the」の検索結果

Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).

日本語の概要は準備中です。原文の説明を表示しています。

Grounded in first principles, rigorously examine and refine a user's plan, task, decision, goal, strategy, proposal, or idea through structured, progressively deeper questioning, in order to bridge the gap between the User and the Agent. Use when the user explicitly requests grilling, challenge, pressure-testing, cross-examination, red-team review, pre-mortem analysis, or a decision audit. The goal is to uncover unclear objectives, hidden assumptions, contradictions, weak evidence, missing information, overlooked constraints, dependencies, risks, trade-offs, failure modes, and misalignment between intended outcomes and likely real-world results. Begin by establishing a shared understanding of the user's actual intent, goals, constraints, and success criteria. Ask focused, high-leverage questions rather than broad or repetitive ones. Adapt each question based on previous answers, probing deeper where uncertainty, unsupported assumptions, or strategic weaknesses remain. Regularly summarize the current understanding of the user's intent and position to confirm alignment, expose misunderstandings, and refine the problem or goal definition. Distinguish facts, assumptions, hypotheses, and unknowns. Challenge reasoning rigorously while remaining constructive, respectful, and solution-oriented. Continue until the reasoning is internally coherent, evidence-aware, constraint-conscious, risk-assessed, and translated into a clearer, more actionable goal, decision, or plan. Ultimately, achieving the super-alignment.

日本語の概要は準備中です。原文の説明を表示しています。

An agent makes an animated film of an average session with its own user, beginning to end, told with that user's real messages: whatever their routine is (code, writing, data, design, video). The agent sits at a desk in a room decorated from what it knows about the user, and the monitor shows their kind of work. Requests glide in as paper planes and unfold. Corrections are a 3D cartoon mallet that bonks, then turns to show the words on its face. Praise is a butterfly towing the words on a ribbon. The agent types each reply onto a sheet, folds it and throws it back. The film opens with the agent asleep until the monitor boots: "Initiating session with <name>". The agent composes its own orchestral score, cued to every action. p5.brush watercolour, rendered in HyperFrames. Trigger on: "a video of our session", "animate a session with me", "session story", "show what working with me is like", "make a film about me and my agent".

日本語の概要は準備中です。原文の説明を表示しています。

调香师与香水 (调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。) Master OS — automated mastery of 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、ac

日本語の概要は準備中です。原文の説明を表示しています。

CEO (Chief Executive Officer) — 一家公司「最高操作员」的工艺, 与泛泛「领导力 / 管理学」不同: (a) 设定战略与凝结愿景 (Drucker 的「企业的经营理论」+ Porter 论定位 + Hamilton Helmer 的「七力」+ Andy Grove 的「战略转折点」+ Roger Martin 《Playing to Win》); (b) 资本配置是 CEO 单一最高杠杆的工作 (Buffett/Munger Berkshire 致股东信 + William Thorndike 《The Outsiders 商界局外人》论 8 位非常规 CEO + Michael Mauboussin 论 hurdle rate + Bezos 年度致股东信「invariants vs bets」+ Mark Leonard Constellation Software); (c) 组建与领导高管班子 (Patrick Lencioni 《团队的五大障碍》+ Ben Horowitz 《艰难的事》+ Reed Hastings 《No Rules Rules》人才密度 + Andy Grove HOP《高产出管理》+ Lou Gerstner IBM 转型 + Marshall Goldsmith); (d) 董事会与投资人关系 (Larcker & Tayan 《公司治理重要》+ Bill George 《True North》+ 正式 CEO-董事长 / CEO-独立董事 protocol + 维权投资人 playbook + 资本市场沟通); (e) 企业文化与价值观作为操作系统 (Netflix 文化手册 + Amazon Leadership Principles + Bridgewater 《Principles》Ray Dalio + Schein 论组织文化 + 任正非 灰度 + 张瑞敏 人单合一 + 稻盛和夫 阿米巴); (f) 高不确定下的高风险决策 (Bezos Type 1/Type 2 决策 + premortem Klein + Kahneman 论 executive bias + RAPID/DACI + base rates + 情景规划 + 反思 premortem); (g) 对内对外沟通 (创始人 / CEO 致股东信作为机构构建工具: Bezos / Buffett / Reed Hastings 备忘录 / 任正非 内部讲话 + Town Hall + 危机沟通 Tylenol/Boeing/Wells Fargo + 应对维权投资人); (h) 跨阶段规模化 (创业 0→1 / 扩张 1→100 / 成熟期掌舵 / 危机转型): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde + Lou Gerstner 转型; (i) 创始人 CEO vs 职业经理人 CEO 的差异 (Paul Graham 「Founder Mode」2024 + Brian Chesky + Reed Hastings (创始人→职业过渡) + BCG/McKinsey 的「manager mode」+ 两者各自代价 + 什么时候切换)。诚实处理: 幸存者偏差 (单个 CEO 的打法 ≠ 普适规律, 学术研究显示 CEO 个人方差约 ⅓, 约 70% 来自行业 / 时代 / 运气 / 资本结构), 创始人崇拜, 区分可复制工艺与不可移植个人魅力, 治理与利益相关者责任 (员工 / 股东 / 社会), 反对 CEO 神话与 Welch 退休金扭曲 / Theranos / WeWork / FTX / Uber-Kalanick 时代 / Musk 80h+ / 996 工时崇拜。覆盖 founder-CEO (Bezos/Hastings/黄仁勋/Chesky/Brin/任正非) 与职业 CEO (Nadella/Gerstner/Pichai/Mulally/Lafley)。不含: 泛泛管理理论 (商业书已覆盖, 本 skill 专谈 C-suite 这个具体岗位), 不含: 「领导力」作为个人成长自助 (Robbins/Tracy/Maxwell 励志体裁), 不含: 「如何创业」早期战术 — 一旦有员工 / 董事会 / 资本, CEO 的工艺才开始。 (CEO (Chief Executive Officer) — the craft of being the top operator of a company, distinct from generic 'leadership/management': (a) setting the strategy and crystallizing the vision (Drucker's 'theory of the business' + Porter on positioning + Hamilton Helmer's 7 powers + Andy Grove's strategic inflection points + Roger Martin Playing to Win); (b) capital allocation as the CEO's single highest-leverage job (Buffett/Munger Berkshire letters + William Thorndike 'The Outsiders' on 8 unconventional CEOs + Michael Mauboussin on hurdle rates + Bezos's annual shareholder letter approach to invariants vs bets + Mark Leonard Constellation Software); (c) building and leading the executive team (Patrick Lencioni 'Five Dysfunctions' + Ben Horowitz 'Hard Things About Hard Things' + Reed Hastings 'No Rules Rules' on talent density + Andy Grove HOP + Lou Gerstner IBM turnaround + Marshall Goldsmith); (d) board and investor relations (Larcker & Tayan 'Corporate Governance Matters' + Bill George 'True North' + the formal CEO-Chair / CEO-Lead Director protocols + activist investor playbooks + capital markets communication); (e) culture and values as operating system (Netflix culture deck + Amazon Leadership Principles + Bridgewater 'Principles' Ray Dalio + Schein on org culture + 任正非 Ren Zhengfei 灰度 + 张瑞敏 Zhang Ruimin 人单合一 + 稻盛和夫 阿米巴); (f) high-stakes decision-making under uncertainty (Bezos Type 1 vs Type 2 + premortem Klein + Kahneman 'Thinking Fast and Slow' for executive bias + RAPID/DACI + base rates + scenario planning + premortem); (g) internal and external communication (founder/CEO letters as institution-builders: Bezos shareholder letters / Buffett letters / Reed Hastings memos / 任正非 内部讲话 + Town Halls + crisis communication Tylenol/Boeing/Wells Fargo + activist responses); (h) cross-stage scaling (founder-CEO of 0→1 / scaling 1→100 / mature-stage stewardship / turnaround): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde mining vs steady-state + Lou Gerstner turnaround; (i) the founder-CEO vs professional-manager-CEO distinction (Paul Graham 'Founder Mod

日本語の概要は準備中です。原文の説明を表示しています。

Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy sweep. The agent reads the prose's meaning directly — there is no claim-comment DSL to maintain. Pairs with TDD — the test suite is the deterministic behavioral gate, this skill is the semantic prose-vs-reality review.

日本語の概要は準備中です。原文の説明を表示しています。

Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.

日本語の概要は準備中です。原文の説明を表示しています。

Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The heavy multi-model plan-gate panel runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)

日本語の概要は準備中です。原文の説明を表示しています。

Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate panel is proportional (0-5 seats, by governance weight) and runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)

日本語の概要は準備中です。原文の説明を表示しています。

Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever the user wants to see how their branch will look on the live Gaia website before merging — "preview this branch", "show me what this looks like", "deploy a preview", "trigger a design preview", "can I see the site with these changes", "preview the skill profile", "check how this renders on the site", "spin up a preview deployment". This skill dispatches a Cloudflare Worker preview deployment for the current branch via GitHub Actions — no local build tooling required. Ideal for containerized environments, design reviews, and confirming that newly curated skills or profile pages render correctly before a PR is merged to main. The preview does NOT regenerate docs; it deploys `docs/` from the branch as-is. If your change depends on regenerated Class S artifacts, run `gaia dev docs` and commit those first — the preview then reflects them.

日本語の概要は準備中です。原文の説明を表示しています。

Presentation/Core/Engine split control plane — the canonical entry point for any work decomposing the Yuzu server into three binaries (presentation · core · engine) per ADR-0031-presentation-core-engine-decomposition / ADR-0032 (the admission interlock) / ADR-0033 (access-control spine). Use when the user says "/split", "/pce-split", "/decomposition", asks to plan or implement a split workstream (WS-A*, WS-B*, WS-X*), asks "what's our gap to the presentation/core split" or "is it safe to extract presentation/the engine yet", asks to audit split readiness, or starts work touching the seam (handlers calling stores directly, the INV-31-4 contract test, the Drogon port, `server/presentation` or `server/engine`, the `uce` DB grants, component service identity, or the ADR-0032 admission/grant/audit substrate — `use_case_run_id`, the release log, the capability-declaration registry).

日本語の概要は準備中です。原文の説明を表示しています。

Dispatch an explicit, user-dictated set of edits that spans TWO OR MORE zones of the GDD — the master spec, systems, content types, and flows — in one ordered pass. Writes nothing itself: it resolves each delta to its (target, zone), orders them so a system change lands before the content or flow that depends on it, delegates each to the owning skill (/unikit-gd-spec, /unikit-gd-system, /unikit-gd-content, /unikit-gd-flow), and closes with one /unikit-gd-verify pass. Use when you already know the changes and they touch more than one part of the design, e.g. "apply these GDD changes", "update the combat system and its loot and the boss flow". It also takes a /unikit-gd-review report file (applies its apply-ready bucket), and a bare /unikit-gd-apply reads the last /unikit-gd-verify output in the session. For a single-zone change call its owner directly; to research an open question use /unikit-gd-explore first.

日本語の概要は準備中です。原文の説明を表示しています。

Record a finding about the configured engine MCP server into .unikit/MCP-RECHECK-NOTES.md — the project's log of what has to be re-checked here. Use right after a call reported success while changing nothing, ate an argument, or validated a broken state, e.g. "write this down", "record this MCP finding", "the server lied — note it", "add a recheck note", "trap this". Takes three forms of input: the finding in one line, a path to a plan file (harvests the "## MCP Findings" table of that plan and nothing else), or nothing at all — then it takes findings already in the session first, and offers to scan the tables of plans touched since the last audit. The table only, never the plan body. Writes in the one allowed genre — a check to perform; never a lifted gate, never a named workaround, never a claim about what the server can or cannot do. Makes zero MCP calls and needs no editor. To replay, retire, or upstream existing notes use /unikit-mcp-audit instead.

日本語の概要は準備中です。原文の説明を表示しています。

Stand up reporting for a new audience — an external client, a business unit, a region, an executive team — end to end: what they need to see, whether the data exists, access and scoping, their place in the pipeline, the standard report set, and validation against numbers they can check themselves. Use when a new audience is onboarded, when an existing one adds a site, a region or a business unit, when their reporting is rebuilt after a change on their side, or when they say the numbers do not match their own records.

日本語の概要は準備中です。原文の説明を表示しています。

Draft the QA scope and plain-language Given/When/Then test scenarios for a Jira ticket, built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022). Use for DoD test and evaluation (T&E) across the Adaptive Acquisition Framework — the four test communities (contractor testing, developmental DT&E, operational OT&E, live-fire LFT&E); the five operational events (Operational Demonstration, EOA, OA, IOT&E, FOT&E) and the OTRR gate; the T&E Strategy / TEMP and its IDSK, with the upstream documents that feed it and the test plans that decompose it; the T&E organizations and oversight roles (USD(R&E), DOT&E, TRMC, the Service Executives and OTAs, the T&E WIPT, CDT); and pathway-specific T&E for all six acquisition pathways (Urgent Capability, Middle Tier, Major Capability, Software, Defense Business Systems). Statutory anchors include 10 U.S.C. §4171 (IOT&E) and §4172 (LFT&E/FUSL). This is guidance, not policy: it points outward to DoDI 5000.89 and the DoDI 5000-series for binding detail, and is thin on detailed test statistics/design-of-experiments methodology, cost estimating, the Acquisition of Services pathway, and any CUI/CAC-gated companion guides.

日本語の概要は準備中です。原文の説明を表示しています。

Compares one policy against one requirement set (standard, regulation, contract schedule or customer requirement) clause by clause and returns a draft gap review: each requirement element, the policy clause that appears to address it, an apparent match state, and every gap as a question with the clause reference on both sides. Never concludes that the policy complies; the owner decides. Use when the user asks to "gap our policy against the standard", "map this policy to the regulation clause by clause", "check the security policy against the customer's contract schedule", "compare our policy with the new edition" or "where does our policy fall short of the requirements". Do not use for mapping a requirement to the operating controls that implement it, use controls-gap-pack instead; for what a regulatory change means for the organisation, use regulatory-change-impact-note. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts the instructions field of a declarative agent that orchestrates a set of custom skills, under a character cap (default 8,000), from the skills' names and descriptions: role and scope, one routing rule per skill, workflow order, gates written as workflow holds, global rules, output format and what the agent never does. Returns the text in a fenced block with its character count labelled counted or estimated, plus a skill inventory, routing table, gate table, rules trace and open questions for the owner. Use when the user asks to "write the instructions for my agent", "draft a system prompt that ties these skills together", "tighten these agent instructions to fit the cap", "how should the agent route between these skills" or "revise my agent's orchestration text". Do not use to review a single SKILL.md, use skill-file-reviewer instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Synthesises exit interview notes or leaver survey responses into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim evidence, breakdowns by broad group only for groups that meet a minimum group size, referred items and open questions for the people team, without naming or identifying any individual. Use when the user asks to analyse, summarise, code, theme or report on exit interviews, leaver feedback, attrition interviews or departure surveys, or says "what are our leavers telling us", "theme these exit interviews" or "summarise the leaver survey". Do not use for customer or product feedback, use customer-feedback-theme-synthesis instead; for redacting one document with no theming, use document-deidentification-pass. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Pull the open Bonemeal action queue (landing pages and blog posts the user has not built yet) via the bonemeal MCP server, let the user pick which ones to build, dispatch each to the spawn-pages or spawn-blogs skill with the action's brief, and mark each completed in Bonemeal once the file is written. Use this whenever the user says "grow", "/grow", "build my Bonemeal queue", "what's in my Bonemeal queue", "build the suggested pages", or wants to act on Bonemeal's content suggestions. Stop and ask the user before marking actions complete the first time, then remember their preference.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言

日本語の概要は準備中です。原文の説明を表示しています。

Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.

日本語の概要は準備中です。原文の説明を表示しています。