@giwonn/claude-daily-review 0.3.1 → 0.3.4

package/.claude-plugin/marketplace.json

@@ -13,7 +13,7 @@
       "source": {
         "source": "url",
         "url": "https://github.com/giwonn/claude-daily-review.git",
-        "sha": "49946f8e9b47730b7f60938507f1c13ef362ae1e"
+        "sha": "5bb643e083c2447f7feabec1705e8c2865e0ebc6"
       },
       "description": "Auto-capture conversations for daily review and career documentation",
       "version": "0.3.0",

package/.github/workflows/release.yml

@@ -0,0 +1,69 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          TAG="${GITHUB_REF#refs/tags/}"
+          PREV_TAG=$(git describe --tags --abbrev=0 "${TAG}^" 2>/dev/null || echo "")
+          if [ -n "$PREV_TAG" ]; then
+            NOTES=$(git log --pretty=format:"- %s" "${PREV_TAG}..${TAG}" | grep -v '\[skip ci\]')
+          else
+            NOTES=$(git log --pretty=format:"- %s" "${TAG}" | head -20)
+          fi
+          gh release create "$TAG" --title "$TAG" --notes "$NOTES"
+
+  publish:
+    needs: release
+    runs-on: ubuntu-latest
+    environment: npm
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+          registry-url: "https://registry.npmjs.org"
+
+      - run: npm install -g npm@latest
+
+      - run: npm publish --access public --provenance
+
+  update-marketplace:
+    needs: release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: master
+
+      - name: Update SHA in marketplace.json
+        run: |
+          SHA=$(git rev-parse HEAD)
+          sed -i "s/\"sha\": \"[a-f0-9]*\"/\"sha\": \"$SHA\"/" .claude-plugin/marketplace.json
+          cat .claude-plugin/marketplace.json
+
+      - name: Commit and push
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git add .claude-plugin/marketplace.json
+          git diff --cached --quiet && echo "No changes" || (git commit -m "chore: update marketplace SHA [skip ci]" && git push)

package/README.ko.md

@@ -1,19 +1,19 @@
 # claude-daily-review
 
-Claude Code 플러그인으로, 대화 내용을 자동으로 캡처하여 Obsidian vault 또는 GitHub 저장소에 구조화된 일일 회고 마크다운 파일을 생성합니다.
+Claude Code 플러그인으로, 대화 내용을 자동으로 캡처하여 Obsidian vault 또는 GitHub 저장소에 구조화된 회고 마크다운 파일을 생성합니다.
 
-AI와 함께하는 일상 개발 업무를 경력 문서로 자동 변환하세요.
+AI와 함께하는 일상 개발 업무를 경력 문서로 변환하세요 — 원할 때 바로.
 
 ## 주요 기능
 
 - **자동 수집**: 훅 기반 대화 기록으로 수동 작업 제로
+- **온디맨드 회고 생성**: 원할 때 자연어로 회고 생성 (`/generate`)
+- **자연어 타겟팅**: "어제 회고", "1분기 요약", "my-app 프로젝트 3월 회고"
 - **구조화된 회고**: 프로젝트별 작업 요약, 배운 점, 의사결정, Q&A 정리
 - **계단식 요약**: 일간 → 주간 → 월간 → 분기 → 연간
-- **프로젝트 추적**: 이력서/경력기술서용 프로젝트별 누적 요약
 - **Obsidian 연동**: 태그와 링크가 포함된 마크다운 직접 출력
 - **GitHub 연동**: OAuth 인증으로 GitHub 저장소에 회고 저장
-- **동시성 안전**: 세션 격리 쓰기 + 지연 병합으로 데이터 무결성 보장
-- **강제종료 복구**: 강제 종료 시에도 원시 로그 보존
+- **강제종료 복구**: 세션 시작 시 트랜스크립트에서 누락 로그 자동 복구
 
 ## 설치
 
@@ -34,6 +34,29 @@ claude plugin add claude-daily-review
 2. 간단한 자기소개 (회사, 직무, 팀)
 3. 요약 주기 선택
 
