/team-create-stories — 스토리 문서 여러 개 동시 작성

여러 Epic 의 스토리 문서를 AI 팀원이 나눠 동시에 작성해 `.bmad/stories/STORY-*.md` 여러 개를 5~15분에 만들고 ZenHub Sprint Backlog 로 등록합니다 — 하나씩 쓰면 스토리당 10~20분.

/team-create-stories — 스토리 문서 여러 개 동시 작성#

항목	내용
실행 명령	`/cc-product:team-create-stories`

한마디로#

여러 명의 작가에게 챕터를 나눠 주고 동시에 글을 쓰게 하는 것과 같습니다. 스토리 문서를 하나씩 차례로 쓰는 대신, AI 팀원 여러 명이 에픽별로 나눠 맡아 한꺼번에 만들어 줍니다.

누가·언제 쓰나요#

팀 리드 역할로 스프린트를 준비하는 사람
작성해야 할 스토리가 3개 이상 여러 에픽에 걸쳐 있을 때 (한 개씩 쓰면 너무 오래 걸리는 상황)
이미 스프린트 계획(epic/story 목록)과 아키텍처 문서가 준비되어 있을 때

👉 전제 조건: 실험 기능인 Agent Teams가 켜져 있어야 합니다(CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1). 꺼져 있으면 명령이 멈추고, 대신 한 개씩 만드는 /create-story를 안내합니다.

무엇을 해주나요#

스토리 문서 여러 개를 동시에 만들어 .bmad/stories/STORY-{ID}.md 파일들로 저장합니다.
스프린트 상태를 한꺼번에 갱신합니다(각 스토리를 "defined" 상태로, 문서 경로 기록).
ZenHub가 연결되어 있으면, 만들어진 스토리를 ZenHub의 Sprint Backlog로 자동 등록(sync)합니다.
포인트가 큰 스토리(기준 충족 시)는 작은 하위 작업(Sub-tasks)으로 쪼개서 ZenHub에 함께 등록합니다.

소요 시간은 보통 5~15분입니다. (하나씩 순서대로 쓰면 스토리당 10~20분이 걸립니다.)

어떻게 쓰나요#

# 스토리 문서 여러 개를 팀으로 동시 작성
/team-create-stories

실행하면 먼저 "이렇게 나눠 만들겠습니다"라는 계획을 보여 주고 확인(y/n) 을 받습니다. (설정에서 agent_teams.auto_approve_plans가 켜져 있으면 이 확인 단계를 건너뜁니다.)

스토리가 1~2개뿐이라면, 동시 작성 대신 한 개씩 만드는 /create-story STORY-{ID} 또는 순차 진행 /dev-story STORY-{ID}를 쓰는 편이 낫습니다.

안에서 무슨 일이 벌어지나요#

사전 점검 — 설정·스프린트 상태·Agent Teams 사용 가능 여부를 확인하고, 아직 문서가 없는 스토리들을 찾아냅니다.
에픽별로 묶기 — 스토리를 에픽 단위로 나눠 팀원에게 한 명당 한 에픽씩 배정합니다. 팀원마다 서로 다른 파일을 쓰므로 충돌이 없습니다.
계획 확인 — 누가 어떤 스토리를 맡는지 보여 주고 진행 여부를 묻습니다.
팀원 투입 — 각 팀원(스토리 작성자)에게 에픽 정보·스토리 목록·아키텍처 요약을 넘겨 동시에 작성을 시작시킵니다.
진행 상황 추적 — 완료된 팀원의 문서가 제대로 만들어졌는지(필수 항목 포함 여부) 확인하며 진척도를 표시합니다.
상태 갱신·동기화 — 모든 팀원이 끝나면 팀 리드가 스프린트 상태를 한꺼번에 갱신하고, ZenHub에 스토리·하위 작업을 등록한 뒤 최종 요약을 보여 줍니다.

⚙️ 상세 옵션·실행 명세 (개발자 / AI 에이전트용)

Workflow Overview#

Goal: Create multiple story documents in parallel using Agent Teams

Phase: 4 - Implementation (Parallel Story Definition)

Agent: Team Lead

Inputs: Sprint plan with epic/story list, architecture document

