「policy」の検索結果

Analysis of aggregate economic phenomena -- GDP measurement, inflation dynamics, unemployment theory, monetary policy (central banks, interest rates, money supply), fiscal policy (government spending, taxation, debt), and the business cycle. Covers Keynesian, monetarist, and new classical perspectives. Use when analyzing national or global economic conditions, policy debates, economic growth, recessions, or the interaction between monetary and fiscal authorities.

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

End-to-end research workflow skill for investment analysts and policy researchers. Three scope modes the user picks at trigger time — light (4-5 page decision memo, ~15 min, 0 charts), medium (12-15 page topic brief, ~1 h, 6-10 charts), heavy (flagship report 30-40 pages / 15k+ words, ~2-3 h, 25-35+ charts, multi-stage workflow, multi-LLM, PDF + Word + WeChat + HTML derivations). Reports default to English; the AI replies in the user's chat language. Battle-tested on real macro/policy/equity reports (e.g. Saudi Vision 2030 deep-dive). Triggers when user types /analyst-research, /flagship-research, or describes needs like "research report", "topic analysis", "investment research", "做研报", "投研报告", "主题分析", "深度分析", "policy assessment", "industry deep-dive". Not for: pure news commentary (use topic-brief), slide decks (use deckster-slide-generator), one-shot Q&A.

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

Evaluates dividend policy with payout sustainability, peer comparison, and investor preference analysis across growth and value contexts. Use when analyzing dividend policy, evaluating payout ratios, or designing dividend programs.

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

Policy for the cross-model council: when to hand off to an installed sibling plugin's own slash command (`/codex:*`) versus dispatching our `delegation-runner` (backend: codex|agy|…), which backend to pick, what permission posture to use, and the fan-out/cost discipline that applies regardless of backend — plus the council layer built on that substrate: which play to run, how a cast gets picked from the project roster, budget guardrails, and where project policy/commission config lives. Consult before delegating out to a peer agentic CLI, before choosing between a sibling plugin's command and our runner, before choosing a permission posture, before fanning out more than one external delegation concurrently, or before running a council play (`/…:council-run`).

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

Specialized research and analysis prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for data analysis, policy research, systematic evidence review, investigative research, and research-specific deliverables. Use when building prompts for quantitative data interpretation, evidence-based policy recommendations, literature reviews, causal analysis, hypothesis-driven investigation, or briefing documents. Trigger on: "prompt for data analysis," "research prompt," "policy brief prompt," "literature review prompt," "prompt for investigating," "systematic review prompt," "build a prompt for evidence synthesis," "causal analysis prompt," "briefing document prompt." Also use when user describes a research or analytical task and needs a structured Claude prompt for it. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or auditing Claude Projects (use rootnode-project-audit if available).

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

Create bulletproof Terms of Service and Privacy Policy documents for SaaS applications. Infers company information from codebase/marketing site, conducts comprehensive audits, drafts documents, then asks user ONLY for missing details at the end. Minimizes user interaction. Use when the user needs to draft, review, or update legal documents (ToS, Terms of Service, Privacy Policy, legal pages). Triggers on requests for legal documents, terms drafting, privacy policy creation, "cover our bases legally", liability protection, or legal compliance for software products.

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

Author structured policy documents and Standard Operating Procedures (SOPs) following ISO document control standards. Covers purpose, scope, roles, policy statements, procedures, compliance monitoring, and review schedules. Use when creating corporate policies, operational procedures, or governance documents.

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

Troubleshooting Connected App OAuth flows — IP relaxation vs IP restriction, refresh token policy traps (default kills the connection on first refresh), session-revocation semantics, the OAuth error-code catalog (`invalid_grant`, `invalid_client_id`, `unsupported_grant_type`), per-user vs admin-pre-approved flows, and the user-policy check (Connected App must be assigned to the user via profile / permset). Covers the Login History debug trail. NOT for designing the OAuth flow itself — use integration/oauth-flows-and-connected-apps. NOT for a SAML / SSO login failure — use security/sso-saml-troubleshooting. Trigger keywords: 'invalid_grant', 'OAUTH_APP_BLOCKED', 'redirect_uri_mismatch', 'LoginHistory Status', 'LoginSubType', 'OauthRefreshToken', 'ForwardedForIp', 'SetupAuditTrail connected app', 'refreshTokenPolicy zero', 'isSecretRequiredForRefreshToken', 'works once then fails', 'diagnosis record'.

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

