「business case」の検索結果

Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.

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

Build business cases with cost-benefit analysis, ROI calculations, risk assessment, implementation timeline, and stakeholder analysis

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

Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases", "test coverage", "TEST-", "test-first". Consumes EPIC- (scope), API-, DBT-, BR-, UJ-. Outputs TEST- entries with Given-When-Then format. Feeds v0.7 Implementation Loop.

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

MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables. Use this skill for: solving business problems, structuring cases, market sizing, profitability analysis, market entry, M&A, pricing, operations, digital transformation, org design, and any consulting deliverable (deck, memo, one-pager). Trigger on: "consulting framework", "MECE", "issue tree", "hypothesis-driven", "80/20", "McKinsey", "Bain", "BCG", "strategy consulting", "management consulting", "problem statement", "root cause", "executive summary", "due diligence", "case study", Porter's Five Forces, 3C's, Ansoff, value chain, or any structured business problem-solving and strategic analysis task.

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

Assesses startup viability through business model canvas analysis, unit economics validation, and market timing evaluation. Use when evaluating startup pitches, analyzing business model sustainability, or assessing product-market fit.

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

Build a business case with costs, benefits, and ROI. Use when the user says "cost-benefit analysis", "business case", "ROI calculation", "is this worth it", "justify the investment", "payback period", "benefits realization", "financial justification", "total cost of ownership", "should we build or buy", "investment appraisal" - even if they don't explicitly say "CBA".

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

Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.

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

Use this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.

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

Turns a business need and its constraints into a DRAFT RFP requirements pack: traced functional and non-functional requirements with priorities, mandatory gates, evaluation criteria with weights left to the business owner, and fact-seeking supplier questions. Solution-neutral; never names a supplier or product. Use when the user asks to "write the RFP requirements", "turn this business case into tender requirements", "draft the supplier questionnaire", "structure our RFQ from this brief" or "set up evaluation criteria before we go to market". Do not use for responses already received, use rfp-comparison-pack to compare them or supplier-evaluation-matrix to score them instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Financial Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, finance risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CFO review", "pressure-test the numbers in this business case", "what would a CFO say about this", "challenge the payback and run costs" or "prepare this for the investment committee". Do not use for delivery or capacity questions, use coo-reviewer instead; for architecture or vendor questions, use cto-reviewer; for positioning or demand, use cmo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Generate comprehensive investor-ready business case document with market, solution, financials, and strategy

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

Hunting skill for business logic vulnerabilities. Built from 12 public bug bounty reports. Covers coupon-race-stacking (Instacart, Stripe, Reverb), negative-quantity-in-cart price tampering (Upserve, Eternal/Zomato), decimal/fraction price-field overflow (Shipt), client-side checkout amount trust on PayPal redirect (WordPress.org), price-per-unit mass-assignment (Krisp), and archived-price swap / cart-TOCTOU (Stripe). Use when hunting business logic — heavy emphasis on financial-impact-demonstrated cases.

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

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

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

WooYun business logic vulnerability methodology — 22,132 real cases across 6 domains (authentication bypass, authorization bypass, payment tampering, information disclosure, logic flaws, misconfiguration) and 33 vulnerability classes. Use for ANY security testing, auditing, or code review of web apps, APIs, or business systems — even without explicit "security" keywords. Triggers: penetration testing, security audit, vulnerability, bug bounty, payment security, IDOR, password reset, weak credentials, unauthorized access, race condition, parameter tampering, code review, 渗透测试, 安全审计, 漏洞挖掘, 支付安全, 越权, 逻辑漏洞, 业务安全, SRC, 代码审计. Also triggers on implicit intent: "test this endpoint", "find bugs", "can I bypass this", "帮我测测这个接口", "这个参数能不能改", "帮我找bug".

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

