「decisions」の検索結果

Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.

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

OpenStack capacity planning operations skill for resource planning, quota management, and scaling decisions. Covers compute capacity (allocation ratios, vCPU/RAM utilization, host aggregates, availability zones), storage capacity (Cinder pool sizing, thin provisioning, Glance storage, Swift rings), network capacity (floating IP pools, port quotas, subnet sizing), project quota management (templates for small/medium/large profiles), flavor sizing strategy, utilization analysis with placement service, growth forecasting from historical metrics, and right-sizing recommendations for underutilized resources.

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

Identify and annotate cloud cost implications of architectural decisions. Use when reviewing infrastructure changes or designing new services.

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

Records hypotheses, evidence and decisions when proposing, running or evaluating forecast experiments, including backtests and feature or model comparisons. Excludes routine tests and unchanged forecast operation.

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

Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.

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

Use when facing unknowns, debugging without a clear cause, or making architecture decisions — enforces hypothesis-driven scientific reasoning through observation, hypothesis formulation, prediction, experiment design, and evidence-based conclusion. Use when previous attempts have failed or the problem space involves uncertainty.

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

Define and develop plugin mission statements — purpose, values, anti-patterns, and trade-offs. Use when creating a new plugin, auditing an existing plugin's alignment, or providing a reference for the alignment check loop to evaluate decisions against. Produces mission.json with [draft] status and writes an interview file for the human to refine it.

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

Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.

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

Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.

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

Design validation and maintained regression protection before test authoring. Use for TDD increments, acceptance or regression evidence, test boundary/oracle decisions, and multi-factor interaction coverage.

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

Look up prior Claude Code sessions when context is lost or forgotten. Use when asked what was done before, what happened in the last session, or any request to recall past conversation history, prior decisions, experiments, or outcomes. Indexes and searches raw JSONL transcripts from ~/.claude/projects/ via DuckDB. Returns verbatim user messages, summarizes AI actions and sub-agent outcomes, detects tool errors and user frustration signals, and reports tool usage statistics. Summaries cached at ~/.claude/kaizen/session-summaries/.

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

Turns raw captures (dictated braindumps in a deliverable's inbox/, or recent macwhspr dictation-log entries) into proposed planning-wiki changes, shown as one unified diff. Classifies each statement as a decision, evidence claim, question, task, or dropped item, traces it to its capture paragraph, tags unconfirmed names, numbers, and citations UNRESOLVED, and writes decisions only with the author's assent. Edits only the planning wiki, never source files. Use when asked to intake, absorb notes, or process the inbox, or after dictating notes from a talk, meeting, or reading session.

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

Interviews a researcher in rounds until an idea, design, or draft has no unexamined decision — numbered questions, each with why it matters and a recommended answer, facts looked up rather than asked, and settled decisions written to a file. Stages are idea (topic or hunch to a falsifiable question and contribution claim), design (estimand, identification, sample and power, measurement, analysis plan, pre-registration, venue), and defend (reviewer objections to a finished design or draft). Use when the user says "grill me", asks to stress-test or poke holes in an idea, design, or plan, asks what they are assuming, or brings an idea that is not yet a design. --plan grills software or process plans.

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

Plans a research project as a decision map that persists across sessions, resolving one ticket per session until the design is defensible and pre-registerable. The map lives as Markdown in the repository, literature sweeps run as parallel research tickets, and the resolved map compiles into a pre-analysis plan. Use at project start, when a design has more open decisions than one conversation can hold, or when planning restarts each session. Not for executing analyses or writing the paper.

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

Plans a research project as a durable decision map, resolving one design decision per session until the design is defensible and pre-registerable. Use at project start, when a design has more open decisions than one conversation holds, or when planning keeps restarting. Not for running analyses or writing the paper.

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

Turns dictated captures in a deliverable's inbox/ into a proposed planning-wiki diff, classifying and tracing each statement; decisions need the author's assent. Use to intake notes or process the inbox.

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

Interviews a researcher in rounds (idea, design, or defend stage) until no decision in a research idea, design, or draft is left assumed, recommending an answer to each question and writing settled decisions to a file. Use for 'grill me', stress-testing a design, or an idea not yet a design; --plan for software or process plans.

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

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

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

Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.

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

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

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

ADI-cycle structured reasoning (Abduction-Deduction-Induction-Audit-Decide). Use for complex decisions when multiple hypotheses need to be considered.

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

Cross-verify Claude-generated plans and code using OpenAI Codex and Google Gemini CLI. Provides code review, plan validation, and comparative analysis. Use when needing second opinions on Claude's code or plans, validating technical decisions, or seeking consensus from multiple AI models.

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

Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.

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

Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.

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