3,475 件 ・ 関連度順
概要と使いどころ
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /claude-setup:build on non-trivial features in repos that have (or should have) a CONTEXT.md.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /build on non-trivial features in repos that have (or should have) a CONTEXT.md.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end meeting workflow skill. Pre-meeting: research attendees, build agenda, prepare talking points, create pre-read. Post-meeting: process notes into action items, draft follow-up emails, log decisions, update project notes. Useful for preparing for important calls, during post-meeting processing, when following up with attendees, and for building a running decision log. Use when the user says "prepare for meeting", "meeting prep", "process meeting notes", "meeting follow up", "meeting machine", or "prep for my call".
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when important product, technical, or founder decisions need to be captured as durable context with rationale, tradeoffs, and follow-up implications.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply dual-process theory to diagnose whether judgments arise from fast intuitive (System 1) or slow analytical (System 2) processing and identify resulting cognitive biases. Use this skill when the user needs to explain why quick decisions go wrong, design choice architectures that account for cognitive defaults, audit decision processes for heuristic errors, or when they ask 'why do people misjudge probability', 'how to reduce snap-judgment errors', or 'when does intuition fail'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply pecking order theory (Myers and Majluf, 1984) to analyze how information asymmetry drives financing hierarchy decisions. Use this skill when the user needs to explain why firms prefer internal over external financing, interpret equity issuance as a negative signal, evaluate capital raising decisions, or when they ask 'why did the stock drop on the equity offering', 'should we use debt or equity', or 'why do firms hoard cash'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply governance theory to analyze multi-level, network, and collaborative governance arrangements beyond traditional government. Use this skill when the user needs to evaluate public-private partnerships, analyze multi-stakeholder governance structures, compare governance models across sectors, or assess institutional arrangements for collective decision-making — even if they say 'who governs this', 'public-private collaboration', or 'how are decisions made across organizations'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply behavioral economics concepts including bounded rationality, prospect theory, mental accounting, and nudge theory to analyze decision-making biases. Use this skill when the user needs to understand why people make irrational economic decisions, design choice architectures, or apply nudges to influence behavior — even if they say 'why do customers make bad choices', 'how do we encourage people to save more', or 'design a better default option'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Management accounting toolkit for internal decision support: ABC costing, variance analysis, transfer pricing, and responsibility accounting. Use for product profitability disputes, budget variance diagnosis, inter-division pricing design, and business-unit manager performance evaluation. Triggers: 『這個產品真的賺錢嗎』『成本分攤』『事業部之間怎麼算錢』『本月成本超支』『評核廠長績效』『內部轉撥』『ABC 作業成本』『差異分析』『責任中心』『管理會計』. For Taiwan EMBA cases, term reports, and management-decision simulations (台大／陽交／成大 財管必修).".
日本語の概要は準備中です。原文の説明を表示しています。
"Solve the newsvendor problem for single-period ordering decisions under uncertain demand. Use this skill when the user needs to determine optimal order quantity for perishable goods, seasonal products, or one-time purchase decisions — even if they say 'how much to order for this season', 'perishable inventory', or 'single-period ordering'.".
日本語の概要は準備中です。原文の説明を表示しています。
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Turn meeting notes, transcripts, or rough bullets into decisions, action items, owners, due dates, and follow-up queues. Use when the work is repetitive meeting cleanup or recap writing. Do not use for negotiation strategy, legal advice, or executive decision framing.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate monthly S&OP or integrated business planning cycles by aligning demand, supply, inventory, capacity, and executive decisions with a standard meeting rhythm and decision log. Use when operations teams need a demand review, supply review, pre-S&OP reconciliation, or executive S&OP pack. Do not use for single-SKU replenishment math only.
日本語の概要は準備中です。原文の説明を表示しています。
Build structured 3-scenario financial models (Base / Bull / Bear) for business planning or investment decisions. Sensitize revenue and cost drivers across scenarios, produce P&L summaries, cash flow bridges, and executive narratives. Aligns with FP&A 2.0 and CIMA Management Accounting standards. Use when leadership needs to understand the financial impact range of a decision. Do not use for statutory financial reporting or audit-ready financials.
日本語の概要は準備中です。原文の説明を表示しています。
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Chart a too-big effort as a shared map of decision tickets on the Gaia headquarters issue tracker, then resolve them one at a time until the way to the destination is clear. Use when someone says: "this is too big for one session", "chart a map", "wayfinder map", "plan this effort", "what do we need to decide first", "open a wayfinder", "work the map", "what's on the frontier", or /wayfinder. Covers any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven and beyond — but every map and every ticket lives on ONE tracker: gaia-research/gaia-skill-tree. This is cartography (planning an effort as decisions), NOT triage of an existing backlog — for that use /gaia-triage.
日本語の概要は準備中です。原文の説明を表示しています。
Ask Daniel a blocking decision as options with a recommendation and honest pros/cons, rather than prose. Use whenever work is blocked on a judgment call, a product decision, an approval, or a choice between approaches — instead of writing "let me know which you prefer" at the end of a message.
日本語の概要は準備中です。原文の説明を表示しています。
Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire or the AI annex buyers now attach to it, executing sales sequences, coaching qualification, or deciding what the website's AI chat agent is allowed to say. Also triggers on: outbound, cold outreach, reply handling, reply classification, out-of-office replies, auto-replies counted as replies, our reply rate is inflated, prospect replied remove me, opt-out by reply, is this list ready to send, launch readiness, CRM segment outbound, we emailed a current customer, outbound hit an open opportunity, ownerless leads, prospects engaging our competitors, competitor connections, displacement list, is this personalization creepy, can we mention they visited our site, signal freshness, deal strategy, pipeline, battle card, objection handling, common objections, why do we keep hearing this objection, mine call transcripts for objections, objection register, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, AI security questionnaire, AI annex, AI vendor due diligence, the buyer is asking if we train on their data, do you train on customer data, which model do you use, model provider sub-processor, AI subprocessor disclosure, where does inference run, can the customer turn the AI feature off, AI-CAIQ, CSA AI Controls Matrix, ISO 42001, ISO/IEC 42001, NIST AI RMF, EU AI Act Article 50, are we a provider or a deployer, AI feature disclosure, our model vendor changed and nobody told the buyer, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss, website chatbot, chat widget, AI chat agent, AI SDR, inbound AI SDR, conversational marketing, live chat, what should our chatbot be allowed to say, our chatbot quoted the wrong price, the bot promised a discount, do we have to disclose it is AI, EU AI Act chatbot disclosure, chatbot handoff to sales, chat transcript review, prompt injection on our chatbot, Drift, Qualified, Intercom.
日本語の概要は準備中です。原文の説明を表示しています。
Unity data-driven design architecture. ScriptableObject config hierarchies, JSON data pipelines, designer handoff workflows, data versioning and migration, Inspector attributes for self-documenting configs. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.
日本語の概要は準備中です。原文の説明を表示しています。
Unity save/load system architecture. Serialization format selection, save data DTOs, versioning and migration, cloud sync, PlayerPrefs scoping, auto-save strategies, mobile persistence. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.
日本語の概要は準備中です。原文の説明を表示しています。