Files

T

genichin 362b008940 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

1.7 KiB

Raw Blame History

name, description, argument-hint, user-invocable

name	description	argument-hint	user-invocable
draft-batch-planning	Use when: drafting the planning document for an existing batch, running /draft-batch-planning with a BAT ID, populating docs/batches/<BAT_ID>/planning.md, or setting batch scope and dependency notes before design.	예: bat-001 또는 docs/batches/bat-001_20260424_scaffold	true

Purpose

This skill writes the planning document for a batch by consolidating included REQs, scope, dependencies, milestones, and key risks.

Inputs

BAT-ID 또는 batch 경로
docs/batches/<BAT_ID>/index.md
포함된 REQ 문서들
docs/batches/<BAT_ID>/planning.md

Core Rules

planning은 batch 수준 범위, 의존성, 순서를 명확히 해야 한다.
REQ 문서를 다시 쓰지 말고 delivery 관점의 묶음 계획으로 요약한다.
planning은 design이 구현 전에 필요한지 여부를 명시해야 한다.
batch-lite라면 planning에 왜 design을 생략할 수 있는지 또는 언제 design이 필요해지는지 남긴다.
planning 작성 후 batch 상태는 in-delivery로 올릴 수 있다.

Execution Procedure

입력에서 batch 경로를 확정한다.
batch index와 포함 REQ를 읽는다.
planning.md에 scope, out-of-scope, dependency, milestone, risk를 채운다.
planning.md의 Design Gate에 design 필요 여부와 근거를 적는다.
필요하면 batch index.md의 Status를 in-delivery로 갱신한다.

Validation

planning 문서에 Included REQ, Delivery Plan, Dependencies, Design Gate, Milestones, Risks가 모두 존재하는지 확인한다.
batch index와 planning의 포함 REQ 목록이 일치하는지 확인한다.

1.7 KiB Raw Blame History