「decision」の検索結果

Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.

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

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.

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

Organic story anatomy from John Truby's The Anatomy of Story (有机结构/设计原则/22步骤/道德议题/四角对立/幽灵/场景编排) — the designing principle (story process plus original execution), the seven key steps as the organic spine, all twenty-two steps with the middle-act machinery the beat sheets lack (ghost, fake-ally opponent, plan, opponent's drive, ally's attack, fake defeat, three revelation-and-decision pairs, audience revelation, visit to death, moral decision), four-corner opposition, the moral-argument chain with the hero-opponent power-balance rule, scene weave with structure-step tags and storyline numbers, and the accordion rule (never fewer than seven steps). Kept side by side with the Field/Snyder page maps. Use when the middle act sags into unconnected episodes, when the premise works but the story feels mechanical, when one antagonist cannot carry the theme, when the theme stays stated instead of acted, or when a BS2 board needs an organic second pass.

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

Distill the current conversation into a structured note (decisions made, open questions, file pointers with line numbers, next 1–3 actions) and save to `quality_reports/session_logs/` before auto-compression. Differs from `/checkpoint` (explicit stop-point snapshot) and from auto-compaction (which truncates rather than distills). Use when context is approaching auto-compact threshold, when a long pipeline has accumulated many decisions, or when the user says "compress", "distil this session", "before we hit auto-compact", "structured handoff before context resets".

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

Add a Jev-powered decision and release gate after an office assistant generates a report, proposal, spreadsheet, document, or slide deck. Use for claim-to-evidence checks, narrow requirement decisions, risk triage, and human-review routing; do not use it to generate the deliverable or claim that Jev browsed or verified a URL.

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

Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.

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

Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential, sigmoid, quadratic — considerations, and action evaluators), plus hybrid BT-drives-Utility agents. Use when implementing a reusable behavior-tree or utility-based decision system, or tuning enemy/NPC decisions beyond a simple FSM, or when the user mentions behavior tree, blackboard, decorator, selector, sequence, tick status, utility AI, response/scoring curve, or consideration. For choosing between FSM/BT/steering or for pathfinding, use game-ai; for Unreal's BehaviorTree/Blackboard assets, use unreal-behavior-trees.

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

Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.

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

Decode a counteroffer after you resign — what the raise, promotion promise, or title bump really signals, the statistics-informed risks of staying, and a clear-eyed decision framework. Use when asked my company countered my resignation, should I accept a counteroffer, they offered me more to stay, or decode this retention offer. Produces a component-by-component decode with 🔴🟡🟢 severity, the questions that expose which promises are real, and the stay/go decision sheet.

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

Write a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations, and a recommendation or the decision sought — scannable in two minutes.

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

Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.

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

Convert a meeting into async work that actually decides — the doc-plus-deadline format that replaces the room, the comment-window rules, the decision-closure step that async usually fumbles, and the honest test for what still needs synchronous. Use when asked can this meeting be async, replace our status meeting with a doc, run this decision without a call, or async isn't working for us. Produces the conversion design, the async artifact format, the closure protocol, and the still-needs-a-room list.

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

Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeting minutes for a board, or a formal record of decisions and actions. Produces structured board minutes with attendees, agenda items, resolutions, decisions, action register, and approval-ready wording.

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

Run a club, PTA, or association AGM that finishes on time and holds up later — the notice and agenda done right, a quorum plan, minutes that capture decisions not conversations, elections without awkwardness, and the follow-up that makes decisions real. Use when a volunteer says 'I have to run the AGM', 'what goes in the agenda', 'nobody comes to our meetings', or 'our elections are a mess'. Produces the notice, agenda, chair's script, minutes template, and quorum rescue plan.

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

Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.

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

Help users master the art of making high-stakes, irreversible decisions by using structured frameworks to reduce cognitive bias and maintain organizational momentum.

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

Audit the choices an implementing agent made, not its diff — a pure decision audit that traces the session's history into a choices ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it. Use when the user wants to review the decisions the AI made on their behalf, before merging or committing AI-implemented work, when integrating a delegated subagent's pass, or when a fix "works" but might be a point fix.

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

Use when the user asks what they are not seeing, what they forgot, what could go wrong, or what an expert would say about a plan, decision, document, code change, or setup they already have. Triggers: "what am I missing", "what don't I know", "poke holes in this", "what would an expert ask", "что я упускаю", "что я не вижу", or /clueless-blindspots. One-shot review; does not change the always-on level.

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

Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer work, or when the user invokes $add. Over-register freely; the developer drops with "drop A", "drop A,C", or "drop all".

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

Use when articulating why an Agricultural Systems (AgSy) result matters — its relevance for farm design, management, decision support, or policy. AgSy values systems analysis that informs a decision, so this is what separates an AgSy paper from a methods demo. It frames implications honestly within the model's scope; it does not over-claim or invent impact.

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

Use when writing the response to an Agricultural Systems (AgSy) revision decision. AgSy review is single anonymized with at least two expert systems reviewers and an editor decision, and revisions often turn on model evaluation, sensitivity/uncertainty, and trade-off framing. The response must convert each reviewer without alienating the editor. Structures the response letter; it does not fabricate new results.

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

Use when you need to understand the Academy of Management Review (AMR) developmental, multi-round review and interpret a decision letter focused on theoretical novelty and logical soundness. Explains the process and decision types; it does NOT draft the response document (that is amr-rebuttal).

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

Use when running the final pre-submission preflight for an Accounting, Organizations and Society (AOS) manuscript — Editorial Manager files (anonymized manuscript, separate title page, declarations), Elsevier policies (competing interests, AI, ethics), and open-access decisions. Checks readiness to submit; it does not handle the post-decision response (aos-rebuttal).

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

Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (amj-rebuttal).

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