Results for “decision-logging”

Record durable project decisions with rationale, alternatives, assumptions, status, and revisit triggers. Load when the user says record this decision, we decided, decision log, why did we choose, revisit this later, or capture architectural/process rationale.

Record decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

【非推奨 → ssot-record を使うこと】 ssot-record に統合済み。/record-decision が呼ばれた場合は ssot-record スキルに処理を委譲する。

Save the current diagnosis state to disk for cross-session recall, including conclusions, rejected directions, and next steps.

Structured logging strategy — levels, correlation IDs, context propagation, PII avoidance. Use when designing a logging approach, reviewing log statements, setting up log aggregation (ELK, Loki, CloudWatch), adding correlation IDs to a distributed system, or deciding what to log and what to keep out.

debug-logging

Creates and manages Architecture Decision Records using the Michael Nygard format, including new ADR creation, retrospective analysis, superseding, deprecating, and index generation.

Build ontology logs (ologs) from problem descriptions using categorical foundations. Use when designing problem taxonomies, classifying tasks for routing, building knowledge libraries, establishing formal analogies between domains via functor search, or translating between natural language and database schemas. NOT for OWL/RDF ontology work, query tuning, or graph modeling without functional-arrow discipline.

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

Reduce decision time and cognitive burden by limiting the number and complexity of simultaneous choices in user interfaces.

Query and filter Datadog logs from the shell using the Composio CLI. Run scoped log searches, pivot across services/environments, and export structured JSON for incident investigation and diagnostics.

Designs and reviews feedback loops for AI agents to ensure goals are machine-decidable, loops are damped, and human judgment is preserved.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.

Use when selecting a statistical test with AI consultation, when assumptions need checking against the actual data, when an analysis plan or decision log must be written before running anything, or when results need APA-style reporting with effect sizes.

当需要进入并维持高度专注的深度工作状态时

Write, review, and maintain architecture decision records with clear context, alternatives, consequences, and lifecycle governance. Use when a consequential technical decision must remain understandable.

Debugging is the scientific method under time pressure.

Query and filter Datadog logs from the shell using the Composio CLI. Run scoped log searches, pivot across services/environments, and export structured JSON for downstream agents instead of click-driving the Datadog UI.

Use when a study needs a preregistration or a frozen analysis plan, when confirmatory and exploratory analyses must be separated, or when every deviation from the registered plan must be logged before the result is reported.

当遇到令人情绪激动或陷入僵局的情境，需要跳出固有反应模式以做出更优决策时

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.

Diagnose Apex behavior with debug logs, structured production logging, and async job monitoring, replacing ad-hoc System.debug habits with durable, queryable observability.

Structure a hard business decision — frame the choice, score options against weighted criteria, run a pre-mortem and stress-test, and produce a recommendation + decision record for any active brand