「decision」の検索結果

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

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

Maintain stewardship protocol continuity and tool/personality boundaries. Use when a repo agent needs steward-mode threshold checks, self-model update decisions, delegation hygiene, boundary violation review, or handoff-safe continuity context without overclaiming steward personality.

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

Steward public stories about any work — creation ethics, application ethics, and maintenance of the story plus its disclosures (generated, drafted, curated, authored). Use when writing a public article, origin story, talk, README narrative, or showcase about how work was made; when publishing ethics and decisions; or when asked who generated vs curated a text. Do not use for ADRs, FAQs, skill citations, or marketing hype.

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

Use when creating a new project folder, starter pack, app scaffold, or agent-ready workspace — AGENTS.md, README, TASKS, DECISIONS, PROMPTS, an idempotent bootstrap script, and starter-pack modes.

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

Examine a plan, decision, belief, or problem through question rounds that explore assumptions, alternatives, and consequences before acting.

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

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

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

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

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

Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.

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

Use when Invoice-Downloader work involves mailbox batch tests, truth audit, regression validation, P0/P1/P2 decisions, packaged frontend acceptance, or clean reruns.

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

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.

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

Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.

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

Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in deepseek-harness; checks every new note for superseded active records, classifies implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.

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

Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment, automation, or irreversible action whose failure would matter; when the user asks for a quality gate, acceptance criteria, QA, completeness, validation, audit, evidence, preflight, release readiness, or a definition of done; or before claiming completion on medium- or high-risk work. Automatically decide whether a formal gate is warranted, derive task-specific pass/fail criteria, gather evidence, and block unsupported completion. Make sure to use this skill even when the user does not say "quality gate" if consequential work needs acceptance criteria or completion evidence. Skip formal gating for trivial, reversible, low-impact requests.

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

EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.

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

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

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

Prioritize vulnerability remediation using KEV-style exploitation context plus asset criticality. Use for CVE triage, patch order decisions, and remediation reporting.

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

Compare model candidates using weighted metrics and deterministic ranking outputs. Use for benchmark leaderboards and model promotion decisions.

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

Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.

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

GStack plan-tune method for calibrating how many questions to ask, autonomy level, stop conditions, and decision style for a workstream or user preference.

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

Durable categorized record-keeping for any predicate-enabled walk. Trigger when: - Classifying a step's output for recording (decision, finding, debt, feedback). - Promoting a scratch artifact to the ledger, to repo/docs, or to a category home (.ledger/tech-debt/, .ledger/process-feedback/). - Auditing whether a draft is structurally ready for its destination. - Running a zero-context sensibility read before committing to promotion. - Recording a known limitation as a tech-debt entry (not prose in the log). - Recording a friction, miss, improvement, or process amendment. - Prompt contains: /record, record-keeping, promote, ledger note, zettelkasten, scratch-to-ledger, zero-context read, over-strip, classification trigger, tech-debt, process-feedback, amendment.

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

Before creating a GitHub issue or epic, search for an existing related one and force a reuse / replace / new decision — so the issue-first flow can't silently mint a duplicate. The create-time half of the dedup gate (the pickup-time half is /issue-sanity-check). Use whenever you're about to open an issue/epic, or run /issue-dedup. Backed by a hard PreToolUse hook on issue_write create.

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

Emit a blocking question the owner can read in ~10 seconds and answer in one reply — the scannable, recommendation-first handoff every agent posts when it hits a fork it can't own. Leads with the one decision + a recommendation, carries the 🤖 provenance header, doubles as the

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

Capture a POC's signed-off behaviour into its spec ledger (`<poc>/spec.json`) — the structured, walkable behaviour contract graduation freezes as authoritative. Run at the moment a behaviour gets signed off ("ok, this works"), while it's fresh — the same trigger as the HANDOFF.md update, but capturing the *behaviour as a testable entry* rather than the *decision as prose*. Use when a POC behaviour is approved, or asked to "capture this spec", "write the spec entry", "log this to the ledger".

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

Decision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.

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