「decisions」の検索結果

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

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

Print your own north-star row from your own record, and nothing else. Reads .claude/harness/decision-log.md, the canvas and the hook logs in this project; prints one line (decisions before the first source file, of which citing outside evidence, kills before code, sessions). Sends nothing anywhere. Opt-in; paste the line where you like or not at all.

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

Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.

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

Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.

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

Apply whenever writing or updating a project-facing document — root CLAUDE.md, `.hedgehog/core-design.md`, specs, READMEs, or similar. Ensures the file reads as a clean, current, as-is snapshot rather than a log of edits or decisions. Applies on first generation and on every later revision, including "update," "rewrite," or "clean up" requests.

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

Use at the start of any session on a project with a build graph (`.hedgehog/hedgehog.db`), and again at every claim/dispatch/verify cycle within it. Owns consuming the build graph — claiming task packets, delegating each to the layer's agent, running `hedgehog verify` to gate the commit, recording debt and decisions, the intent check at an intent's last layer, and when to clear context. Not for a build agent handed an already-claimed packet — that agent never claims, dispatches, or verifies; this skill is the orchestrating session's own.

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

Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.

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

Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through", "explore X with me", "help me plan Y", or "walk me through my thinking on Z" when the user wants a guided conversation rather than a direct answer. Applies broadly — career decisions, project ideas, product direction, personal goals, research questions, team problems — not just technical topics.

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

Compares build vs buy alternatives with risk-adjusted returns, time-to-value, and execution probability assessment. Use when evaluating growth strategies, comparing M&A vs organic investment, or analyzing make-vs-buy decisions.

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

Structures best execution monitoring with venue analysis, systematic internalization assessment, and regulatory compliance documentation. Use when managing best execution, documenting execution decisions, or conducting venue analysis.

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

Evaluates bridge round scenarios with insider dynamics, signal risk, and term structuring for existing portfolio companies. Use when considering bridge financing, structuring insider rounds, or analyzing pay-to-play provisions.

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

Creates VC IC presentation materials with deal thesis, market analysis, team assessment, competitive landscape, and return scenarios. Use when preparing IC memos, presenting investment opportunities, or documenting investment decisions.

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

Structures credit committee packages with borrower analysis, risk assessment, structuring proposal, and recommendation documentation. Use when preparing credit committee materials, presenting loan opportunities, or documenting credit decisions.

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

Evaluates vertical integration decisions with make-vs-buy analysis, supply chain control benefits, and margin capture opportunity assessment. Use when analyzing vertical integration, evaluating supply chain strategy, or assessing integration economics.

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

Evaluates regulatory decision impact with approval probability, timeline analysis, and outcome scenario modeling for event-driven positions. Use when analyzing regulatory events, evaluating FDA/FCC/DOJ decisions, or modeling regulatory outcomes.

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

Evaluates fairness opinion methodologies across DCF, trading comps, and precedent transactions for board-level decisions. Use when reviewing fairness opinions, preparing board materials, or analyzing transaction fairness.

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

Semantic search over global agent memory. Use to retrieve previously learned patterns, decisions, gotchas, and workarounds. Prevents stale-context errors across long sessions and multi-agent pipelines.

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

N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.

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

Architecture review and design validation. Evaluates system designs against best practices, identifies anti-patterns, and ensures architectural decisions align with non-functional requirements.

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

End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a travel day hour by hour, fill a spare block of time ("I'm near X with 2 free hours"), turn a finished plan into a designed page (eight themed renders: illustrated / clay / noir / glass / journal / zine / splash / portal — 插画/黏土/夜航/玻璃/手账/Zine/闪屏/穿越版), or asks 旅行规划/行程安排/机票比价/去某国玩N天怎么安排/现在有空档干嘛/把行程做成好看的网页 — even if they only mention one piece (just flights, just hotels, or just navigation), the playbook and verification rules here still apply.

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

Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)

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

Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search

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

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.

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

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", "리스크 분석", "위험 분석".

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