Post Release Followup

---
name: post-release-followup
description: Analyze release workflow findings and recommend follow-up actions — execute immediately or register as issues
scope: harness
user-invocable: false
effort: medium
---

# Post-Release Follow-up

## Purpose

After PR creation in the auto-dev release workflow, collect unaddressed findings and present actionable follow-up recommendations. Genuine defects and process gaps are registered as GitHub issues automatically (no user confirmation needed). Only code-changing "immediate action" items require user confirmation.

## Workflow

### 1. Collect Follow-up Candidates

Gather unfinished work from multiple sources:

**Source A — Remaining open issues**:
- Run: `gh issue list --label triage-complete --state open --json number,title,labels`
- These are triaged issues NOT included in the current release

**Source B — Deep-verify findings**:
- Read the latest deep-verify output from `.claude/outputs/sessions/{today}/`

### Tool: Writing artifacts under .claude/outputs/

Under `mode: "bypassPermissions"`, subagents write directly to `.claude/outputs/sessions/` with the Write tool — direct `.claude/**` writes are permitted (CC v2.1.121+, #1101). No `/tmp` staging or script wrapping is needed. Read-only Bash on `.claude/outputs/` (e.g., `cat`, `head`, `wc`) is allowed for verification.

Reference: R006/R010 sensitive-path handling (direct `.claude/**` write under bypassPermissions), #1101.

- Extract any MEDIUM or LOW severity findings that were flagged but not fixed

**Source C — Triage deferred items**:
- Read the latest professor-triage output from `.claude/outputs/sessions/{today}/`
- Extract items explicitly marked as deferred or P3

**Source D — TODO markers in changed files**:
- Run: `git diff develop...HEAD --name-only` to get changed files
- Search changed files for `TODO`, `FIXME`, `HACK` markers added in this release

**Source E — PR review feedback**:
- Run: `gh api repos/{owner}/{repo}/pulls/{pr_number}/comments` and `gh api repos/{owner}/{repo}/issues/{pr_number}/comments`
- Parse omc_pr_analyzer bot comments (Senior Architect, Project Colleague, Professor Synthesis)
- Extract findings categorized as Critical, High, Medium
- Identify: required fixes, recommended improvements, structural concerns

### 2. Deduplicate and Categorize

Remove duplicates (same issue referenced from multiple sources). Categorize:

| Category | Criteria | Default Action |
|----------|----------|----------------|
| **즉시 실행** | P1/P2 잔여 이슈, MEDIUM+ 검증 발견사항, Critical/High PR 리뷰 발견사항 | 즉시 실행 |
| **이슈 등록** | P3 이슈, LOW 검증 발견사항, 새 TODO, Medium PR 리뷰 발견사항 | 이슈로 등록 |
| **참고** | 이미 추적 중인 이슈, 외관 관련 메모 | 건너뛰기 |

### Auto-Register Genuine Defects (no-ask)

**Before presenting the summary to the user**, auto-register all "이슈 등록" category items that are genuine defects or process gaps. No user confirmation is required for these.

**Definition — auto-register if ANY of:**
- Genuine defect: a bug, regression, broken behavior, or incorrect output observed during verification
- Process gap: a workflow hole, missing guard, or coverage gap surfaced by deep-verify / triage
- Coverage gap: a missing test, missing documentation, or missing automation for a known scenario

**Definition — do NOT auto-register (keep for user choice):**
- Pure cosmetic / style preference notes
- Items that are purely subjective or opinion-based

**When ambiguous, lean toward registering.** Registering a borderline item costs nothing; missing a genuine defect costs a future session.

**How to auto-register:**
```bash
gh issue create \
  --title "{간결한 설명}" \
  --body "## 출처\n\nv{version} 릴리즈 워크플로우에서 자동 등록.\n\n## 컨텍스트\n\n{상세 컨텍스트}\n\n## 권장 조치\n\n{권장 사항}" \
  --label "professor"
```

**이슈 본문의 코드 위치 표기 — 행 번호 대신 앵커 (#1652 #3-2)**: `## 컨텍스트`에서 코드 위치는 행
번호가 아니라 **함수명·고유 앵커 문자열**(예: 함수명, 해당 위치의 고유 주석 문구)로 적는다. 행
번호는 다음 릴리즈 커밋에서 stale해진다 — v1.1.60 세션에서 #1647 본문의 행 346-348은 v1.1.59 시점
값이었고, 스크립트가 608→733행으로 성장해 구현 에이전트 2개가 재탐색해야 했다. 행 번호를
병기하려면 기준 커밋 SHA를 함께 적고 "참고용"임을 명시한다. 후속 위임서도 "행 번호는 참고, 앵커로
재탐색"을 전제로 작성된다(auto-dev.yaml substitution 조항 cross-ref).

Add priority label (`P3` default for defects surfaced here; escalate to `P2` if MEDIUM+ severity).

**Authority**: user directive (session 102) — genuine defects found during release workflows should be registered without prompting. See also R016 Defect Response Matrix: CI/infra defect and Process gap both require Issue registration.

After auto-registering, include the created issue numbers in the summary display.

### 3. Present to User

Auto-register all genuine defects first (see above). Then display follow-up summary showing what was already registered and what remains for user decision:

```
[Follow-up] {n}개 후속 작업 발견

━━━ 자동 등록 완료 ({count}개) ━━━
  ✓ #{issue_number} — {description} (이미 등록됨)
  ✓ #{issue_number} — {description} (이미 등록됨)

━━━ 즉시 실행 추천 ({count}개) ━━━
  1. {description} — 출처: {source}
  2. {description} — 출처: {source}

━━━ 참고 사항 ({count}개) ━━━
  3. {description} — 이미 #{issue_number}로 추적 중

즉시 실행 항목 선택:
  [A] 추천대로 실행 (즉시 실행 항목 모두 실행)
  [B] 개별 선택 (항목별로 질문)
  [C] 건너뛰기
```

Use AskUserQuestion (or equivalent user prompt) to get the choice **only if there are "즉시 실행" items**. If there are none, skip the prompt and complete automatically.

### 4. Process User Choice

**Option A (추천대로)**:
- "Immediate" items → delegate to appropriate specialist agents for execution
- (Trackable items were already auto-registered in step above)
- "Informational" items → skip

**Option B (개별 선택)**:
- For each "즉시 실행" item, ask: `[{n}] {description} — 실행(E) / 건너뛰기(S)?`
- Process each per user choice

**Option C (건너뛰기)**:
- Skip remaining immediate actions
- Complete workflow

### 5. Report

```
[Follow-up Complete]
├── 즉시 실행: {n}개 완료
├── 이슈 등록: {n}개 (#{numbers})
├── 건너뛰기: {n}개
└── 총 처리: {total}개
```

## Issue Creation Template

For auto-registered genuine defects / process gaps:

```bash
gh issue create \
  --title "{간결한 설명}" \
  --body "## 출처\n\nv{version} 릴리즈 워크플로우에서 자동 등록.\n\n## 컨텍스트\n\n{triage/verify에서의 상세 컨텍스트}\n\n## 권장 조치\n\n{권장 사항}" \
  --label "professor"
```

For user-requested issue creation (Option C fallback, if ever used):

```bash
gh issue create \
  --title "{간결한 설명}" \
  --body "## 출처\n\nv{version} 릴리즈 워크플로우에서 발견.\n\n## 컨텍스트\n\n{triage/verify에서의 상세 컨텍스트}\n\n## 권장 조치\n\n{권장 사항}" \
  --label "professor"
```

Add priority label (`P1`, `P2`, `P3`) based on categorization. Default for auto-registered items: `P3` (escalate to `P2` for MEDIUM+ severity).

**`## 권장 조치`의 미검증 제안은 `[가설]` 태그 필수**: `{권장 사항}`에 적는 수정안이 실행·테스트 등으로 검증되지 않았다면, 문장 앞에 `[가설]` 태그를 붙이고 무엇을 확인하면 검증되는지 함께 적으십시오. 원인 진단에만 `[가설]`을 붙이고 제안 수정안은 확정형으로 적으면, 그 제안을 그대로 적용했을 때 실패할 위험이 후속 세션으로 이월됩니다(R020 Diagnostic Hypothesis Verification, Origin: #1725 찐빠 #1).

## Notes

- This skill runs in the main conversation context (via workflow skill step)
- Genuine defect/process gap items are auto-registered as issues WITHOUT user confirmation (session 102 directive)
- Only "즉시 실행" (code-changing immediate action) items require user confirmation
- All file modifications delegated to specialist subagents per R010
- Issue creation uses `gh` CLI directly (read-only operation pattern)
- If no follow-up candidates found, report "No follow-up actions needed" and complete
- PR review feedback is available shortly after PR creation — the omc_pr_analyzer bot comments automatically

## Permission Mode

When spawning agents via the Agent tool during this skill's execution, always pass `mode: "bypassPermissions"`. The Agent tool default (`acceptEdits`) overrides agent frontmatter `permissionMode`, causing permission prompts during unattended execution.