Output: Multiple .bmad/stories/STORY-{ID}.md files, updated sprint status

Duration: 5-15 minutes (parallel vs 10-20 min per story sequential)

When to use: When you have 3+ stories to document across multiple epics

Prerequisite: Agent Teams must be enabled (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1)

Pre-Flight#

Load context per helpers.md#Combined-Config-Load
Check sprint status per helpers.md#Load-Sprint-Status
Check Agent Teams per helpers.md#Check-Agent-Teams-Available

If teams_available = false:

Output:

      ⚠ Agent Teams not available.

Agent Teams is an experimental feature that requires:
  CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

Sequential alternative:
  Use /create-story STORY-{ID} to create stories one at a time.

Stop workflow (do not proceed)

Load sprint plan: Read .bmad/sprint-plan-*.md
Load architecture (if Level 2+): Read .bmad/architecture-*.md
Load ZenHub context per helpers.md#Load-ZenHub-Context
Identify stories to create:
- Find all stories without story documents (no .bmad/stories/STORY-{ID}.md)
- Or accept user-specified story IDs as input
Load max_teammates from config agent_teams.max_teammates (default: 3)
Check sub-task support:
- If zh_sub_tasks_enabled: Stories with 5+ points will include auto-generated sub-tasks

Part 1: Group Stories by Epic#

Organize stories for parallel creation:

Group by epic:

    Epic 1  " {name} " : STORY-001, STORY-002, STORY-003
Epic 2  " {name} " : STORY-004, STORY-005
Epic 3  " {name} " : STORY-006, STORY-007, STORY-008

Assign epics to teammates:
- Each teammate handles one epic's stories
- If more epics than max_teammates: combine smallest epics
- No file conflicts: each teammate writes different STORY-{ID}.md files

Display plan:

    Story Creation Plan:

Teammate 1 (Story Creator):
  Epic:  " {epic_1_name} " 
   Stories: STORY-001, STORY-002, STORY-003
  Output: .bmad/stories/STORY-001.md, STORY-002.md, STORY-003.md

Teammate 2 (Story Creator):
  Epic:  " {epic_2_name} " 
   Stories: STORY-004, STORY-005
  Output: .bmad/stories/STORY-004.md, STORY-005.md

Total: {count} stories across {count} teammates

Proceed? (y/n)

Wait for user confirmation.

If config.agent_teams.auto_approve_plans = true, skip confirmation.

Part 2: Spawn Story Creators#

Step 1: Create shared task list per helpers.md#Create-Team-Task-List:

For each teammate:

TaskCreate:
  subject:  " Story Creator: Create stories for Epic {epic_name} " 
   description: Story IDs, epic context, architecture summary
  activeForm:  " Creating stories for {epic_name} "

Step 2: Spawn teammates per helpers.md#Spawn-BMAD-Teammate:

For each teammate:

role: "story-creator"
context:
- Epic details (name, description, goals)
- Story IDs and titles from sprint plan
- Architecture key sections (relevant to this epic)
- Story template (standard BMAD format)

Each teammate creates stories independently — no file conflicts since each writes to unique .bmad/stories/STORY-{ID}.md paths.

Sub-task generation context (if zh_sub_tasks_enabled): Include in each teammate's context:

"For stories with {min_story_points}+ points, include a Sub-tasks section"
"Sub-tasks should be discrete implementation units (1-4 hours each)"
"Categories: Implementation, Validation, Testing"
Teammates generate sub-task lists in story documents; Lead syncs to ZenHub in Part 4

Part 3: Monitor & Collect#

Monitor teammate progress:

Poll task status:

    Call TaskList
Display progress: {completed}/{total} teammates done

On teammate completion:
- Verify story documents exist at expected paths
- Quick validation: check each story has required sections (User Story, Acceptance Criteria, Technical Notes, Story Points)

Display progress:

    Story Creation Progress:

Teammate 1: ✓ Complete
  ✓ STORY-001.md (5 acceptance criteria, 3 points)
  ✓ STORY-002.md (4 acceptance criteria, 5 points)
  ✓ STORY-003.md (6 acceptance criteria, 8 points)

