skills.rest
sicambria
sicambriaCOMMUNITY
Explore all skills by this author →
GitHub

decide

Writes dated decision records and logs decision events to an observability log.

Updated Jun 28, 2026
Search Tags:#retrospective#observability#governance#audit trail#decision log#gate override#markdown record
One-click install
npx skills add https://github.com/sicambria/talkteach-asr --skill decide-sicambria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decide
Source: https://github.com/sicambria/talkteach-asr/tree/main/.claude/skills/decide
Command: npx skills add https://github.com/sicambria/talkteach-asr --skill decide-sicambria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decisions made during development — gate overrides, scope cuts, architectural calls — often go unrecorded, leaving future sessions unable to tell whether a choice was deliberate or accidental. This Skill makes every non-obvious decision auditable by writing a dated record and logging a traceable event. ## Core Features & Use Cases - Dated decision records: Writes a structured Markdown file under .harness/archive/decisions/ with context, options considered, the decision, and rationale. - Observability event logging: Appends a decision event via .harness/scripts/ops/events.mjs so dashboards and retrospectives can surface it. - Gate override auditing: Enforces the "Overrides are audited, never silent" invariant by requiring a paper trail for any guardrail bypass. - Use Case: After overriding a branch-protection gate to hotfix a release, invoke this Skill to record why the override was justified, which gate was bypassed, and link the evidence for later review. ## Quick Start Ask the AI to log a decision recording why a specific gate was overridden, including the context, options considered, and rationale.

Frequently Asked Questions about decide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log an auditable decision in a repository?▼

Invoke the decide skill with a summary, context, options considered, and rationale. It writes a dated Markdown file under .harness/archive/decisions/ and appends a decision event to the observability log via events.mjs.

When should I record a decision versus just committing code?▼

Record a decision for gate overrides, scope cuts, deferrals, or non-obvious architectural calls that future sessions need to understand. Routine implementation choices that don't need a standing record should not be logged.

What format does the decision record file use?▼

The record is a Markdown file named with a date and kebab-case slug, containing sections for context, options considered, the decision, rationale, and related path or line citations.

What happens if the event logging script fails?▼

The events.mjs script never throws on a bad write. If logging fails, the Markdown record is still kept because the record file is the source of truth and the event is only an index over it.

Can decision records be committed directly on the default branch?▼

Yes. The .harness/archive/ path is exempt from branch guards via the branchGuard.exemptPaths configuration, so decision records commit directly on the default branch per the repository's invariants.

Related Skills

Explore More Software Engineering Skills→
em-jonesem-jones
1

write-adr

Generate Architecture Decision Records documenting context, options, and outcomes.

Community
Basic
doffskiiidoffskiii
33

reflect

Analyze daily tasks, session notes, and calendar events to generate structured reflections.

Community
Intermediate
LucasMalessaLucasMalessa

ring:using-ring

Enforce orchestrator protocols and skill discovery before direct tool use.

Community
Advanced
gongye19gongye19

git-workflow

Enforce Git workflow best practices for commits, branches, and pull requests.

Community
Intermediate