企画、営業、経理、法務、プロジェクト管理（2,864 件）
概要と使いどころ
Evaluates assumption, rejection, and assignment decisions for executory contracts and unexpired leases in bankruptcy. Use when analyzing contract decisions, evaluating lease rejections, or modeling cure cost exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates ESG strategy with materiality assessment, stakeholder analysis, and value creation linkage for corporate decision-making. Use when analyzing ESG strategy, assessing material ESG factors, or linking sustainability to value.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates Dutch auction mechanics with optimal pricing strategy, odd-lot proration, and shareholder base analysis. Use when analyzing Dutch auctions, modeling tender strategies, or evaluating self-tender economics.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates signal half-life, turnover implications, and capacity constraints for systematic alpha factors. Use when analyzing signal persistence, evaluating factor decay, or estimating strategy capacity.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous AI Sales Development Rep for B2B export — handles lead discovery, BANT qualification, multi-channel outreach (WhatsApp/Email/Telegram), CRM management, and deal pipeline tracking. Built for cross-border trade.
日本語の概要は準備中です。原文の説明を表示しています。
Smart contract and secure API contract security analysis — invariant checking, access control, reentrancy, and integer overflow patterns. Implements Checks-Effects-Interactions pattern, formal invariant verification, and OpenSCV vulnerability taxonomy for Solidity/EVM and Rust/Solana contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds OpenAPI contract component with type generation.
日本語の概要は準備中です。原文の説明を表示しています。
OpenAPI contract standards for API specification, versioning, and type generation.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt business logic flaws — race conditions, workflow state bypass, parameter pollution affecting logic, coupon/discount abuse, refund logic, multi-step process bypass, integer overflow, negative quantities, double-spend. Use when looking for non-CVE bugs that require understanding the app's intended workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a complete subcontract from a firm's template, awarded bid, and project specs. Outputs a Word document. Triggers: 'subcontract', 'sub agreement', 'write contract', 'draft subcontract'. Requires awarded bid.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate tabulated subcontractor bids against specs and drawings — scope gap analysis, exclusion risk scoring, award recommendation. Triggers: 'evaluate bids', 'bid evaluation', 'lowest responsible bidder'.
日本語の概要は準備中です。原文の説明を表示しています。
Find the most valuable commercial insight and the monetization point closest to lawful revenue for a project, product, service, website, community, content account, open-source tool, or business idea. Use when a user asks how to monetize, who pays, why people do not buy, what to charge, whether to keep building, what to stop, what to do next, or asks to continue or deepen an earlier business analysis. Answer the user's actual question before asking for more information and carry the analysis forward without repeating it. When the buyer, purchased result, or delivery ability is unknown, do not select them from industry stereotypes; use explicit conditional candidates and an evidence-gathering next step. Not for investment advice, income forecasts, get-rich-quick schemes, or guaranteed results.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a frozen workflow contract and collect evidence by implementing only approved scope/files and checks. Use when PLAN_FROZEN=true and Execution Contract is complete, then hand off to review.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.
日本語の概要は準備中です。原文の説明を表示しています。
Review execution against the frozen Execution Contract, produce Evidence/Gaps, and decide pass or unfreeze. Use after ac-execute or at milestone acceptance gates.
日本語の概要は準備中です。原文の説明を表示しています。
Perform an adversarial review of the current uncommitted changeset, validating it against project contracts and architectural intent.
日本語の概要は準備中です。原文の説明を表示しています。
Prospective failure analysis using Gary Klein's pre-mortem technique. Assumes complete failure, works backward to identify risks, leading indicators, and circuit breakers. Counters optimism bias by forcing systematic exploration of failure modes before they materialize. Use for project plans, architecture decisions, technology adoption, business strategy, or feature launches. Triggers on "리스크", "위험", "실패하면", "swing-mortem", "뭐가 잘못될 수 있어", "risk", "what could go wrong", "걱정되는 점", "failure modes", "리스크 분석", "위험 분석".
日本語の概要は準備中です。原文の説明を表示しています。
用户想预防某个潜在风险或问题时; 当系统出现早期预警信号但尚未爆发时; 当已出现问题需要防止恶化和扩散时; 当需要建立长期防护机制时。 不适用于: 紧急危机处理(系统正在崩溃, 需要急救而非预防); 纯历史回顾 (分析过去发生了什么但不涉及未来预防)。
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to finalize a deal, handle tough objections, or create a "Mutual Action Plan" to close a sale.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is working a B2B SaaS deal from qualified opportunity to closed-won — preparing discovery calls, structuring demos or POCs, handling a specific objection, qualifying with MEDDIC/MEDDPICC/SPICED, building mutual action plans, navigating negotiation or procurement, or reviewing pipeline health, forecast accuracy, and deal velocity. Not for finding or prospecting new leads (use prospecting) or upstream positioning (use product-position).
日本語の概要は準備中です。原文の説明を表示しています。
Escalate blocked scraping campaigns with provider-neutral proxy rotation — decide between datacenter, residential, and mobile pools, integrate rotation with scrapling, configure session stickiness for stateful flows, monitor cost and health, and stay inside legal and ethical boundaries. Use as the next step after `headless-web-scraping` client-side stealth (StealthyFetcher, rate limiting, robots.txt) is insufficient and traffic is legitimate.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a comprehensive spectroscopic analysis campaign by defining the analytical question, assessing sample characteristics, selecting appropriate techniques using a decision matrix, planning sample preparation for each technique, sequencing analyses from non-destructive to destructive, and defining success criteria with a cross-validation strategy.
日本語の概要は準備中です。原文の説明を表示しています。