/devdocs-onboard              → Smart Detection (Ask whether to read or write)
/devdocs-onboard --read       → Only read existing documents, no modifications
/devdocs-onboard --update     → Force rescan and update

Check if 00-context.md exists
        │
        ├── Does not exist → Automatically enter update mode
        │
        └── Exists → Ask user
                    ├── "Read existing content" → Display document, no modifications
                    └── "Rescan and update" → Scan project, overwrite file

Session A (Claude Code)          Session B (New AI Tool)
        │                            │
        ├── Understand project structure              │ ← Needs to re-understand
        ├── Read design documents              │ ← Needs to re-read
        ├── Understand current progress              │ ← Needs to re-understand
        └── Know next tasks            │ ← Needs to re-confirm
                                     │
                    ┌────────────────┘
                    ▼
             /devdocs-onboard
                    │
                    ▼
            Generate context summary
                    │
                    ▼
             Quickly take over project

1. Scan DevDocs documents
   │
   ▼
2. Extract key information
   ├── Project Overview
   ├── Technical Architecture
   ├── Current Progress
   └── Pending Tasks
   │
   ▼
3. Scan codebase structure
   │
   ▼
4. Generate context summary
   │
   ▼
5. Output file (can be directly passed to new AI)

# Project Context: <Project Name>

**Generation Time**: YYYY-MM-DD HH:mm
**Generation Tool**: /devdocs-onboard

---

## 1. Project Overview

### 1.1 Project Objectives
<Extracted from 01-requirements.md>

### 1.2 Core Features
| ID | Feature | Status |
|------|------|------|
| F-001 | <Feature Name> | ✅ Completed / 🔄 In Progress / ⏳ Pending Development |

### 1.3 Tech Stack
<Extracted from 02-system-design.md>

---

## 2. System Architecture

### 2.1 Architecture Overview
<Extract architecture diagram from 02-system-design.md>

### 2.2 Core Modules
| Module | Responsibility | Key Files |
|------|------|----------|
| <Module Name> | <Responsibility> | `src/xxx/` |

### 2.3 Core Interfaces
<Extract key interface signatures from 02-system-design.md>

---

## 3. Code Structure

### 3.1 Directory Structure

### 3.2 Key File Explanations
| File | Purpose |
|------|------|
| `src/index.ts` | Entry file |
| `src/config.ts` | Configuration management |

---

## 4. Current Progress

### 4.1 Overall Progress
| Type | Total | Completed | In Progress | Completion Rate |
|------|------|--------|--------|--------|
| Feature Points | X | X | X | XX% |
| Development Tasks | X | X | X | XX% |

### 4.2 Recently Completed
- T-05: <Task Name> (YYYY-MM-DD)
- T-04: <Task Name> (YYYY-MM-DD)

### 4.3 In Progress
- T-06: <Task Name>
  - Status: <Progress Description>
  - Involved Files: `src/xxx.ts`

### 4.4 Uncommitted Changes
<List any uncommitted code changes>

---

## 5. Pending Tasks

### 5.1 Next Tasks
| Priority | Task | Dependencies | Associated Requirements |
|--------|------|------|----------|
| P0 | T-07: <Task Name> | T-06 | F-002, AC-005 |

### 5.2 Blockers
<List any blockers>

---

## 6. Important Agreements

### 6.1 Coding Standards
- Follow MTE principles (Maintainable, Testable, Extensible)
- Functions no longer than 50 lines
- No more than 5 parameters

### 6.2 Testing Requirements
- Unit test coverage ≥ 80%
- Forbid weak assertions

### 6.3 Commit Standards
<Extract project commit style from git log>

---

## 7. Quick Start

### 7.1 Environment Preparation
```bash
<Dependency installation commands>

<Run commands>

<Test commands>

## Information Extraction Rules

### Extract from DevDocs

| Information | Source Document | Extracted Content |
|------|----------|----------|
| Project Objectives | `01-requirements.md` | Requirements background, target users |
| Feature List | `01-requirements.md` | F-XXX feature points and statuses |
| Tech Stack | `02-system-design.md` | Technology selection table |
| Architecture Diagram | `02-system-design.md` | Architecture overview diagram |
| Core Interfaces | `02-system-design.md` | Interface signature table |
| Current Progress | `04-dev-tasks.md` | Execution checklist |
| Pending Tasks | `04-dev-tasks.md` | Uncompleted T-XX tasks |

### Extract from Codebase

| Information | Extraction Method |
|------|----------|
| Directory Structure | `ls -la` or `tree` |
| Key Files | Analyze package.json, entry files |
| Uncommitted Changes | `git status` |
| Commit Style | `git log --oneline -5` |
| Run Commands | Extract from package.json scripts or Makefile |

## Usage Scenarios

### Scenario 1: Complete work and prepare for handover (--update)

### Scenario 2: New AI takes over project (--read)

### Scenario 3: Uncertain (Smart Detection)

## Constraints

### Generation Constraints

- [ ] **Must scan all DevDocs documents**
- [ ] **Must check current codebase status**
- [ ] **Must include uncommitted changes information**
- [ ] Output files must be self-contained (no external links required for understanding)
- [ ] Key information must be directly displayed (not just referencing document paths)

### Content Constraints

- [ ] **Project overview must not exceed 200 words**
- [ ] **Architecture diagram must be included (ASCII or Mermaid)**
- [ ] **Must list executable next-step tasks**
- [ ] Sensitive information (keys, passwords) must not be included
- [ ] File paths must be accurate and accessible

### Update Constraints

- [ ] Overwrite old file with each generation
- [ ] Must record generation time
- [ ] If DevDocs do not exist, prompt user to run the relevant skill first

## Skill Collaboration

| Scenario | Collaborative Skill | Description |
|------|-----------|------|
| DevDocs do not exist | `/devdocs-retrofit` | First reverse-generate documents from code |
| Progress information is outdated | `/devdocs-sync` | First sync document status |
| Need detailed tasks | `/devdocs-dev-tasks` | View complete task list |

## Command Options

```bash
# Smart Detection: Ask user based on document existence status
/devdocs-onboard

# Read-only Mode: Read and display existing documents, no modifications
/devdocs-onboard --read

# Update Mode: Force rescan project and update document
/devdocs-onboard --update