analysis-dr

/analysis-dr

Manage Analysis Decision Records — the team's append-only log of methodology decisions.

Subcommands: new | scan | list | show {NNN}

Instructions

Step 1: Parse subcommand

Read $ARGUMENTS:

• new or no argument → write a new DR (go to Step 2a)
• scan → scan analyses for DR candidates (go to Step 2b)
• list → display the DR index (go to Step 2c)
• show {NNN} → display a specific DR (go to Step 2d)

If argument is ambiguous, default to new.

---

Step 2a: New DR

Goal: Help the user write a well-formed DR, or propose one based on current context.

Step 2a-1: Load context

Read these files to understand what might need a DR right now:

• .analysis/config.md — current metrics, team context
• .analysis/status.md — active analyses
• For each active analysis folder, read its most recent stage file (e.g., 03_investigate.md if at INVESTIGATE)
• analyses/decisions/INDEX.md — existing DRs (to avoid duplicates)

Step 2a-2: Check for decision signals

Look for signals that a decision was made or is being debated:

• Metric being defined or redefined in the current analysis
• Statistical method chosen (A/B test, regression, etc.)
• Segment or time window that was argued about
• Model algorithm that was selected over alternatives

If strong signals found, propose a DR draft:

📋 DR 초안 제안

분석에서 다음 결정이 발견됐어요. DR로 기록하면 좋을 것 같아요:

유형: {Metric | Methodology | Scope | Model | Principle}
제목 초안: "{결정 제목}"
결정 내용: "{한 문장 초안}"

이대로 작성할까요, 아니면 직접 내용을 알려주세요?

If no strong signals, ask the user:

어떤 결정을 DR로 남기고 싶으세요?
유형을 알려주시면 해당 템플릿으로 안내해드릴게요:
  Metric — 지표 정의
  Methodology — 분석 방법론
  Scope — 세그먼트/기간 범위
  Model — 모델/알고리즘 선택
  Principle — 분석 원칙

Step 2a-3: Determine next DR number

Read analyses/decisions/INDEX.md. Count existing DRs and increment by 1 (e.g., if DR-005 is last → new DR is DR-006). If INDEX.md doesn't exist yet, start with DR-001.

Step 2a-4: Write the DR

Collect or confirm these fields with the user:

• 결정: one sentence, what was decided
• 배경: what triggered this decision
• 근거: why this choice, what alternatives were rejected
• 트레이드오프: what costs are accepted
• 검토 트리거: when to reconsider
• 참고 분석: analysis folder path (optional)