企画、営業、経理、法務、プロジェクト管理（2,816 件）
概要と使いどころ
Guidance for helping users create and accomplish goals. Read it before you create a goal for the user when no goal-creation contract is in context, and whenever you help with an existing goal. A Goals-tab creation turn already carries that contract and does not need this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze vendor and contractor coordination systems for performance scoring, competitive bid evaluation, SLA compliance tracking, and vendor risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Audit whether a product is ready for enterprise sales. Use when you need to assess SSO/SAML/SCIM support, RBAC maturity, multi-tenancy data isolation, audit logging coverage, public API quality, SLA operational readiness, SOC2/ISO27001 certification gaps, GDPR data residency controls.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an ASC 606 / IFRS 15 revenue recognition engine for SaaS — the five-step model (identify contract, identify performance obligations, determine transaction price, allocate to performance obligations, recognize as POs are satisfied) applied to subscription contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze preventive and predictive maintenance scheduling systems including CMMS/EAM work order optimization, asset condition scoring with Facility Condition Index, PM compliance tracking, maintenance backlog reduction, reliability-centered maintenance strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze an HR operations system for headcount planning effectiveness, attrition pattern detection, compensation benchmarking accuracy, workforce analytics maturity, and onboarding process optimization..
日本語の概要は準備中です。原文の説明を表示しています。
Audit legal aid and public defense case management systems -- client intake workflows, Federal Poverty Level eligibility screening accuracy, conflict-of-interest checking, document assembly and e-filing integration, court deadline calculation with rule-based calendaring.
日本語の概要は準備中です。原文の説明を表示しています。
Audit e-discovery and litigation document review systems -- data collection pipelines (PST, MBOX, SharePoint, Slack), document processing (OCR via Tesseract/ABBYY, metadata extraction, deduplication), Technology Assisted Review (TAR 1.0/2.0/CAL with recall/precision tracking).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze donor retention and CRM systems — lapse risk scoring and prediction models, stewardship workflow automation, donor lifetime value (LTV) modeling, communication personalization engines, giving pattern analysis, and retention metric benchmarking.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze debt payoff software — avalanche vs snowball strategy engines, interest calculation accuracy, amortization schedules, payment scheduling automation, credit score impact modeling, hardship accommodation workflows, and progress visualization.
日本語の概要は準備中です。原文の説明を表示しています。
Audit contract management codebases for clause extraction accuracy, obligation tracking completeness, risk scoring model quality, renewal management, SLA monitoring, liability exposure, force majeure handling, and IP assignment detection..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze carbon accounting and emissions tracking software for Scope 1/2/3 calculation accuracy, GHG Protocol compliance, offset verification, supply chain emissions, reporting standards (CDP, TCFD, GRI, SASB, SEC), reduction target tracking, and audit trail integrity..
日本語の概要は準備中です。原文の説明を表示しています。
Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Qualify a sales opportunity using the MEDDIC framework. Use when the user says "qualify this deal", "is this deal real", "MEDDIC qualification", "MEDDICC framework", "should I pursue this opportunity", "deal review", "how qualified is this prospect", "pipeline review prep", "forecast this deal", "sanity check on this opportunity", or wants to assess whether a sales opportunity is worth pursuing and at what pipeline stage.
日本語の概要は準備中です。原文の説明を表示しています。
Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and prepare for a sales discovery call. Use when the user says "prep for discovery call", "discovery call questions", "how to structure my discovery call", "first call with a prospect", "what to ask on a discovery call", "sales call prep", "plan my discovery call", "initial call framework", or wants to prepare for or debrief a first sales conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
日本語の概要は準備中です。原文の説明を表示しています。
Write a performance-based job description. Use when the user says "write a JD", "draft a job posting", "create a job description", "help me post this role", "write requirements for this position", or wants to define what success looks like in a role - even if they don't explicitly say "job description". Also use when a hiring manager says "I need someone who can do X, Y, Z" and needs that translated into a structured posting.
日本語の概要は準備中です。原文の説明を表示しています。
Build a structured interview scorecard for a role. Use when the user says "create an interview scorecard", "build an interview guide", "what questions should I ask for this role", "help me evaluate candidates consistently", "design the interview process", or wants to assess candidates against defined criteria - even if they don't explicitly say "scorecard". Also use when a recruiter or hiring manager wants to prevent gut-feel hiring.
日本語の概要は準備中です。原文の説明を表示しています。
Build a candidate sourcing strategy and outreach pipeline. Use when the user says "where do I find candidates for this role", "build a sourcing plan", "write a cold outreach message", "we're not getting enough applicants", "our pipeline is dry", "help me find passive candidates", "write a LinkedIn message", or wants to increase the volume or quality of candidates in the funnel - even if they don't explicitly say "sourcing strategy". Also use when a recruiter needs to go beyond job postings to find talent.
日本語の概要は準備中です。原文の説明を表示しています。
Run a recruiter-hiring manager intake meeting to kick off a search. Use when the user says "I need to kick off hiring", "run the intake call", "prepare for the intake meeting", "align with the hiring manager on this role", "we're opening a req", or wants to define hiring criteria and process before sourcing begins - even if they don't explicitly say "intake meeting". Also use when a recruiter needs to get a hiring manager aligned on what "great" looks like before anyone talks to a single candidate.
日本語の概要は準備中です。原文の説明を表示しています。
Construct a compelling job offer. Use when the user says "write an offer letter", "help me make an offer", "how should I structure this offer", "what should we include in the offer", "how do I explain the equity", "the candidate is negotiating", or wants to convert a candidate from interested to accepted - even if they don't explicitly say "offer letter". Also use when a recruiter needs to explain comp philosophy or total compensation to a candidate.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and run a post-interview candidate debrief. Use when the user says "run the debrief", "how do we decide on this candidate", "let's calibrate", "we need to make a hire/no-hire call", "prep the debrief meeting", or wants to structure the decision-making process after interviews are complete - even if they don't explicitly say "debrief". Also use when a recruiter wants to prevent groupthink or HiPPO effect (highest paid person's opinion) from dominating the decision.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis".
日本語の概要は準備中です。原文の説明を表示しています。