Build and deliver a raise request that actually works — the evidence, the number, the timing, and the exact words — instead of hoping it gets noticed. Use when asked how do I ask for a raise, I deserve more money, prepare me to ask for a raise, or negotiate a pay increase at my job. Produces a value case built on your actual contributions and market rate, a specific target number with justification, the right timing and person, a script for the conversation, and responses to the likely pushbacks — turning 'I want more' into a business case your manager can say yes to.

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

HR business partnership across talent strategy, org development, and employee relations. Use when building workforce plans, designing performance reviews, resolving employee relations cases, or advising leadership on org change.

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

Generate Amazon and cross-border ecommerce product images from a product business card. Use when the user asks for a white-background image, showcase image, selling-point image, hero image, detail image, lifestyle image, one or more ecommerce images, or a complete image set. Always collect the business card first, then confirm image types, output location, filenames, and the generation plan before creating images.

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

A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.

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

Create and improve Odoo custom module tests using the Odoo test framework. Use when the user asks to add tests, create TransactionCase/HttpCase tests, test Odoo business logic, mock external APIs, use Form helper, test access rules, test workflows, or improve Odoo test coverage.

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

Deconstructs SaaS operating metrics including ARR, NRR, gross retention, magic number, rule of 40, and cohort economics. Use when analyzing SaaS businesses, benchmarking software metrics, or evaluating subscription model health.

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

"Corporate-governance practice playbook: board composition, three lines of defense, audit/compensation/nomination committee operations, independent-director governance, stakeholder communication, IPO governance upgrade, and family-business professionalization. Use for board-structure design, independent-director selection, three-lines implementation, IPO governance preparation, major governance incidents (fraud, scandal, insider trading), or family-business corporatization. Triggers: 『董事會組成』『獨董沒發揮功能』『三道防線』『上櫃治理補強』『家族法人化』『委員會分工』『ESG 治理』『審計委員會』『薪酬委員會』『提名委員會』. For Taiwan EMBA corporate-governance/finance/law/ESG cases. Focuses on listed-company and IPO practice; governance theory: use Asgard `grad-governance`; 9-box/繼任規劃/接班人才盤點: use `ops-talent-strategy`; COSO ERM/風險地圖/風險委員會運作: use `biz-erm`.".

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

"SME and family-business management for Taiwan's industrial structure (98% SME, 70%+ family-controlled listed). Integrates four pillars: resource-constrained decision-making, family governance (Tagiuri-Davis three circles), four-layer succession, and professionalization. Use for sub-200-employee strategy, capital-constrained prioritization, family-vs-professional-manager conflict, founder handover, family-constitution design, or SME financing limits. Triggers: 『二代接班』『家族企業』『中小企業』『家族憲章』『家族辦公室』『傳承規劃』『小公司策略』『資源有限』『家族跟專業經理人』『三圓模型』『隱形冠軍』. For 成大 EMBA SME strategy, 政大 EMBA family-business succession, 逢甲 EMBA SME management cases. Fills Asgard gaps in resource-constrained strategy and Chinese-family governance.".

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

Business logic flaws are application vulnerabilities where valid functions are abused in unintended ways: price manipulation via hidden field tampering, workflow step-skipping, function call limit bypass (coupon reuse), process timing exploitation (race conditions on balance updates), and request forging via guessable/predictable parameters. Detect using Burp Suite proxy interception, HTTP POST/GET parameter analysis, and misuse-case testing against multi-step workflows. Tools: Burp Suite, OWASP ZAP.

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

Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for eliciting the requirements in the first place — use admin/requirements-gathering-for-sf. NOT for user-story authoring — use admin/user-story-writing-for-salesforce. NOT for UAT test design — use admin/uat-test-case-design. NOT for Apex test design — use apex/test-class-standards. NOT for backlog prioritization — use admin/moscow-prioritization-for-sf-backlog. More triggers: traceability.md, build-layer traceability, REQ-XXX and FG-XXX id mapping, artefact-to-requirement orphan report, coverage-gap report, check_rtm.py --manifest-dir, owning run-time agent column, design decision ref column, metadata API name in a traceability row.

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