Skip to content

hoavdc/CodexKit / skills/codexkit-decision-log

codexkit-decision-log

Unverified

Record and track organizational decisions using the RAPID framework. Captures decision context, options analysis, RAPID roles, risk assessment, and communication plan. Use when making cross-functional decisions, documenting governance choices, or building an auditable decision trail.

Decision Log

When to Use

  • When a decision affects multiple teams or has lasting consequences
  • When leadership needs an auditable trail of why choices were made
  • When recurring decisions need a consistent framework
  • When decisions stall due to unclear ownership or roles

Procedure

Step 1 — Frame the Decision

ElementDescription
Decision IDDEC-YYYY-NNN
TitleOne-line description
CategoryStrategic / Tactical / Operational
UrgencyCritical (24h) / High (1 week) / Normal (2 weeks) / Low
ReversibilityEasy / Moderate / Difficult / Irreversible
ScopeWho and what is affected

Step 2 — RAPID Roles

Assign clear decision roles:

RolePersonResponsibility
R — Recommend[Name]Researches, proposes recommendation
A — Agree[Names]Must agree before approval (has veto)
P — Perform[Names]Implements the decision
I — Input[Names]Provides data/perspective (no veto)
D — Decide[Name]Makes the final call (ONE person)

Rule: Exactly one D. Multiple A/P/I are fine.

Step 3 — Options Analysis

CriterionOption AOption BOption C (Status Quo)
Cost$50K$30K$0
Time to implement3 months6 months—
RiskLowMediumHigh (doing nothing)
Alignment with strategyHighMediumLow

Step 4 — Risk Assessment

OptionRiskProbabilityImpactMitigation
AVendor lock-inMediumHighContractual exit clause
BTeam capacityHighMediumPhase rollout

Step 5 — Decision Record

Decision: We will proceed with Option A
Rationale: Best alignment with strategy, acceptable cost, low risk
Trade-offs accepted: Higher cost than Option B
Conditions: Must complete vendor contract review by [date]
Review date: [6 months from now]

Step 6 — Communication Plan

AudienceChannelTimingMessage
LeadershipEmail summaryDay 1Decision + rationale
Affected teamsTeam meetingDay 2Impact + timeline
Broader orgSlack / NewsletterDay 5High-level announcement

Inputs

InputRequiredFormat
Decision topicYesWhat is being decided
OptionsYesAt least 2 including status quo
StakeholdersYesWho is affected / involved
ConstraintsRecommendedTimeline, budget, dependencies

Output

## Decision Record — DEC-2024-012

### Migrate Primary Database to PostgreSQL
**Status:** Accepted | **Date:** 2024-03-15
**Decided by:** CTO | **Recommended by:** Platform Lead

### RAPID
[Roles table]

### Options Considered
[Comparison matrix]

### Decision
We will migrate to PostgreSQL 16 managed on AWS RDS.

### Rationale
- Team expertise (8/10 engineers proficient)
- 40% cost reduction vs current Oracle license
- Acceptable migration risk with phased approach

### Communication Plan
[Audience → Channel → Timing table]

Definition of Done

  • Decision clearly framed with category and urgency
  • RAPID roles assigned (exactly one D)
  • Options compared including status quo
  • Risks identified per option
  • Decision recorded with rationale
  • Communication plan defined

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 192kUpdated Claude CodeCodexVerifiedInstall