Work

# GitHub Issue/Milestone Work Execution

This command executes development work based on GitHub Issues or Milestones following the project workflow.

## Usage

```bash
/project:work                         # Context mode: create issue from conversation and execute
/project:work --issue <number>        # Single issue implementation
/project:work --milestone <number>    # All issues in milestone (Ralph Loop)

Options

Option	Description
(none)	Context Mode: Analyze conversation, create GitHub issue, then execute
--issue <N>	Implement single issue #N
--milestone <N>	Process all issues in milestone N
--dry-run	Show plan only, no execution
--skip-review	Skip code review (emergency fixes only)
--parallel	Auto-detect and execute parallelizable issues

---

Context Mode (no options)

When /work is invoked without any options, analyze the current conversation context and create a GitHub issue automatically.

Workflow

1. Analyze Conversation Context

   • Review the conversation history
   • Identify the task/feature being discussed
   • Extract requirements, acceptance criteria, and implementation details

2. Create GitHub Issue

   gh issue create --title "<type>: <description>" --body "$(cat <<'EOF'
   ## Summary
   <extracted summary from conversation>
   
   ## Requirements
   - [ ] <requirement 1>
   - [ ] <requirement 2>
   
   ## Acceptance Criteria
   - [ ] <criteria 1>
   - [ ] <criteria 2>
   
   ## Technical Notes
   <any technical details discussed>
   
   ---
   *Auto-generated from conversation context*
   EOF
   )"
   

3. Execute the Created Issue

   • Automatically proceed with Single Issue Mode workflow
   • Use the newly created issue number

Example

User: 로그인 페이지에 "비밀번호 찾기" 링크를 추가해주세요.
      클릭하면 이메일 입력 모달이 뜨고, 이메일로 재설정 링크를 보내야 해요.

User: /work

Claude:
1. Analyzing conversation context...
   - Task: Add "Forgot Password" feature to login page
   - Requirements: Link + Modal + Email sending

2. Creating GitHub Issue #175...
   Title: "feat(auth): add forgot password functionality"
   Body: [auto-generated from context]

3. Proceeding with Issue #175...
   [... single issue workflow continues ...]

Issue Title Format

Type	Prefix	Example
Feature	feat(<scope>):	feat(auth): add forgot password
Bug Fix	fix(<scope>):	fix(login): resolve session timeout
Refactor	refactor(<scope>):	refactor(api): extract validation logic
Docs	docs(<scope>):	docs(readme): update installation guide

---

Single Issue Mode (--issue)

Workflow

1. Load Issue Context

   gh issue view <number> --json number,title,body,labels,milestone
   

   • Read and understand issue requirements
   • Check for dependencies ("depends on #N", "blocked by #N")

2. Prepare Work

   • Create feature branch from develop:

     git checkout develop
     git pull origin develop
     git checkout -b feature/<number>-<description>
     

   • Initialize task.md with issue context

3. Implementation (TDD Cycle)

   • Red: Write failing test
   • Green: Implement minimal code
   • Refactor: Clean up

   At each checkpoint:

   • Commit with issue reference: feat: <description> (#<number>)
   • Update task.md history
   • Update plan.md checkbox (mark with ✅)
   • Update GitHub Issue body checkboxes (see details below)

4. GitHub Issue Checkbox Updates ⚠️ CRITICAL

   When to update checkboxes:

   • ✅ After completing each requirement item
   • ✅ After completing each acceptance criteria
   • ✅ After completing each sub-task in the issue body

   How to update checkboxes:

   # 1. Fetch current issue body
   BODY=$(gh issue view <number> --json body -q .body)
   
   # 2. Update specific checkbox (unchecked → checked)
   # Replace the exact task text that was completed
   UPDATED=$(echo "$BODY" | sed 's/- \[ \] <completed task>/- [x] <completed task>/')
   
   # 3. Apply the update
   gh issue edit <number> --body "$UPDATED"
   

   Progress tracking pattern:

   Status	Checkbox	Example
   Not started	- [ ]	- [ ] Implement login API
   In progress	- [ ] + comment	- [ ] Implement login API (WIP)
   Completed	- [x]	- [x] Implement login API

   Example: Progressive updates during development

   # Initial issue body:
   # - [ ] Create database schema
   # - [ ] Implement API endpoint
   # - [ ] Add unit tests
   # - [ ] Add E2E tests
   
   # After completing database schema:
   gh issue edit 175 --body "$(gh issue view 175 --json body -q .body | sed 's/- \[ \] Create database schema/- [x] Create database schema/')"
   
   # After completing API endpoint:
   gh issue edit 175 --body "$(gh issue view 175 --json body -q .body | sed 's/- \[ \] Implement API endpoint/- [x] Implement API endpoint/')"
   
   # Continue until all checkboxes are checked...
   

5. Add E2E Tests (if applicable)

   • For API changes: Add tests to e2e/tests/api-*.spec.ts
   • For CLI changes: Add tests to platform/services/cli/tests/e2e/
   • Run and verify tests pass before PR
   • Update issue checkbox: - [x] Add E2E tests

6. Create Pull Request

   gh pr create --base develop --title "<type>: <description> (#<number>)" --body "..."
   

7. Code Review

   • Execute /code-review:code-review
   • Address any feedback

8. Merge (on approval)

   gh pr merge --squash --delete-branch
   

   • Issue auto-closes via "Closes #N" in PR
   • Final checkbox update: Ensure ALL checkboxes in issue body are checked

---

Milestone Mode (--milestone)

Workflow

1. Load Milestone Context ⚠️ IMPORTANT

   gh api repos/{owner}/{repo}/milestones/<number>
   

   • Read milestone title, description, due date
   • **Re