「go」の検索結果

Format documents for Japanese enterprise approval workflows including ringi (稟議), purchase requests (購入申請), and internal proposals. Handles bilingual requirements, proper keigo levels, required approval sections, and corporate template compliance.

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

Periodic inbox scan that categorizes new emails by project/client, identifies action-required items, and generates prioritized summary with FYI/requires-response/requires-action/blocked-waiting classifications. Use for inbox overview, project-based email grouping, or action item extraction.

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

Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.

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

ゴール記述モデルの良い点・悪い点を分析し、改善点と改善のための問いを生成

匠Methodのゴール記述モデルを作成

ゴール記述モデルを作る時の観点を説明する

検証結果に基づいてゴール記述モデルを洗練・修正する

Use when advising, planning, reviewing, reporting, operating, or improving CTO and technology leadership work across strategy, cybersecurity management, SME/COE, functional and technical requirements, framework selection, people, organization, delivery, risk, KPI, roadmap, budgeting, governance, audit, R&D, stakeholder communication, culture, politics, and sector-specific leadership.

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

Use when performing cybersecurity operations - offensive or defensive - including threat detection and hunting, SOC operations, incident response, digital forensics and DFIR, malware analysis and reverse engineering, threat intelligence, cloud/container/network/application/API security, identity-access and zero-trust, OT/ICS and endpoint security, vulnerability and supply-chain management, DevSecOps, cryptography, AI security, compliance and governance, and red-team or penetration testing under signed rules of engagement; routes to one of 800+ technique playbooks mapped to MITRE ATT&CK, D3FEND, and NIST CSF.

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

End-of-life detection for runtimes (Node, Python, Java, Go, .NET) and key packages — surfaces past-EOL items, items reaching EOL within 90 days, and EOL base images for containers. Use when planning a runtime upgrade, auditing for unsupported versions, gating a deploy against EOL deps, or producing a remediation roadmap.

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

Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "scope this analytical question". (narrative-common)

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

Create a look-alike audience from a seed audience and a candidate population dataset. Classifies Rosetta Stone attributes, generates the same materialized-view scoring pipeline Lookalike Studio emits (Naive-Bayes categorical weights + Gaussian continuous similarity), gates on approval, submits via `narrative_workflows_create`, and monitors the build to completion. Use when: "create a lookalike audience", "find more users like this segment", "expand my seed audience to 500k similar users", "score the population against my customers", "build a look-alike of dataset X". (narrative-audience)

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

Conducts rigorous authoring and review of Playwright E2E tests. Enforces accessibility-first locators, web-first assertions, strict isolation, and DAMP architecture. Use when generating, refactoring, or reviewing any Playwright test code.

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

Export Codex rollout/session JSONL as a self-contained HTML report that can be opened offline. Use when a user provides a complete session file path or Codex session ID, or asks to export a Codex session to HTML, generate a session report, or convert a rollout to HTML. Supports exact full-ID lookup in the CODEX_HOME sessions and archived_sessions directories.

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

Reconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with no standard text; RG 1.152 Rev 4, BTP 7-18, BTP 7-19, other SRP Chapter 7 sections, and NUREG/CR contractor reports are outside the pack; reflects the pinned 2013 and 2016 editions, not later agency actions; synthesized reference notes, not legal or licensing advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. § 105).

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

Reconstructed reference notes on US FAA approval guidance for airborne software and airborne electronic hardware, built from four public-domain sources (FAA Order 8110.49A, AC 20-115D, AC 20-152A, AC 00-69; documents dated 2017-07-21 to 2022-10-07, pinned 2026-10-12). Use for how FAA certification staff plan and conduct software reviews (certification liaison, desk versus on-site review, review planning agreements), how the level of FAA involvement (LOI) is picked and scored with the Appendix A worksheets, how software conformity inspection works (software part and installation conformity, ASE and ASI tasks, Form 8120-10), what AC 20-115D recognizes and how DO-178B processes and tool qualification transition to DO-178C/DO-330 (supplements, FLS, UMS, legacy software changes), and what AC 20-152A adds for airborne electronic hardware (simple versus complex custom devices, robustness and HDL code coverage, tool assessment, previously developed hardware, COTS IP, COTS devices, circuit board assemblies), and what AC 00-69 adds as best practices for change impact analysis, data and control coupling, and design-level error handling (best practices, not guidance and not a means of compliance). SCOPE LIMITS: FAA guidance only, and guidance is not regulation (ACs are acceptable means, not the only means); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, supplement, or SAE ARP text, which are copyrighted and named only (see the avionics-signpost pack); no AC 00-72 (named, not packed); no DO-178C software-level objective tables; no EASA AMC 20-115D or AMC 20-152A content (use easa-rules); reflects the pinned source dates, not later FAA actions; synthesized reference notes, not legal advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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