+## 동작 원리
+
+```
+매 응답 완료       →  원시 로그 자동 저장 (비동기, 논블로킹)
+세션 시작          →  트랜스크립트에서 누락 로그 복구
+/generate          →  원시 로그를 기반으로 회고 생성
+```
+
+### 회고 생성
+
+`/generate`에 자연어로 원하는 범위를 지정할 수 있습니다:
+
+```
+/generate                              → 누락된 회고 전체 생성
+/generate 어제 회고 만들어줘             → 어제 일일 회고
+/generate 지난주 주간 회고               → 지난주 주간 요약
+/generate 1분기 회고                    → 1분기 분기 요약
+/generate my-app 프로젝트 3월 회고       → my-app만 필터한 3월 회고
+/generate 3월 1일~15일                  → 날짜 범위 일일 회고
+```
+
+인자 없이 실행하면 아직 생성되지 않은 회고를 모두 생성합니다 (증분 모드).
+
 ## GitHub 저장소
 
 GitHub를 저장소 백엔드로 선택하면, **OAuth Device Flow**로 인증합니다 — 개인 액세스 토큰이 필요 없습니다.
@@ -54,14 +77,6 @@ GitHub를 저장소 백엔드로 선택하면, **OAuth Device Flow**로 인증
 
 파일은 **GitHub Contents API**를 통해 읽고 쓰여집니다. 각 회고 파일은 마크다운 파일로 저장소에 직접 커밋되며, 로컬 저장소와 동일한 폴더 구조를 사용합니다. 로컬 git 설치가 필요 없습니다.
 
-## 동작 원리
-
-```
-매 응답 완료  →  원시 로그 저장 (비동기, 논블로킹)
-세션 종료     →  AI가 구조화된 회고 생성
-다음 세션     →  회고를 일일 파일에 병합 + 주기별 요약 생성
-```
-
 ## 폴더 구조
 
 ```

package/README.md

@@ -2,20 +2,20 @@
 
 [한국어](README.ko.md)
 
-Claude Code plugin that automatically captures your conversations and generates structured daily review markdown files in your Obsidian vault or GitHub repository.
+Claude Code plugin that automatically captures your conversations and generates structured review markdown files in your Obsidian vault or GitHub repository.
 
-Turn your daily AI-assisted development work into career documentation — automatically.
+Turn your daily AI-assisted development work into career documentation — on demand.
 
 ## Features
 
 - **Auto-capture**: Hook-based conversation logging with zero manual effort
+- **On-demand reviews**: Generate reviews when you want with natural language (`/generate`)
+- **Natural language targeting**: "yesterday's review", "Q1 summary", "my-app project March review"
 - **Structured reviews**: Work summaries, learnings, decisions, and Q&A organized by project
 - **Cascading summaries**: Daily → Weekly → Monthly → Quarterly → Yearly
-- **Project tracking**: Per-project summaries for resume/portfolio building
 - **Obsidian integration**: Direct markdown output with tags and links
 - **GitHub integration**: Store reviews in a GitHub repo with OAuth authentication
-- **Concurrency-safe**: Session-isolated writes with deferred merge
-- **Crash recovery**: Raw logs preserved even on force-quit
+- **Crash recovery**: Missing raw logs auto-recovered from transcripts on session start
 
 ## Installation
 
@@ -36,6 +36,29 @@ This will ask for:
 2. A brief professional profile (company, role, team)
 3. Which summary periods to enable
 
+## How It Works
+
+```
+Every response     →  Raw log saved automatically (async, non-blocking)
+Session start      →  Missing logs recovered from transcripts
+/generate          →  AI generates reviews from raw logs on demand
+```
+
+### Generating Reviews
+
+Use `/generate` with natural language to control what gets generated:
+
+```
+/generate                                → Generate all missing reviews
+/generate yesterday's review             → Daily review for yesterday
+/generate last week's weekly summary     → Weekly summary for last week
+/generate Q1 review                      → Quarterly summary for Q1
+/generate my-app project March review    → March review filtered to my-app
+/generate March 1-15                     → Daily reviews for date range
+```
+
+When no arguments are given, it generates all reviews that haven't been created yet (incremental mode).
+
 ## GitHub Storage
 
 When you choose GitHub as your storage backend, the plugin authenticates using the **OAuth Device Flow** — no personal access tokens required.
@@ -56,18 +79,10 @@ After authenticating, you can either:
 
 Files are read and written via the **GitHub Contents API**. Each review file is committed directly to the repository as a markdown file, using the same folder structure as local storage. No local git installation is required.
 
-## How It Works
-
-```
-Every response  →  Raw log saved (async, non-blocking)
-Session end     →  AI generates structured review
-Next session    →  Reviews merged into daily file + periodic summaries generated
-```
-
 ## Vault Structure
 
 ```