Use when configuring or troubleshooting the B2B/B2C Commerce product catalog — ProductCatalog, ProductCategory, ProductCategoryProduct, WebStoreCatalog, CommerceEntitlementPolicy, product attributes, and product variants. Trigger keywords: product catalog, product category, commerce catalog, entitlement policy, product variants, product attributes, catalog visibility. NOT for taxonomy, attribute strategy or category navigation design — use admin/commerce-catalog-strategy. NOT for search ranking, facets or index rebuilds — use apex/commerce-search-customization. NOT for CPQ catalogs.

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

Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.

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

Detects missing, broken, or placeholder privacy policy links in-app, enforcing Guideline 5.1.1(i) which requires a functional, accessible privacy policy within the app itself.

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

Drafts a CCPA/CPRA-compliant privacy policy covering all required statutory disclosures under Cal. Civil Code §§ 1798.100–1798.199. Use when drafting or updating a California privacy policy, CCPA compliance notice, or consumer privacy disclosure for a business meeting CCPA applicability thresholds.

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

Drafts time-limited policy-limits demand letters that create an opportunity-to-settle record for third-party bad faith exposure. Use when the user mentions time-limited demand, policy limits demand, bad faith notice, Stowers demand, civil remedy notice, failure to settle demand, excess exposure letter, insurer settlement opportunity, or needs help with acceptance mechanics for a policy-limits offer. Also trigger for Georgia O.C.G.A. § 9-11-67.1 compliance, Florida statutory bad faith prerequisites, or documenting insurer refusal to settle.

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

Manages government affairs, public policy communications, and collective action aligned with B Corp GACA standards. Creates policy position papers, advocacy communications, regulatory response documents, and transparent lobbying reports. Use when user asks about government relations, public policy, advocacy, lobbying, regulatory affairs, collective action, or political engagement transparency.

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

Resolve, validate, and audit manuscript integrity and applicable requirements for academic manuscripts and paper artifacts. Use when Codex needs to determine active paper rules from manuscript state, paper type, venue, submission stage, or workflow mode; lint a LaTeX paper project; assess submission readiness; create or update a paper policy profile; explain why a rule is active; or validate the paper-policy registries. Do not use as the primary skill for prose drafting, peer review, rebuttal writing, citation discovery, or figure/table creation.

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

Produces a draft controls and gap pack from a requirement, regulation, standard or policy and the organisation's control descriptions: obligations broken out of the source text, the controls that appear to address each, apparent coverage, gaps, questions for control owners and actions to assess. Never concludes compliance or that a control is effective; owners and audit assess. Use when the user asks to "map this regulation to our controls", "run a controls gap analysis", "break this standard into obligations" or "where is our control coverage thin". Do not use for comparing a policy document against a standard, use policy-gap-review instead; to draft evidence requests from the mapped controls, use control-evidence-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Turns a set of questions (form exports, helpdesk logs, meeting Q and A, chat threads, a plain list) plus the source documents the user supplies into a DRAFT FAQ grouped by theme: every answer quoted or paraphrased from a named source with a reference, verbatim quotes for dates, figures, eligibility and obligations, UNKNOWN where the sources are silent, a source register with precedence, a conflicts table and a routing list of unanswered questions to owners. Use when the user asks to "build an FAQ from these documents", "answer these questions from the policy", "turn the Q and A into an FAQ page", "group these questions and answer them from the guide" or "what do our documents say about these questions". Do not use for the manager FAQ of a changed HR policy, use policy-change-briefing instead; for checking whether a document's own claims are evidenced, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.

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

Applies standard AI review policy guidelines for upstream (design) phase reviews.

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

Applies standard AI review policy guidelines for midstream (implementation) phase reviews.

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

Applies standard AI review policy guidelines for downstream (test/QA) phase reviews.

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

Enforce Kubernetes admission policies using OPA Gatekeeper with ConstraintTemplates, Rego rules, and the Gatekeeper policy library.

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

Implement GCP Organization Policy constraints to enforce security guardrails across the entire resource hierarchy, restricting risky configurations and ensuring compliance at organization, folder, and project levels.

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

Reviews and approves blocked agent network requests in the TUI. Use when approving or denying sandbox egress requests, managing blocked network calls, or using the approval TUI. Trigger keywords - nemoclaw approve network requests, sandbox egress approval tui, customize nemoclaw network policy, sandbox egress policy configuration.

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

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

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