Knowledge pack synthesized from JSP 376 Defence Acquisition Safety Policy V1.1 (April 2024, Ministry of Defence, Open Government Licence v3.0): acquisition safety requirements, safety artefacts, and their application across the standard acquisition lifecycle. Covers the policy frame and legislative baseline, SRO and User responsibilities, safety management and safety requirements, test and evaluation and the safety case, supervision and approvals decision support, and the seven lifecycle phases. SCOPE LIMITS: single-source (JSP 376 V1.1); MOD policy and guidance, not statute; builds on JSP 815 and cites JSP 655, neither reproduced here (use jsp-815 for the SMS); Chapter 4 (Non-Standard Acquisition) is unpublished in V1.1 and is not in this pack; no DEF-STAN text (Def Stan 00-056 is named, not quoted); no other JSP reproduced. Reconstructed reference notes, not MOD guidance, and no official status.

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

Signpost (not a knowledge pack) for maritime safety and class rules: SOLAS Consolidated Edition 2024 (IH110E) as the paywalled statutory core, ISM Code & Guidelines 2018 (ID117E), ISPS Code 2003 (K116E) and the 2021 guide (IB116E), and COLREGS 2026 (IC904E), with designation, edition, owner, status, and official URL only. Contains no source content. Free-path layers are US flag implementation (eCFR Title 46 and USCG circulars), the USCG Navigation Rules PDF, UK MCA notices under Open Government Licence v3.0, and class portals (DNV, ABS, Bureau Veritas). None of those layers is the IMO consolidated text. No in-repo pack covers these instruments.

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

Reconstructed reference notes on EU and UK medical-device software, built from six sources captured 2026-10-13: MDCG 2019-11 rev.1 (June 2025), MDCG 2020-6 (April 2020), MDCG 2020-13 (July 2020), MDCG 2020-7 (April 2020), MDCG 2020-8 (April 2020), and the MHRA software-applications guidance (2023-07-01) with its stand-alone software PDF. Use for SaMD qualification and classification, legacy-device clinical evidence, the clinical evaluation assessment report, the PMCF plan, and the PMCF evaluation report, under EU MDCG guidance or UK MHRA guidance. SCOPE LIMITS: EU MDR and UK MHRA device software only; no IEC 62304, ISO 13485, or ISO 14971 text; no MDR or IVDR regulation body text; MDCG guidance is not legally binding; MHRA guidance is UK-specific; synthesized notes, not legal advice. LICENCE: Per-document: European Commission reuse policy (Decision 2011/833/EU, CC BY 4.0, attribution and indication of changes) for the MDCG documents; Open Government Licence v3.0 for the MHRA guidance; reconstructed notes with attribution; official PDFs not redistributed.

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

Reconstructed reference notes on US FDA medical-device software regulation, built from seven public-domain FDA sources (the QMSR final rule 89 FR 7496, FDA device software guidance documents, and the eSTAR program page; pinned 2026-10-12). Use for regulatory pathways and premarket submissions (510(k), De Novo, PMA, eSTAR), premarket software documentation levels (Basic or Enhanced), software validation and Computer Software Assurance, the Quality Management System Regulation (QMSR, 21 CFR 820), medical-device cybersecurity (secure product development, SBOMs, FD&C Act section 524B, labelling), clinical decision support boundaries, off-the-shelf software, MDDS and other software-function scope questions, and the 510(k) software-change trigger. SCOPE LIMITS: US FDA device regulation only; no EU MDR or UKCA content (see `med-device-eu`); no ISO 13485, ISO 14971, or IEC 62304 text, which are named and summarized only as FDA obligations; no drug, biologic, or combination-product rules; reflects the pinned source dates, not later FDA actions; synthesized reference notes, not legal advice and not a substitute for the guidance documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).

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

Knowledge pack reconstructed from JSP 815 Defence Safety Management System V1.3 (Ministry of Defence, Open Government Licence v3.0): the SMS Framework, all 12 Elements with their Expectations and Performance Statement themes, and Annexes A to F plus H. Covers the Defence Safety Function and which JSP applies, leadership and safety culture, organisation and SEMS applicability, legislation and exemption certificates, risk assessment and safety cases, supervision and contracting, competence and letters of delegation, equipment and infrastructure safety, performance and incident management, and assurance, audit, and the ISO 45001 clause mapping. SCOPE LIMITS: single-source (JSP 815 V1.3 with Annex H V1.2); carries no DEF-STAN 00-051 or DEF-STAN 00-970 content, no JSP 375, JSP 816; acquisition safety policy is in jsp-376, no Annex G (Assurance Toolkit), and no ISO 45001 text (clause numbers only). This pack is reconstructed reference notes, not MOD guidance, and has no official status.

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

Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.

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

Audit ClawJS/Clawix code hygiene without editing code, producing categorized findings, baseline status, and validation evidence.

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

Execute a bounded ClawJS/Clawix code hygiene cleanup campaign from an audit report, one category and repo at a time.

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