Squashed '.vendor/stage-pilot/' changes from 7ab085e..551777b

551777b feat: add interface contract and data model baseline support to bootstrap-baseline f17e086 feat: add bootstrap seed file support to bootstrap-baseline skill be85338 feat: introduce lightweight change path, change-req skill, and release feedback loop 949bb40 docs(skill): new-discovery 병렬 Discovery 및 active-cycle 처리 규칙 강화 7f96130 docs: fix draft-req skill template paths 94b1445 diff --git a/.github/skills/draft-batch-design/SKILL.md b/.github/skills/draft-batch-design/SKILL.md index 5f87d00..944e075 100644 --- a/.github/skills/draft-batch-design/SKILL.md +++ b/.github/skills/draft-batch-design/SKILL.md @@ -1,6 +1,6 @@ --- name: draft-batch-design -description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, or recording architecture and interface decisions before implementation." +description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, recording architecture and interface decisions before implementation, or planning updates to docs/project-structure.md and docs/runtime-flows.md." argument-hint: "예: bat-001 또는 docs/batches/bat-001_20260424_scaffold" user-invocable: true --- @@ -9,27 +9,43 @@ user-invocable: true d1ce3ce 프로세스 완전 변경 git-subtree-dir: .vendor/stage-pilot git-subtree-split: 551777bc7009ee133fbaab1267ca324f1dc3c6bb
2026-04-30 13:00:41 +00:00
parent 8406e6f7af
commit 362b008940
106 changed files with 6716 additions and 4165 deletions
@@ -0,0 +1,110 @@
+# req-001: Docs release checklist
+
+- Status: Approved
+- Type: Documentation
+- Priority: Medium
+- Owner: Docs Maintainer
+
+## Intent
+- docs-only release에서도 소비자 관점의 품질 게이트를 문서화하고 검증 근거로 남긴다.
+
+## Requirement
+- docs-only release는 release note 반영과 broken-link 검증 결과를 release evidence에 포함해야 한다.
+
+## Acceptance Criteria
+1. Given docs-only release가 준비되었을 때, When release evidence를 검토하면, Then broken-link 검증 결과가 명시되어야 한다.
+2. Given release feedback가 수집되었을 때, When follow-up를 분류하면, Then Discovery/REQ/change-req 입력이 구분되어야 한다.
+
+## Impacted Area
+- Docs: docs/releases/rel-001_20260428_docs_release_hardening.md, README.md
+- Modules: bootstrap/stagepilot.sh, .github/scripts/stagepilot-doctor.py
+- Tests: doctor release feedback summary validation
+
+## Notes
+- `CHG-20260430-02`로 acceptance criteria가 강화되어 기존 구현 증거는 재검증이 필요하다.
+
+## Change Log
+
+### CHG-20260426-01
+- Date: 2026-04-26
+- Author: Docs Maintainer
+
+#### Change Summary
+- initial requirement created
+
+#### Intent
+- docs-only release checklist를 requirement로 관리한다.
+
+#### Acceptance Criteria Delta
+- Added:
+  - release evidence must include release note update result
+- Updated:
+  - none
+- Removed:
+  - none
+
+#### Impacted Area Delta
+- Docs:
+  - release template
+- Modules:
+  - none
+- Tests:
+  - manual release review
+
+#### Delivery Trace Delta
+- Batches:
+  - bat-001
+- Releases:
+  - rel-001
+
+#### Revalidation Impact
+- Reverification Needed: no
+- Existing Implementation Invalidated: no
+- Status Recommendation: keep-current
+- Follow-up Action: implement through bat-001
+
+#### Validation Plan
+- verify release checklist before approval
+
+### CHG-20260430-02
+- Date: 2026-04-30
+- Author: Docs Maintainer
+
+#### Change Summary
+- strengthen docs-only release criteria to require broken-link evidence and explicit feedback triage
+
+#### Intent
+- release feedback에서 드러난 품질 gap을 기존 REQ에 반영한다.
+
+#### Acceptance Criteria Delta
+- Added:
+  - broken-link 검증 결과가 release evidence에 포함되어야 한다.
+  - feedback handoff는 Discovery/REQ/change-req 입력을 구분해야 한다.
+- Updated:
+  - release note update alone is no longer sufficient for docs-only release verification.
+- Removed:
+  - none
+
+#### Impacted Area Delta
+- Docs:
+  - docs/releases/rel-001_20260428_docs_release_hardening.md
+  - README.md
+- Modules:
+  - .github/scripts/stagepilot-doctor.py
+- Tests:
+  - doctor feedback summary sample
+
+#### Delivery Trace Delta
+- Batches:
+  - bat-001 needs reverification or successor batch is required
+- Releases:
+  - rel-001 remains historical evidence only
+
+#### Revalidation Impact
+- Reverification Needed: yes
+- Existing Implementation Invalidated: yes
+- Status Recommendation: revert-to-approved
+- Follow-up Action: prepare a follow-up batch to reverify docs-only release criteria
+
+#### Validation Plan
+- rerun doctor on a follow-up batch and verify release feedback summary plus broken-link evidence
@@ -0,0 +1,26 @@
+# Software Requirement Specification Index
+
+## 목적
+- 이 문서는 프로젝트의 SRS 운영 기준과 requirement 목록을 관리하는 entry point이다.
+- 개별 requirement의 상세 내용은 타입별 폴더 하위 `req-XXX_*.md` 파일에서 관리한다.
+
+## 사용 방법
+1. 새로운 requirement가 필요하면 `Next Requirement ID`를 확인하고 `docs/srs/req-template.md`를 복사해 `docs/srs/<Type>/req-XXX_<slug>.md` 파일을 생성한다.
+2. 초안 작성은 `draft-req`, 승인 전환은 `confirm-req`, 변경 대응은 `change-req`, 구현 완료 전환은 `confirm-req-implemented` skill을 기준으로 수행한다.
+3. 작성 또는 수정 후 누락과 모호성을 점검한다.
+4. requirement 추가 또는 변경 후 `Next Requirement ID`, `Requirement Register`, `Recent Change Log Summary`를 함께 갱신한다.
+
+## Next Requirement ID
+
+- Current: `REQ-002`
+- Rule: `Requirement Register`에 있는 가장 큰 REQ 번호보다 정확히 1 커야 한다.
+
+## Requirement Register
+
+| ID | Title | Type | Status | Priority | Owner | Link |
+| --- | --- | --- | --- | --- | --- | --- |
+| REQ-001 | Docs release checklist | Documentation | Approved | Medium | Docs Maintainer | [req-001](./Documentation/req-001_docs_release_checklist.md) |
+
+## Recent Change Log Summary
+
+- 2026-04-30 `REQ-001` `CHG-20260430-02`: broken-link acceptance criteria 강화, 상태 `Implemented -> Approved`