「commitment」の検索結果

Validates a plan before committing to it - checks whether the ranking survives the assumptions, finds the most likely way it fails, and makes the trade-offs explicit via a Pareto frontier instead of an invented single score. Use before a launch, price change, migration, infrastructure change or major commitment, when running a premortem, when two objectives conflict, or when a decision depends on an assumption nobody has tested.

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

当用户因之前的承诺或表态而感到"必须坚持下去"，或在"明知不对但因说到做到而无法退出"时激活。用于识别承诺如何操控自我认知和行为，并区分机械一致与理性坚持。 不适用于: 纯信息查询、日常惯例性选择、正常的信守承诺行为。

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

Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).

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

Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.

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

Cross-reference project artifacts (WBS, meeting minutes, requirements docs) by date, participant, and action items. Extract commitments from meeting minutes and link to WBS tasks. Generate traceability reports showing which decisions were captured in which documents.

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

Knowledge base from NASA Risk Management Handbook (NASA/SP-2011-3422). Use for risk-informed decision making, continuous risk management, performance commitments, risk scenario diagrams, risk disposition types, risk burn-down schedules, objectives hierarchies, deliberation and alternative selection, risk driver identification, and RM planning for space and safety-critical programmes. Does not cover domain-specific PRA methods (fault trees, event trees) in procedural depth — see NASA PRA Procedures Guide for those.

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

Capture decisions and commitments after a meeting and draft a concise follow-up.

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

Pull fresh call recordings and transcripts from Fireflies.ai into an Obsidian vault over the official GraphQL API, then distill action items and commitments and reindex. Incremental and idempotent by transcript id. Triggers: "/fireflies-sync", "pull fireflies", "sync call recordings".

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

Use when the user asks to "build our social posting calendar", "set weekly slots and queue depth per channel", or "plan the evergreen recycle rotation"; produces the always-on brand calendar — pillar allocation with hero/hub/help balance and give:ask targets (all labeled Estimated starting heuristics to calibrate against own analytics, never scored rules), per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle with freshness re-checks, deliberate open slots for realtime/trend moments fed by trend-spotter go/skip verdicts, and first-comment/publish-order ops — cadence commitments filed to the channel registry, and no batch ships to the queue without a SHIP verdict from social-quality-auditor pre-publish mode. Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier. 社媒排期/内容日历/栏目配比/常青循环复用

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

Acceptance & Commitment Therapy (ACT) according to Steven Hayes: Hexaflex model with the six core processes of psychological flexibility.

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

Acceptance & Commitment Therapy (ACT) nach Steven Hayes: Hexaflex-Modell mit den sechs Kernprozessen psychischer Flexibilität.

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

Drafts an account plan from the CRM notes, emails, meeting notes and contracts the user provides: situation, stakeholder map, opportunities as recorded, risks, open commitments and proposed next actions, every line traced to a source and gaps marked UNKNOWN. Returns a DRAFT Markdown document in the chat. Use when the user asks to "build an account plan", "refresh the key account plan", "what do we know about this account", "account review for <customer>" or "what should happen next on this account". Do not use for preparing a first call with a prospect, use discovery-call-prep instead; for scoring inbound leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

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

Builds a role-tuned morning brief as a dated Markdown document covering emails that need replies, today's calendar with conflicts flagged, chat mentions and upcoming deadlines, in the section order set by a preset (project manager, executive assistant, IT admin, sales or custom) read from an editable config. Use when the user asks to "run my brief", "give me my morning brief", "start-of-day summary", "switch my brief to the sales preset" or "change what my brief covers". Do not use for tracking promises made or owed across days, use commitment-catcher instead. Drafts for human review; never approves, authorises or signs off.

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

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

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

Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").

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

Behavioral UX specialist applying choice architecture, friction audits, and commitment design to guide users toward intended actions without coercion. Use when optimizing conversion flows, onboarding, or checkout UX.

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

Improve, rewrite, and explain workplace English for an English-as-a-second-language professional in Australia. Use when the user asks to polish, fix, rewrite, improve, or check work emails, Slack or Teams messages, follow-ups, replies to managers or stakeholders, technical explanations, status updates, polite chasing messages, questions, pushback, issue explanations, or similar workplace communication for Australian companies. Ask targeted clarifying questions before rewriting when the intended meaning, recipient, action, deadline, blame, commitment, or technical conclusion is unclear.

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

Personal App-in-Skill customer-support desk (help desk) that triages incoming support tickets from email, WhatsApp, web chat, contact forms, and WeChat, drafts KB-grounded replies, and proposes actions, then holds every send behind a human approval queue with a pre-send quality gate (support-qa) that outputs SHIP/FIX/BLOCK, plus SLA and CSAT tracking. Use when the user invokes $kelly-support or /kelly-support, mentions 客服 / 工单 / 支持台, a support desk, help desk, customer service, support tickets, ticket triage, a knowledge base or canned macros, SLA / first-response time, CSAT, escalations, or refund requests, wants incoming tickets triaged into a needs_review → approved → done pipeline, agent-drafted replies grounded in a knowledge base and reviewed before sending, refunds and commitments gated behind human approval, or breaching-SLA tickets surfaced. This is the OPERATOR desk (agent + human), distinct from a visitor-facing chat bubble.

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

Orchestrates the end-to-end germline short-variant pipeline from FASTQ to a filtered, normalized, benchmarked VCF, chaining QC/trim, BWA-MEM2 alignment, duplicate marking, optional BQSR, calling (bcftools/GATK HaplotypeCaller/DeepVariant/DRAGEN), normalization, site+genotype filtering, annotation, and hap.py/vcfeval benchmarking. Use when deciding the pipeline-wide reference-genome commitment (GRCh38 analysis set vs T2T, ALT/decoy handling), sequencing the steps in the defensible order (normalize BEFORE annotate, filter site- then genotype-level), choosing the calling engine and single-sample vs cohort joint-calling, picking a filtering strategy by cohort size, or benchmarking stratified within GIAB confident regions. Hands off mechanism to the variant-calling and read-alignment component skills; not a re-teach of any single step.

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

Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.

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

Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.

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

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".

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

Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).

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

[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.

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