-vault/daily-review/
+daily-review/
 ├── daily/2026-03-28.md          ← Daily review (all projects)
 ├── weekly/2026-W13.md           ← Weekly summary
 ├── monthly/2026-03.md           ← Monthly summary
@@ -89,9 +104,10 @@ Config is stored at `$CLAUDE_PLUGIN_DATA/config.json`.
 {
   "storage": {
     "type": "local",
-    "vaultPath": "/path/to/obsidian/vault"
+    "local": {
+      "basePath": "/path/to/obsidian/vault/daily-review"
+    }
   },
-  "reviewFolder": "daily-review",
   "language": "ko",
   "periods": {
     "daily": true,
@@ -115,12 +131,13 @@ Config is stored at `$CLAUDE_PLUGIN_DATA/config.json`.
 {
   "storage": {
     "type": "github",
-    "owner": "your-github-username",
-    "repo": "daily-review",
-    "branch": "main",
-    "token": "<stored by OAuth flow>"
+    "github": {
+      "owner": "your-github-username",
+      "repo": "daily-review",
+      "token": "<stored by OAuth flow>",
+      "basePath": "daily-review"
+    }
   },
-  "reviewFolder": "daily-review",
   "language": "ko",
   "periods": {
     "daily": true,

package/commands/daily-review-setup.md

@@ -0,0 +1,238 @@
+---
+description: Configure the daily review plugin — set storage backend, user profile, and review periods
+allowed-tools: ["AskUserQuestion", "Read", "Write", "Bash"]
+---
+
+# Daily Review Setup
+
+You are setting up the claude-daily-review plugin for the user.
+
+## Important Rules
+
+- **NEVER show raw error messages, stack traces, or file paths to the user.** If a Bash command fails, interpret the error and explain it in plain Korean.
+- When a command fails, tell the user what went wrong and what to do next — not the technical details.
+- Example: Instead of showing "Error: GitHub auth timed out waiting for authorization" with a stack trace, say "GitHub 인증이 시간 초과되었습니다. 다시 시도해주세요."
+
+## Check Existing Config
+
+First, read `${CLAUDE_PLUGIN_DATA}/config.json` to see if a config already exists.
+
+If it **does not exist**, proceed to the full onboarding flow below.
+
+If it **exists**, show the current storage type and profile summary, then ask using AskUserQuestion:
+- question: "이미 설정이 되어 있습니다. 어떻게 할까요?"
+- options:
+  1. label: "현재 설정 유지", description: "변경 없이 그대로 사용합니다"
+  2. label: "저장소 변경", description: "다른 저장소로 변경합니다"
+  3. label: "프로필/주기 변경", description: "프로필이나 요약 주기만 변경합니다"
+  4. label: "처음부터 다시 설정", description: "모든 설정을 초기화합니다"
+
+- "현재 설정 유지": exit with "현재 설정을 유지합니다."
+- "저장소 변경": go to Step 0 (Storage Selection), keep existing profile/periods
+- "프로필/주기 변경": go to Step 2 (Profile), keep existing storage
+- "처음부터 다시 설정": delete existing config and proceed to full onboarding flow
+
+## Onboarding Flow
+
+### Step 0: Storage Selection
+
+Ask the user using AskUserQuestion:
+- question: "회고를 어디에 저장할까요?"
+- options:
+  1. label: "GitHub 저장소", description: "원격 저장소에 저장. 여러 PC에서 공유 가능"
+  2. label: "로컬 폴더", description: "Obsidian vault 등 로컬 디렉토리에 저장"
+
+#### Option 1: GitHub Storage
+
+**1a. Authenticate with GitHub OAuth Device Flow:**
+
+Run via Bash:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/lib/request-device-code.mjs"
+```
+
+Show the user:
+> "GitHub 인증이 필요합니다. 아래 링크를 브라우저에서 열고 코드를 입력해주세요."
+> - URL: https://github.com/login/device
+> - 코드: `{user_code}`
+
+Then poll for the token (pass the full device code response as JSON argument):
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/lib/poll-token.mjs" '{"device_code":"{device_code}","interval":{interval},"user_code":"{user_code}","verification_uri":"https://github.com/login/device","expires_in":900}'
+```
+
+Wait for the user to complete authorization. Store the returned token string.
+
+**1b. Select or create a repository:**
+
+Ask using AskUserQuestion:
+- question: "GitHub 저장소를 어떻게 할까요?"
+- options:
+  1. label: "새 저장소 만들기", description: "비공개 저장소를 자동 생성합니다"
+  2. label: "기존 저장소 사용", description: "이미 있는 저장소를 지정합니다"
+
+- **New:** Ask for a repo name. Create it via Bash:
+  ```bash
+  MSYS_NO_PATHCONV=1 gh api /user/repos -X POST -f name=<name> -f private=true
+  ```
+  If `gh` is not available, tell the user to create the repo at https://github.com/new and then provide the `owner/repo`.
+- **Existing:** Ask for the repository in `owner/repo` format. Parse into `owner` and `repo`.
+
+**1c. Check for shared config in repo:**
+
+After repo is selected/created, try to read the shared config:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/lib/storage-cli.mjs" read .config.json
+```
+
+If `.config.json` exists in the repo, parse it and **skip Steps 1-3** (Profile and Periods). Use the values from the shared config. Tell the user:
+> "이전에 저장된 설정을 찾았습니다! 프로필과 주기 설정을 자동으로 복원합니다."
+
+If `.config.json` does not exist, proceed to Step 2 (Profile).
+
+The local config will be:
+```json
+{
+  "storage": {
+    "type": "github",
+    "github": {
+      "owner": "<owner>",
+      "repo": "<repo>",
+      "token": "<access_token>",
+      "basePath": "daily-review"
+    }
+  }
+}
+```
+
+The profile/periods/language go into the **shared config** (saved in Step 4).
+
+After storage selection, proceed to Step 2 (Profile). Skip Step 1 (Vault Path) for GitHub storage.
+
+#### Option 2: Local Storage
+
+Proceed to Step 1 (Vault Path) below. The storage config will be:
+```json
+{
+  "storage": {
+    "type": "local",
+    "local": {
+      "basePath": "<path>/daily-review"
+    }
+  }
+}
+```
+
+### Step 1: Vault Path (Local storage only)
+
+Ask the user:
+> "Obsidian vault 경로를 알려주세요. (예: C:/Users/name/Documents/MyVault)"
+
+After they provide a path:
+- Verify the directory exists using the Bash tool: `test -d "{path}" && echo "OK" || echo "NOT_FOUND"`
+- If not found, ask them to check the path
+- Normalize the path (resolve ~, remove trailing slashes)
+- Set the `basePath` in the storage config to `{path}/daily-review`
+
+### Step 2: Profile
+
+Ask each profile field one at a time using AskUserQuestion.
+
+**회사명:**
+- question: "어떤 회사에서 일하고 계신가요?"
+- options:
+  1. label: "직접 입력", description: ""
+  2. label: "건너뛰기", description: "나중에 설정할 수 있습니다"
+- If "직접 입력" selected: ask "회사명을 입력해주세요" in the next message and wait for text response.
+- If "건너뛰기" selected: store as empty string.
+
+**역할/직무:**
+- question: "역할/직무가 뭔가요?"
+- options:
+  1. label: "직접 입력", description: "예: 프론트엔드 개발자"
+  2. label: "건너뛰기", description: "나중에 설정할 수 있습니다"
+
+**팀/도메인:**
+- question: "팀이나 담당 도메인이 있다면?"
+- options:
+  1. label: "직접 입력", description: "예: 결제플랫폼팀"
+  2. label: "건너뛰기", description: "나중에 설정할 수 있습니다"
+
+**하는 일 설명:**
+- question: "하고 계신 일을 한 줄로 설명하면?"
+- options:
+  1. label: "직접 입력", description: "예: B2B SaaS 결제 시스템 개발 및 운영"
+  2. label: "건너뛰기", description: "나중에 설정할 수 있습니다"
+
+### Step 3: Periods
+
+Ask using AskUserQuestion with multiSelect:
+- question: "어떤 주기로 회고를 요약할까요? (daily는 항상 활성화)"
+- multiSelect: true
+- options:
+  1. label: "weekly (주간)", description: "매주 요약"
+  2. label: "monthly (월간)", description: "매월 요약"
+  3. label: "quarterly (분기)", description: "분기별 요약"
+  4. label: "yearly (연간)", description: "연간 요약"
+
+Selected items are enabled. daily is always true.
+
+### Step 4: Save
+
+**Save local config** to `${CLAUDE_PLUGIN_DATA}/config.json` using the Write tool.
+
+For **local storage**, the config includes everything:
+```json
+{
+  "storage": { "type": "local", "local": { "basePath": "..." } },
+  "language": "ko",
+  "periods": { "daily": true, "weekly": true, "monthly": true, "quarterly": true, "yearly": false },
+  "profile": { "company": "...", "role": "...", "team": "...", "context": "..." }
+}
+```
+
+For **GitHub storage**, the local config only has storage credentials:
+```json
+{
+  "storage": { "type": "github", "github": { "owner": "...", "repo": "...", "token": "...", "basePath": "daily-review" } },
+  "language": "ko",
+  "periods": { "daily": true, "weekly": true, "monthly": true, "quarterly": true, "yearly": false },
+  "profile": { "company": "...", "role": "...", "team": "...", "context": "..." }
+}
+```
+
+Additionally, **save shared config to the repo** so other machines can restore it:
+```bash
+echo '<shared_config_json>' | node "${CLAUDE_PLUGIN_ROOT}/lib/storage-cli.mjs" write .config.json
+```
+
+The shared config contains only profile, periods, and language (NO storage credentials):
+```json
+{
+  "language": "ko",
+  "periods": { "daily": true, "weekly": true, "monthly": true, "quarterly": true, "yearly": false },
+  "profile": { "company": "...", "role": "...", "team": "...", "context": "..." }
+}
+```
+
+**If local storage:** Create the vault directories:
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/lib/create-dirs.mjs"
+```
+
+**If GitHub storage:** Skip directory creation.
+
+### Step 5: Confirm
+
+Tell the user:
+
+**For local storage:**
+> "설정 완료! 이제부터 대화 내용이 자동으로 기록됩니다."
+> "회고 파일은 `{basePath}/` 에서 확인하세요."
+> "설정을 변경하려면 `/daily-review-setup`을 다시 실행하세요."
+
+**For GitHub storage:**
+> "설정 완료! 이제부터 대화 내용이 자동으로 GitHub에 기록됩니다."
+> "회고 파일은 `https://github.com/{owner}/{repo}` 에서 확인하세요."
+> "설정을 변경하려면 `/daily-review-setup`을 다시 실행하세요."
+> "다른 PC에서도 GitHub 인증만 하면 설정이 자동으로 복원됩니다."

package/commands/generate.md

@@ -0,0 +1,195 @@
+---
+description: Generate reviews from raw conversation logs (supports natural language targeting)
+allowed-tools: ["Read", "Write", "Bash"]
+---
+
+# Generate Reviews
+
+## Important Rules
+
+- Write all review content in Korean.
+- **NEVER show raw error messages or file paths to the user.**
+- Use the user's profile to add business context.
+- Today's date: use the system date for resolving relative expressions.
+
+## Step 0: Interpret User Request
+
+The user may provide a natural language request as arguments. Parse their intent to determine:
+
+1. **Date scope** — which dates/periods to generate
+2. **Period type** — daily, weekly, monthly, quarterly, yearly (or all cascading)
+3. **Project filter** — specific project name (optional)
+4. **Force regeneration** — whether to regenerate already-generated reviews
+
+### Interpretation Examples
+
+| User input | from | to | force | Period type | Project |
+|---|---|---|---|---|---|
+| (empty) | - | - | no | all missing | all |
+| "어제 회고" | yesterday | yesterday | yes | daily | all |
+| "3월 15일 회고" | 2026-03-15 | 2026-03-15 | yes | daily | all |
+| "지난주 주간 회고" | (week start) | (week end) | yes | weekly | all |
+| "이번달 회고" | (month start) | today | yes | daily+monthly | all |
+| "1분기 회고" | Q1 start | Q1 end | yes | quarterly | all |
+| "my-app 프로젝트 3월 회고" | 03-01 | 03-31 | yes | daily+monthly | my-app |
+| "올해 회고 다시 만들어줘" | year start | today | yes | all cascade | all |
+| "3월 1일~15일" | 03-01 | 03-15 | yes | daily | all |
+
+**Rules:**
+- If the user specifies a specific date/period, set `force` to `yes` (they want it regenerated).
+- If no input is given, run in default mode (generate only missing reviews, no force).
+- For period types like "주간", "월간", "분기", "연간": generate the requested summary AND any prerequisite lower-level reviews needed as input.
+- When the user mentions a project name, generate reviews for all dates but only include logs from that project's cwd.
+
+## Step 1: Collect Data
+
+Based on Step 0 interpretation, build the command:
+
+```bash
+CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/lib/collect-raw-logs.mjs" [OPTIONS]
+```
+
+Options (all optional):
+- `--from YYYY-MM-DD` — start date filter
+- `--to YYYY-MM-DD` — end date filter
+- `--force` — include dates even if already generated
+
+If no options, runs in default incremental mode (only new logs since last generation).
+
+This outputs JSON with:
+- `profile`: user's company/role/team/context
+- `language`: review language
+- `needs.daily`: dates that need daily review generation
+- `needs.weekly`: weeks that need weekly summary
+- `needs.monthly`: months that need monthly summary
+- `needs.quarterly`: quarters that need quarterly summary
+- `needs.yearly`: years that need yearly summary
+- `logs`: raw conversation logs keyed by date
+
+If `needs` is all empty, tell the user "해당 기간에 생성할 회고가 없습니다." and stop.
+
+## Step 2: Apply Filters
+
+- **Project filter**: If the user requested a specific project, filter `logs[date]` entries to only include those where the last path segment of `cwd` matches the project name.
+- **Period type filter**: If the user only requested a specific period type (e.g., "주간 회고"), only generate that type and its prerequisites. For example, if weekly is requested, generate daily reviews first (as input), then the weekly summary.
+
+## Step 3: Generate Daily Reviews
+
+For each date in `needs.daily`:
+
+1. Take all log entries from `logs[date]`
+2. Group by `cwd` (last path segment = project name)
+3. For each project, analyze user/assistant pairs and extract:
+   - **작업 요약**: What was accomplished (use profile for business context)
+   - **배운 것**: New things learned
+   - **고민한 포인트**: Decisions and reasoning
+   - **질문과 답변**: Key Q&A (summarized)
+4. General questions go under "미분류"
+
+Write via:
+```bash
+echo '<content>' | CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/lib/storage-cli.mjs" write "daily/{date}.md"
+```
+
+Format:
+```markdown
+---
+date: {date}
+type: daily-review
+projects: [{names}]
+---
+
+# {date} Daily Review
+
+## [{project}] {title}
+**작업 요약:** {summary}
+**배운 것:**
+- {item}
+**고민한 포인트:**
+- {decision} → {choice} ({reason})
+**질문과 답변:**
+- Q: {question}
+  → A: {answer}
+
+## 미분류
+- Q: {question}
+  → A: {answer}
+```
+
+## Step 4: Generate Weekly Summaries
+
+For each week in `needs.weekly`:
+
+1. Read the daily reviews that belong to this week using:
+```bash
+CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/lib/storage-cli.mjs" read "daily/{date}.md"
+```
+2. Summarize into weekly review with:
+   - 주요 성과
+   - 기술 스택 활용
+   - 핵심 의사결정
+   - 성장 포인트
+
+Write to `weekly/{week}.md`.
+
+## Step 5: Generate Monthly Summaries
+
+For each month in `needs.monthly`:
+
+1. Read weekly reviews for that month (or daily reviews if weekly is empty)
+2. Summarize into monthly review with:
+   - 프로젝트별 진행 요약
+   - 이번 달 핵심 성장
+   - 기술 스택
+   - 주요 의사결정 기록
+
+Write to `monthly/{month}.md`.
+
+## Step 6: Generate Quarterly Summaries
+
+For each quarter in `needs.quarterly`:
+
+1. Read monthly reviews for that quarter
+2. Summarize with:
+   - 분기 성과 요약
+   - 핵심 역량 성장
+   - 기술 스택 총괄
+   - 경력기술서 하이라이트
+
+Write to `quarterly/{quarter}.md`.
+
+## Step 7: Generate Yearly Summaries
+
+For each year in `needs.yearly`:
+
+1. Read quarterly reviews for that year
+2. Summarize with:
+   - 연간 프로젝트 총괄
+   - 핵심 역량 맵
+   - 이력서용 요약
+   - 경력기술서용 상세
+
+Write to `yearly/{year}.md`.
+
+## Step 8: Update last-generated timestamp
+
+**Only update if running in default mode (no user-specified scope).**
+
+If the user requested a specific date/period/project, do NOT update `last-generated.json` — the incremental tracking should remain unchanged.
+
+If running in default mode, save the `newTimestamp` from Step 1:
+```bash
+echo '{"timestamp":"NEW_TIMESTAMP_VALUE"}' > "${CLAUDE_PLUGIN_DATA}/last-generated.json"
+```
+
+## Step 9: Report
+
+Tell the user what was generated:
+> "회고 생성 완료!"
+> - 일일 회고: {count}개
+> - 주간 요약: {count}개
+> - 월간 요약: {count}개
+> - 분기 요약: {count}개
+> - 연간 요약: {count}개
+
+Only show lines where count > 0.