Teammate 2: 🔄 In Progress
  ✓ STORY-004.md (3 acceptance criteria, 2 points)
  ⏳ STORY-005.md ...

Part 4: Update Status & Sync#

After all teammates complete:

Step 1: Update sprint status (Lead-only batch update):

Per helpers.md#Update-Sprint-Status:

For each created story:
  - Update status:  " defined " 
   - Add story_document path
  - Verify story_points match sprint plan

Step 2: Sync to ZenHub (if available):

If zh_available:
  For each created story:
    1. Build story body from document content
    2. Call helpers.md#Sync-Story-to-ZenHub:
       - story_title, story_body, story_points
       - zh_epic_id (parent epic)
       - pipeline_id: Sprint Backlog
    3. Call helpers.md#Store-ZenHub-Cross-Reference:
       - Update story document with ZenHub link
       - Update sprint-status.yaml with zh_issue_id
    4. Log:  " ✓ Synced STORY-{ID} → ZenHub #{issue_number} " 

   If zh_sub_tasks_enabled:
    For each story with sub-tasks in its document:
      5. For each sub-task:
         a. Generate sub-task body per helpers.md#Generate-Sub-task-Body
         b. Call helpers.md#Sync-Sub-task-to-ZenHub:
            - sub_task_title, sub_task_body
            - zh_story_id (parent, from step 2 above)
         c. Store zh_sub_task_id in sprint-status sub_tasks array
         d. Log:  "    ✓ Sub-task: #{sub_issue_number} (parent: #{story_number}) "

Step 3: Display summary:

✓ Team Story Creation Complete!

Stories Created: {count}/{total}

Epic  " {name} " :
  STORY-001: {title} ({points} pts, {criteria_count} Acceptance Criteria)
  STORY-002: {title} ({points} pts, {criteria_count} Acceptance Criteria)
  STORY-003: {title} ({points} pts, {criteria_count} Acceptance Criteria)

Epic  " {name} " :
  STORY-004: {title} ({points} pts, {criteria_count} Acceptance Criteria)
  STORY-005: {title} ({points} pts, {criteria_count} Acceptance Criteria)

Total Story Points: {sum}
Documents: .bmad/stories/

ZenHub: {count} stories synced to Sprint Backlog  (if zh_available)
ZenHub: {count} sub-tasks synced  (if sub-tasks created)

Next Steps:
  1. Review stories: Read .bmad/stories/STORY-{ID}.md
  2. Start development: /team-dev (parallel) or /dev-story STORY-{ID} (sequential)

Helper References#

Load config: helpers.md#Combined-Config-Load
Load sprint status: helpers.md#Load-Sprint-Status
Update sprint status: helpers.md#Update-Sprint-Status
Check Agent Teams: helpers.md#Check-Agent-Teams-Available
Spawn teammate: helpers.md#Spawn-BMAD-Teammate
Create team tasks: helpers.md#Create-Team-Task-List
Collect results: helpers.md#Collect-Team-Results
ZenHub context: helpers.md#Load-ZenHub-Context
Sync story: helpers.md#Sync-Story-to-ZenHub
Sync sub-task: helpers.md#Sync-Sub-task-to-ZenHub
Generate sub-task body: helpers.md#Generate-Sub-task-Body
Store xref: helpers.md#Store-ZenHub-Cross-Reference

Notes for LLMs#

ALWAYS check Agent Teams availability first (Pre-Flight step 3-4)
If teams not available, suggest /create-story and STOP
No file conflicts possible: each teammate writes unique STORY-{ID}.md files
Sprint-status.yaml updates are Lead-only: batch update after ALL teammates complete
ZenHub sync is also batched after teammates complete (Lead handles all syncing)
Story documents must follow standard BMAD template format
Validate each story has required sections before accepting
If a teammate fails, its stories can be created manually with /create-story
Sub-task generation is included in teammate context when zh_sub_tasks_enabled
Sub-task ZenHub sync is batched by Lead after all teammates complete (not by teammates)
Sub-tasks are only generated for stories meeting min_story_points threshold

Remember: Story creation is inherently parallelizable since each story is an independent document. The main value is time savings when creating 3+ stories.