「decision」の検索結果

7 agentic design patterns with decision tree for choosing the right pattern for each agent type

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

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

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

Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.

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

Use when the user needs to WRITE a marketing report someone else will read — a one-page weekly for a CEO, a full monthly, or a quarterly strategy report with TL;DR, results versus target, insight, decisions needed, and next actions with owners. Trigger on 'marketing report', 'monthly report', 'weekly update for my boss', 'report for the client', 'quarterly summary', 'turn these numbers into a report'. Also use when the user says a stakeholder is asking how marketing is doing. Not for — diagnosing why the numbers are bad, see `03-performance-eval-global`; turning a raw export into insight, see `13-data-analysis-global`; a closed campaign retrospective, see `63-campaign-retrospective-global`.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Map a large, unclear, multi-session effort as linked decisions, then advance the map until the route to the destination is clear.

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

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

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

Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Coordinate nontrivial work in the ctx repository when a task has independent investigation, implementation, or test lanes; compute-heavy checks; or repetitive changes suited to scripts or codemods. Use for decomposition and concurrency decisions, not simple edits or questions.

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

Clarify domain concepts, language, boundaries, and durable architectural decisions. Use when terminology is ambiguous, the user is shaping a domain model, or a design depends on resolving what concepts mean.

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

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

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

Optimize React rendering, bundle size, and data flow with profiler-led decisions. Use when reducing re-renders, fixing waterfalls, or deciding whether memoization is warranted in React.

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

Controls authorized cybersecurity exercises through inject scheduling, safety gates, stop and restart decisions, communications, and synthetic-data boundaries. Use when serving as exercise control or white-team coordinator, not as compliance assessor or whitehat operator.

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

Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only.

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

Document tested Elixir APIs; may update README/ADRs. Not for docs lookup, audits/reviews, or standalone decisions.

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

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.

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

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.

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

The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.

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

This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.

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

Create and manage todo tracking documents for features, bugs, and multi-step tasks. Use when starting new work that benefits from a persistent record of decisions, progress, and context.

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

Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Agents should invoke this skill for academic or technical papers, arXiv/PubMed/IEEE/ACM links, PDFs, methodology review, limitations, practical implications, or extracting findings for engineering decisions.

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