ビジネスのスキル

Report CRM health for a period with counts, trends, owners, and the next fixes.

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

Use when the user needs an ideal partner profile: who to recruit, in what tiers, what good looks like, and who to say no to.

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

Sort contract deviations by the user's playbook priority and route each one to its business owner or counsel.

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

Extract contract facts into a source-cited tracker without interpreting ambiguous language or giving legal advice.

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

Compare clause versions or a clause with supplied playbook text, showing exact additions, removals, and open decisions.

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

Use when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone: the CI brief with landscape, change blocks, pricing read, and win strategy.

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

Turn signed contract duties into an owned, source-cited tracker while routing unclear obligations to counsel.

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

Set up a non-advisory contract review using user-supplied agreements, playbooks, owners, and counsel gates.

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

Extract renewal and notice facts into an owned tracker, with source cites and no automatic renewal or cancellation action.

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

Analyze and improve business processes. Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix.

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

Use when a deal needs the money case: value proposition, demo plan, proof-of-concept scope, ROI model, or the proposal that carries them.

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

Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.

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

Use for month-end close support: the checklist with owners and status, accrual review, account reconciliations, control evidence, and audit preparation.

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

Review churn risk from dated usage, outcome, support, relationship, and contract evidence, then propose the next check.

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

Use to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.

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

Use when the user wants named candidates for an open role, more people for a thin slate, lookalikes of a benchmark person, or a read on how hard the search will be.

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

Use when the user names a release, a launch date, or a launch tier, or asks whether the business is ready to launch: the readiness assessment, sequenced plan, enablement spec, and 90-day measure.

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

Expert knowledge of SED/EESSI integration in melosys-api. Use when: (1) Understanding SED document types (A001, A003, H-series, X008), (2) Debugging SED sending/receiving flows and RINA integration, (3) Working with BUC (Business Use Case) creation and management, (4) Understanding saga steps for SED handling (SEND_VEDTAK_UTLAND, SED_MOTTAK_RUTING), (5) Troubleshooting mottakerinstitusjoner (recipient institutions) issues.

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

Expert knowledge of vedtak (verdict) processing in melosys-api using the saksflyt saga pattern. Use when: (1) Debugging vedtak-related issues or failures in IVERKSETT_VEDTAK_* processes, (2) Investigating race conditions where vedtak fails due to concurrent operations, (3) Understanding how fattVedtak triggers MEDL updates, letters, invoices, and case closure, (4) Tracing why vedtak got stuck or failed at specific steps, (5) Understanding the relationship between VedtakService classes and Prosessinstans, (6) Debugging issues with brev (letters), fakturering (invoicing), or MEDL registration.

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

Expert knowledge of Kodeverk (code registry/enums) system in melosys-api. Use when: (1) Understanding enums (Sakstyper, Behandlingstyper, Behandlingstema, etc.), (2) Validating legal combinations of case/treatment types, (3) Debugging "ugyldig kombinasjon" errors, (4) Adding new enum values or combinations, (5) Mapping between internal codes and external systems (MEDL, Oppgave, SED).

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

Use when a working Spark implementation should be simplified without changing its observed behavior, ownership, compatibility, or public contract.

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

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.

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

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

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

Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates.

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