project-init

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

project-init

项目初始化

Purpose

用途

Provide AI assistants with structured guidance for initializing brand new (greenfield) projects using the AI Dev Flow framework. This skill handles the one-time setup process that must occur BEFORE workflow execution begins.

⚠️ CRITICAL: This skill is for NEW PROJECT INITIALIZATION ONLY. For ongoing workflow execution on existing projects, use the

doc-flow

skill instead.

为AI助手提供结构化指导，使其能够使用AI Dev Flow框架初始化全新（从零开始）的项目。该技能负责处理工作流执行开始前必须完成的一次性设置流程。

⚠️ 重要提示：此技能仅适用于新项目初始化。对于现有项目的持续工作流执行，请使用

doc-flow

技能。

When to Use This Skill

何时使用此技能

Use project-init when:

Starting a brand new project from scratch (greenfield)
No project folders exist yet
Domain has not been selected
Project structure needs to be initialized

Do NOT use project-init when:

Project already has docs/ folder structure
Domain is already configured
Working on existing project
→ Use
```
doc-flow
```
skill instead for workflow execution

在以下场景使用project-init：

从零开始启动全新项目（greenfield）
尚未创建任何项目文件夹
尚未选择领域
需要初始化项目结构

请勿在以下场景使用project-init：

项目已存在docs/文件夹结构
领域已配置完成
正在处理现有项目
→ 请改用
```
doc-flow
```
技能执行工作流

Hand-off to doc-flow

交接至doc-flow

After completing project initialization, AI Assistant MUST inform user:

✅ Project initialization complete!

Next: Use the `doc-flow` skill to begin workflow execution:
- Create BRD (Business Requirements)
- Create PRD (Product Requirements)
- Follow 15-layer architecture (Layers 0-14) with 11 artifact directories (BRD through TASKS): BRD → PRD → EARS → BDD → ADR → SYS → REQ → [IMPL] → [CTR] → SPEC → TASKS → Code → Tests → Validation

完成项目初始化后，AI助手必须告知用户：

✅ 项目初始化完成！

下一步：使用`doc-flow`技能开始工作流执行：
- 创建BRD（业务需求文档）
- 创建PRD（产品需求文档）
- 遵循15层架构（第0-14层）及11个工件目录（从BRD到TASKS）：BRD → PRD → EARS → BDD → ADR → SYS → REQ → [IMPL] → [CTR] → SPEC → TASKS → 代码 → 测试 → 验证

Initialization Workflow (8 Steps)

初始化工作流（8个步骤）

Step 0: Read Execution Rules

步骤0：阅读执行规则

File: AI_ASSISTANT_RULES.md

Purpose: Understand core execution rules before starting

Key Rules:

Domain Selection FIRST
Create Folders BEFORE Documents
Apply Domain Configuration
Run Contract Questionnaire
Initialize Index Files
Validate Setup
Token Optimization
Tool-Specific Guidance

Action: AI Assistant reads this file to understand all 15 rules

文件：AI_ASSISTANT_RULES.md

用途：在开始前理解核心执行规则

关键规则：

先选择领域
先创建文件夹再创建文档
应用领域配置
运行合同调查问卷
初始化索引文件
验证设置
Token优化
工具特定指导

操作：AI助手阅读此文件以了解全部15条规则

Step 1: Domain Selection (REQUIRED FIRST)

步骤1：领域选择（必须第一步完成）

File: DOMAIN_SELECTION_QUESTIONNAIRE.md

Purpose: Determine project domain to load correct configuration

AI Assistant Action: Present questionnaire to user

═══════════════════════════════════════════════════════════
                 PROJECT DOMAIN SELECTION
═══════════════════════════════════════════════════════════

What is the purpose and focus of this new project?

Select one:

1. Financial Services (DEFAULT)
   - Trading platforms, banking, insurance, portfolio management
   - Regulatory: SEC, FINRA, SOX, Basel III, PCI-DSS

2. Software/SaaS
   - B2B/B2C software services, multi-tenant applications
   - Regulatory: SOC2, GDPR/CCPA, ISO 27001

3. Healthcare
   - EMR, telemedicine, medical devices, patient management
   - Regulatory: HIPAA, FDA, HITECH, 21 CFR Part 11

4. E-commerce
   - Retail, marketplace, subscription services
   - Regulatory: PCI-DSS, GDPR/CCPA, FTC

5. IoT (Internet of Things)
   - Connected devices, sensors, industrial systems
   - Regulatory: FCC, CE, UL/IEC, FDA (medical devices)

6. Other/Generic
   - Internal tools, utilities, custom domain
   - Regulatory: Company policies only

Enter selection (1-6) or press Enter for default (1):

Output: Domain selected, configuration file determined

Domain Configuration Mapping:

Selection	Domain	Config File
1 or Enter	Financial Services	FINANCIAL_DOMAIN_CONFIG.md
2	Software/SaaS	SOFTWARE_DOMAIN_CONFIG.md
3	Healthcare	DOMAIN_ADAPTATION_GUIDE.md (Healthcare)
4	E-commerce	DOMAIN_ADAPTATION_GUIDE.md (E-commerce)
5	IoT	DOMAIN_ADAPTATION_GUIDE.md (IoT)
6	Other/Generic	GENERIC_DOMAIN_CONFIG.md

文件：DOMAIN_SELECTION_QUESTIONNAIRE.md

用途：确定项目领域以加载正确的配置

AI助手操作：向用户展示调查问卷

═══════════════════════════════════════════════════════════
                 项目领域选择
═══════════════════════════════════════════════════════════

这个新项目的用途和重点是什么？

请选择一项：

1. 金融服务（默认）
   - 交易平台、银行、保险、投资组合管理
   - 监管要求：SEC、FINRA、SOX、巴塞尔协议III、PCI-DSS

2. 软件/SaaS
   - B2B/B2C软件服务、多租户应用
   - 监管要求：SOC2、GDPR/CCPA、ISO 27001

3. 医疗健康
   - 电子病历、远程医疗、医疗设备、患者管理
   - 监管要求：HIPAA、FDA、HITECH、21 CFR Part 11

4. 电子商务
   - 零售、市场平台、订阅服务
   - 监管要求：PCI-DSS、GDPR/CCPA、FTC

5. IoT（物联网）
   - 互联设备、传感器、工业系统
   - 监管要求：FCC、CE、UL/IEC、FDA（医疗设备）

6. 其他/通用
   - 内部工具、实用程序、自定义领域
   - 监管要求：仅遵循公司政策

请输入选项编号（1-6）或按回车键选择默认项（1）：

输出：已选择领域，确定配置文件

领域配置映射：

选项	领域	配置文件
1 或回车键	金融服务	FINANCIAL_DOMAIN_CONFIG.md
2	软件/SaaS	SOFTWARE_DOMAIN_CONFIG.md
3	医疗健康	DOMAIN_ADAPTATION_GUIDE.md (Healthcare)
4	电子商务	DOMAIN_ADAPTATION_GUIDE.md (E-commerce)
5	IoT	DOMAIN_ADAPTATION_GUIDE.md (IoT)
6	其他/通用	GENERIC_DOMAIN_CONFIG.md

Step 2: Folder Structure Creation (REQUIRED SECOND)

步骤2：创建文件夹结构（必须第二步完成）

Rule: AI Assistant MUST create complete directory structure BEFORE creating any documents.

Why: Prevents "file not found" errors, ensures proper organization

IMPORTANT: Ensure project root directory exists first:

bash

undefined

规则：AI助手必须在创建任何文档之前创建完整的目录结构。

原因：避免“文件未找到”错误，确保组织规范

重要提示：首先确保项目根目录已存在：

bash

undefined

Create project root directory if it doesn't exist

如果项目根目录不存在则创建

mkdir -p {project_root} cd {project_root}


> Replace `{project_root}` with your actual project path (e.g., `/opt/data/my_project`)

**Commands to Execute**:

```bash

mkdir -p {project_root} cd {project_root}


> 将`{project_root}`替换为实际项目路径（例如：`/opt/data/my_project`）

**要执行的命令**：

```bash

Core 11 artifact directories (BRD through TASKS)

核心11个工件目录（从BRD到TASKS）

mkdir -p docs/BRD mkdir -p docs/PRD mkdir -p docs/EARS mkdir -p docs/BDD mkdir -p docs/ADR mkdir -p docs/SYS mkdir -p docs/REQ mkdir -p docs/IMPL mkdir -p docs/CTR mkdir -p docs/SPEC mkdir -p docs/TASKS

NOTE: REQ and CTR subdirectories are created on-demand by doc-req and doc-ctr skills

注意：REQ和CTR子目录会在doc-req和doc-ctr技能生成文档时按需创建。

when documents are generated. This ensures folders match actual project needs.

这确保文件夹与实际项目需求匹配。

Scripts directory

脚本目录

mkdir -p scripts

Work plans directory (for /save-plan command output)

工作计划目录（用于/save-plan命令输出）

mkdir -p work_plans


**Validation**:
```bash
ls -la docs/  # Verify 11 artifact directories created
ls -la work_plans/  # Verify work_plans directory

mkdir -p work_plans


**验证**：
```bash
ls -la docs/  # 验证已创建11个工件目录
ls -la work_plans/  # 验证work_plans目录存在

Step 3: Load Domain Configuration

步骤3：加载领域配置

Files:

FINANCIAL_DOMAIN_CONFIG.md - Default
SOFTWARE_DOMAIN_CONFIG.md
GENERIC_DOMAIN_CONFIG.md

Purpose: Apply domain-specific terminology and placeholders

AI Assistant Action:

Read selected domain configuration file
Extract placeholder mappings
Store terminology for document generation

Example Mappings:

Financial Services:

[RESOURCE_COLLECTION] → Portfolio
[RESOURCE_ITEM] → Position
[USER_ROLE] → Trader / Portfolio Manager
[TRANSACTION] → Trade
[REGULATORY_REQUIREMENT] → SEC Rule 15c3-5

Software/SaaS:

[RESOURCE_COLLECTION] → Workspace
[RESOURCE_ITEM] → Resource
[USER_ROLE] → Account Admin / Member
[TRANSACTION] → API Call
[REGULATORY_REQUIREMENT] → SOC2 Control

Generic:

[RESOURCE_COLLECTION] → Collection
[RESOURCE_ITEM] → Entity
[USER_ROLE] → User
[TRANSACTION] → Action
[REGULATORY_REQUIREMENT] → Company Policy

文件：

FINANCIAL_DOMAIN_CONFIG.md - 默认
SOFTWARE_DOMAIN_CONFIG.md
GENERIC_DOMAIN_CONFIG.md

用途：应用领域特定术语和占位符

AI助手操作：

读取所选领域的配置文件
提取占位符映射关系
存储术语以供文档生成使用

示例映射：

金融服务：

[RESOURCE_COLLECTION] → 投资组合
[RESOURCE_ITEM] → 持仓
[USER_ROLE] → 交易员 / 投资组合经理
[TRANSACTION] → 交易
[REGULATORY_REQUIREMENT] → SEC Rule 15c3-5

软件/SaaS：

[RESOURCE_COLLECTION] → 工作区
[RESOURCE_ITEM] → 资源
[USER_ROLE] → 账户管理员 / 成员
[TRANSACTION] → API调用
[REGULATORY_REQUIREMENT] → SOC2控制项

通用：

[RESOURCE_COLLECTION] → 集合
[RESOURCE_ITEM] → 实体
[USER_ROLE] → 用户
[TRANSACTION] → 操作
[REGULATORY_REQUIREMENT] → 公司政策

Step 4: Template Copying (Optional)

步骤4：复制模板（可选）

Purpose: Copy framework templates to project (optional step)

Commands:

bash

undefined

用途：将框架模板复制到项目中（可选步骤）

命令：

bash

undefined

Create ai_dev_flow directory for framework templates

创建ai_dev_flow目录用于存放框架模板

mkdir -p ai_dev_flow

Copy all templates (if framework templates exist)

复制所有模板（如果框架模板存在）

cp -r {framework_root}/ai_dev_flow/* ai_dev_flow/

Copy validation scripts

复制验证脚本

cp {framework_root}/ai_dev_flow/scripts/*.py scripts/


**Directory Purpose**:
- `ai_dev_flow/` = Framework templates (BRD-TEMPLATE.md, examples/, etc.)
- `docs/` = Project documentation (BRD-01.md, PRD-01.md, etc.)

**Note**: This step is optional. Templates can also be referenced directly from framework location.

---

cp {framework_root}/ai_dev_flow/scripts/*.py scripts/


**目录用途**：
- `ai_dev_flow/` = 框架模板（BRD-TEMPLATE.md、examples/等）
- `docs/` = 项目文档（BRD-01.md、PRD-01.md等）

**注意**：此步骤为可选。也可以直接从框架位置引用模板。

---

Step 5: Contract Decision (REQUIRED)

步骤5：合同决策（必须完成）

File: CONTRACT_DECISION_QUESTIONNAIRE.md

Purpose: Determine if CTR (Contracts) layer should be included in workflow

AI Assistant Action: Present questionnaire to user

═══════════════════════════════════════════════════════════
              CONTRACT DECISION QUESTIONNAIRE
═══════════════════════════════════════════════════════════

Does this project require API contracts or interface definitions?

Select all that apply:

1. ☐ REST/GraphQL APIs (External HTTP endpoints)
2. ☐ Event Schemas (Pub/Sub, message queues, webhooks)
3. ☐ Data Contracts (Shared database schemas, data models between services)
4. ☐ RPC/gRPC Interfaces (Service-to-service communication)
5. ☐ WebSocket APIs (Real-time bidirectional communication)
6. ☐ File Format Specifications (CSV, JSON, XML exchange formats)
7. ☐ None - Internal logic only
8. ☐ Unsure - Need guidance

Enter selections (comma-separated, e.g., "1,2" or single "7"):

Decision Matrix:

Selection	Include CTR?	Workflow
1-6	YES	REQ → IMPL → CTR → SPEC → TASKS
7	NO	REQ → IMPL → SPEC → TASKS
8	Ask follow-up questions	See CONTRACT_DECISION_QUESTIONNAIRE.md

Output: Workflow determined (with or without CTR layer)

文件：CONTRACT_DECISION_QUESTIONNAIRE.md

用途：确定工作流中是否应包含CTR（合同）层

AI助手操作：向用户展示调查问卷

═══════════════════════════════════════════════════════════
              合同决策调查问卷
═══════════════════════════════════════════════════════════

此项目是否需要API合同或接口定义？

请选择所有适用项：

1. ☐ REST/GraphQL APIs（外部HTTP端点）
2. ☐ 事件模式（发布/订阅、消息队列、Webhook）
3. ☐ 数据合同（共享数据库模式、服务间数据模型）
4. ☐ RPC/gRPC接口（服务间通信）
5. ☐ WebSocket APIs（实时双向通信）
6. ☐ 文件格式规范（CSV、JSON、XML交换格式）
7. ☐ 无 - 仅包含内部逻辑
8. ☐ 不确定 - 需要指导

请输入选项编号（逗号分隔，例如："1,2" 或单独输入"7"）：

决策矩阵：

选项	是否包含CTR？	工作流
1-6	是	REQ → IMPL → CTR → SPEC → TASKS
7	否	REQ → IMPL → SPEC → TASKS
8	提出后续问题	请参阅CONTRACT_DECISION_QUESTIONNAIRE.md

输出：确定工作流（包含或不包含CTR层）

Step 6: Index File Initialization + Document Control

步骤6：初始化索引文件 + 文档控制

Purpose: Create index files for each document type

Document Control Requirements: All AI Dev Flow templates include a Document Control section with:

Project metadata (name, version, date, owner, preparer, status)
Document Revision History table
Essential for traceability, change management, and regulatory compliance

AI Assistant Must Emphasize: When creating documents from templates, users must complete the Document Control section with all required fields.

Commands:

bash

undefined

用途：为每种文档类型创建索引文件

文档控制要求：所有AI Dev Flow模板都包含文档控制部分，其中包括：

项目元数据（名称、版本、日期、所有者、编制者、状态）
文档修订历史表
对于可追溯性、变更管理和合规性至关重要

AI助手必须强调：从模板创建文档时，用户必须填写文档控制部分的所有必填字段。

命令：

bash

undefined

Create index files

创建索引文件

touch docs/BRD/BRD-00_index.md touch docs/prd/PRD-00_index.md touch docs/ears/EARS-00_index.md touch docs/BDD/BDD-00_index.md touch docs/adrs/ADR-00_index.md touch docs/sys/SYS-00_index.md touch docs/REQ/REQ-00_index.md touch docs/IMPL/IMPL-00_index.md touch docs/CTR/CTR-00_index.md touch docs/specs/SPEC-00_index.yaml touch docs/TASKS/TASKS-00_index.md


**Index File Purpose**:
- Track all documents of each type
- Provide next available ID
- Document registry with status

---


**索引文件用途**：
- 跟踪每种类型的所有文档
- 提供下一个可用的ID
- 包含状态的文档注册表

---

Step 7: Validation

步骤7：验证

Purpose: Verify setup complete and correct

Validation Commands:

bash

undefined

用途：验证设置已完成且正确

验证命令：

bash

undefined

Verify directory structure

验证目录结构

ls -laR docs/

Verify index files exist

验证索引文件是否存在

ls docs//index. || ls docs//_index.*

Expected: 11 artifact directories (BRD through TASKS) + domain subdirectories

预期结果：11个工件目录（从BRD到TASKS） + 领域子目录

Expected: 11 index files

预期结果：11个索引文件


**Success Criteria**:
- ✅ All 11 artifact directories exist (BRD, PRD, EARS, BDD, ADR, SYS, REQ, IMPL, CTR, SPEC, TASKS)
- ✅ Domain-specific subdirectories exist (risk/, trading/, tenant/, etc.)
- ✅ All index files created
- ✅ All templates include Document Control sections
- ✅ Validation scripts present (if copied)
- ✅ work_plans directory exists (for /save-plan command)

**Error Handling**:
- If folders missing: Re-run Step 2
- If index files missing: Re-run Step 6
- If domain subdirs missing: Check Step 1 domain selection

---


**成功标准**：
- ✅ 所有11个工件目录已存在（BRD、PRD、EARS、BDD、ADR、SYS、REQ、IMPL、CTR、SPEC、TASKS）
- ✅ 领域特定子目录已存在（risk/、trading/、tenant/等）
- ✅ 所有索引文件已创建
- ✅ 所有模板包含文档控制部分
- ✅ 验证脚本已存在（如果已复制）
- ✅ work_plans目录已存在（用于/save-plan命令）

**错误处理**：
- 若缺少文件夹：重新运行步骤2
- 若缺少索引文件：重新运行步骤6
- 若缺少领域子目录：检查步骤1的领域选择

---

Step 8: Project Ready - Hand-off to doc-flow

步骤8：项目准备完成 - 交接至doc-flow

AI Assistant Confirmation Message:

═══════════════════════════════════════════════════════════
              PROJECT INITIALIZATION COMPLETE
═══════════════════════════════════════════════════════════

✓ Domain: [Financial Services / Software/SaaS / etc.]
✓ Folders: Created (11 artifact directories + domain subdirectories)
✓ Domain Config: Applied ([PLACEHOLDERS] → [domain terms])
✓ Contracts: [Included / Skipped] (CTR layer [active / inactive])
✓ Index Files: Initialized (11 files)
✓ Validation: Passed

Workflow Configuration:
[With CTR]:    REQ → IMPL → CTR → SPEC → TASKS → Code
[Without CTR]: REQ → IMPL → SPEC → TASKS → Code

═══════════════════════════════════════════════════════════
                      NEXT STEPS
═══════════════════════════════════════════════════════════

✅ Project structure ready for development!

Next: Use the `doc-flow` skill to begin workflow execution

Week 1 Tasks (see PROJECT_KICKOFF_TASKS.md):
- Day 1: Create BRD (Business Requirements)
- Day 2: Create PRD + EARS (Product Requirements)
- Day 3: Create BDD + ADR (Tests + Architecture)
- Day 4: Create SYS + REQ (System Specs + Requirements)
- Day 5: Create IMPL + CTR (Implementation Plan + Contracts)
- Day 6: Create SPEC (Technical Specifications)
- Day 7: Create TASKS + Validation

Invoke: doc-flow skill to start Day 1

═══════════════════════════════════════════════════════════

AI助手确认消息：

═══════════════════════════════════════════════════════════
              项目初始化完成
═══════════════════════════════════════════════════════════

✓ 领域：[金融服务 / 软件/SaaS / 等]
✓ 文件夹：已创建（11个工件目录 + 领域子目录）
✓ 领域配置：已应用（[占位符] → [领域术语]）
✓ 合同：[已包含 / 已跳过]（CTR层[激活 / 未激活]）
✓ 索引文件：已初始化（11个文件）
✓ 验证：已通过

工作流配置：
[包含CTR]:    REQ → IMPL → CTR → SPEC → TASKS → 代码
[不包含CTR]: REQ → IMPL → SPEC → TASKS → 代码

═══════════════════════════════════════════════════════════
                      下一步
═══════════════════════════════════════════════════════════

✅ 项目结构已准备就绪，可开始开发！

下一步：使用`doc-flow`技能开始工作流执行

第1周任务（请参阅PROJECT_KICKOFF_TASKS.md）：
- 第1天：创建BRD（业务需求文档）
- 第2天：创建PRD + EARS（产品需求文档）
- 第3天：创建BDD + ADR（测试 + 架构）
- 第4天：创建SYS + REQ（系统规格 + 需求）
- 第5天：创建IMPL + CTR（实施计划 + 合同）
- 第6天：创建SPEC（技术规格）
- 第7天：创建TASKS + 验证

调用：doc-flow技能开始第1天的工作

═══════════════════════════════════════════════════════════

Reference Files

参考文件

All guidance files located in:

{project_root}/ai_dev_flow/

所有指导文件位于：

{project_root}/ai_dev_flow/

Core Guidance Files

核心指导文件

AI_ASSISTANT_RULES.md - 15 execution rules
DOMAIN_SELECTION_QUESTIONNAIRE.md - Domain selection
CONTRACT_DECISION_QUESTIONNAIRE.md - Contract decision
PROJECT_SETUP_GUIDE.md - Master setup guide
PROJECT_KICKOFF_TASKS.md - Week 1 tasks
TRACEABILITY_SETUP.md - Validation automation
QUICK_REFERENCE.md - Quick reference card

AI_ASSISTANT_RULES.md - 15条执行规则
DOMAIN_SELECTION_QUESTIONNAIRE.md - 领域选择
CONTRACT_DECISION_QUESTIONNAIRE.md - 合同决策
PROJECT_SETUP_GUIDE.md - 主设置指南
PROJECT_KICKOFF_TASKS.md - 第1周任务
TRACEABILITY_SETUP.md - 验证自动化
QUICK_REFERENCE.md - 快速参考卡

Domain Configuration Files

领域配置文件

FINANCIAL_DOMAIN_CONFIG.md - Financial Services (DEFAULT)
SOFTWARE_DOMAIN_CONFIG.md - Software/SaaS
GENERIC_DOMAIN_CONFIG.md - Generic/Other

FINANCIAL_DOMAIN_CONFIG.md - 金融服务（默认）
SOFTWARE_DOMAIN_CONFIG.md - 软件/SaaS
GENERIC_DOMAIN_CONFIG.md - 通用/其他

Example Usage

使用示例

Example 1: Software Application Project

示例1：软件应用项目

User: "Initialize new software application project"

AI Assistant (using project-init skill):

Step 1: Domain Selection
"What is the purpose and focus of this new project?"

User: "2" (Software/SaaS)

AI Assistant:
✓ Domain selected: Software/SaaS
✓ Loading configuration: SOFTWARE_DOMAIN_CONFIG.md
✓ Domain-specific subdirectories: tenant, subscription, billing, workspace

Step 2: Folder Creation
Creating 15-layer architecture (12 artifact directories)...
✓ Created: docs/BRD/
✓ Created: docs/PRD/
✓ Created: docs/EARS/
✓ Created: docs/BDD/
✓ Created: docs/ADR/
✓ Created: docs/SYS/
✓ Created: docs/REQ/
✓ Created: docs/IMPL/
✓ Created: docs/CTR/
✓ Created: docs/SPEC/
✓ Created: docs/TASKS/
✓ Created: docs/REQ/tenant/
✓ Created: docs/REQ/subscription/
✓ Created: docs/REQ/billing/
✓ Created: docs/REQ/workspace/
✓ Created: scripts/
✓ Created: work_plans/

Step 3: Domain Configuration
Applying Software/SaaS terminology:
✓ [RESOURCE_COLLECTION] → Workspace
✓ [RESOURCE_ITEM] → Resource
✓ [USER_ROLE] → Account Admin
✓ [REGULATORY_REQUIREMENT] → SOC2 Control

Step 5: Contract Decision
"Does this project require API contracts?"

User: "1,2" (REST APIs + Event Schemas)

AI Assistant:
✓ Contracts needed
✓ Contract types: REST API (OpenAPI), Event Schemas (AsyncAPI)
✓ Workflow: REQ → IMPL → CTR → SPEC → TASKS

Step 6: Index Files
✓ All 11 index files created

Step 7: Validation
✓ All directories verified
✓ All index files verified

═══════════════════════════════════════════════════════════
              PROJECT INITIALIZATION COMPLETE
═══════════════════════════════════════════════════════════

✓ Domain: Software/SaaS
✓ Folders: Created (11 artifact directories + 4 SaaS subdirectories)
✓ Contracts: Included (CTR layer active)
✓ Workflow: REQ → IMPL → CTR → SPEC → TASKS

Next: Use `doc-flow` skill to begin workflow execution
Start with: BRD-01 (Business Requirements Document)

═══════════════════════════════════════════════════════════

用户："初始化新的软件应用项目"

AI助手（使用project-init技能）：

步骤1：领域选择
"这个新项目的用途和重点是什么？"

用户："2"（软件/SaaS）

AI助手：
✓ 已选择领域：软件/SaaS
✓ 正在加载配置：SOFTWARE_DOMAIN_CONFIG.md
✓ 领域特定子目录：tenant、subscription、billing、workspace

步骤2：创建文件夹
正在创建15层架构（12个工件目录）...
✓ 已创建：docs/BRD/
✓ 已创建：docs/PRD/
✓ 已创建：docs/EARS/
✓ 已创建：docs/BDD/
✓ 已创建：docs/ADR/
✓ 已创建：docs/SYS/
✓ 已创建：docs/REQ/
✓ 已创建：docs/IMPL/
✓ 已创建：docs/CTR/
✓ 已创建：docs/SPEC/
✓ 已创建：docs/TASKS/
✓ 已创建：docs/REQ/tenant/
✓ 已创建：docs/REQ/subscription/
✓ 已创建：docs/REQ/billing/
✓ 已创建：docs/REQ/workspace/
✓ 已创建：scripts/
✓ 已创建：work_plans/

步骤3：领域配置
正在应用软件/SaaS术语：
✓ [RESOURCE_COLLECTION] → 工作区
✓ [RESOURCE_ITEM] → 资源
✓ [USER_ROLE] → 账户管理员
✓ [REGULATORY_REQUIREMENT] → SOC2控制项

步骤5：合同决策
"此项目是否需要API合同？"

用户："1,2"（REST APIs + 事件模式）

AI助手：
✓ 需要合同
✓ 合同类型：REST API（OpenAPI）、事件模式（AsyncAPI）
✓ 工作流：REQ → IMPL → CTR → SPEC → TASKS

步骤6：索引文件
✓ 所有11个索引文件已创建

步骤7：验证
✓ 所有目录已验证
✓ 所有索引文件已验证

═══════════════════════════════════════════════════════════
              项目初始化完成
═══════════════════════════════════════════════════════════

✓ 领域：软件/SaaS
✓ 文件夹：已创建（11个工件目录 + 4个SaaS子目录）
✓ 合同：已包含（CTR层已激活）
✓ 工作流：REQ → IMPL → CTR → SPEC → TASKS

下一步：使用`doc-flow`技能开始工作流执行
从创建BRD-01（业务需求文档）开始

═══════════════════════════════════════════════════════════

Example 2: Software/SaaS Multi-Tenant Platform

示例2：软件/SaaS多租户平台

User: "Set up new SaaS project for team collaboration platform"

AI Assistant (using project-init skill):

Step 1: Domain Selection
User: "2" (Software/SaaS)

AI Assistant:
✓ Domain selected: Software/SaaS
✓ Loading configuration: SOFTWARE_DOMAIN_CONFIG.md
✓ Domain-specific subdirectories: tenant, subscription, billing, workspace

Step 2: Folder Creation
✓ All core directories created
✓ SaaS subdirectories created: tenant/, subscription/, billing/, workspace/
✓ Support directories created: scripts/, work_plans/

Step 3: Domain Configuration
✓ [RESOURCE_COLLECTION] → Workspace
✓ [RESOURCE_ITEM] → Resource
✓ [USER_ROLE] → Account Admin
✓ [TRANSACTION] → API Call
✓ [REGULATORY_REQUIREMENT] → SOC2 Control

Step 5: Contract Decision
User: "1,2" (REST API + Event Schemas)

AI Assistant:
✓ Contracts included
✓ Workflow: REQ → IMPL → CTR → SPEC → TASKS

Project Ready!
Next: Use `doc-flow` skill for BRD-01 creation

用户："为团队协作平台设置新的SaaS项目"

AI助手（使用project-init技能）：

步骤1：领域选择
用户："2"（软件/SaaS）

AI助手：
✓ 已选择领域：软件/SaaS
✓ 正在加载配置：SOFTWARE_DOMAIN_CONFIG.md
✓ 领域特定子目录：tenant、subscription、billing、workspace

步骤2：创建文件夹
✓ 所有核心目录已创建
✓ SaaS子目录已创建：tenant/、subscription/、billing/、workspace/
✓ 支持目录已创建：scripts/、work_plans/

步骤3：领域配置
✓ [RESOURCE_COLLECTION] → 工作区
✓ [RESOURCE_ITEM] → 资源
✓ [USER_ROLE] → 账户管理员
✓ [TRANSACTION] → API调用
✓ [REGULATORY_REQUIREMENT] → SOC2控制项

步骤5：合同决策
用户："1,2"（REST API + 事件模式）

AI助手：
✓ 已包含合同
✓ 工作流：REQ → IMPL → CTR → SPEC → TASKS

项目准备就绪！
下一步：使用`doc-flow`技能创建BRD-01

Troubleshooting

故障排除

Issue: Directory Already Exists

问题：目录已存在

Error:

mkdir: cannot create directory 'docs': File exists

Resolution:

Project may already be initialized
Verify:
```
ls -la docs/
```
If folders exist, skip to doc-flow skill
If folders incomplete, delete and re-run project-init

错误：

mkdir: cannot create directory 'docs': File exists

解决方法：

项目可能已初始化
验证：
```
ls -la docs/
```
如果文件夹已存在，请直接使用doc-flow技能
如果文件夹不完整，请删除后重新运行project-init

Issue: Permission Denied

问题：权限被拒绝

Error:

mkdir: cannot create directory: Permission denied

Resolution:

Check current working directory permissions
Ensure write access to parent directory
Use
```
pwd
```
to verify location

错误：

mkdir: cannot create directory: Permission denied

解决方法：

检查当前工作目录的权限
确保对父目录有写入权限
使用
```
pwd
```
验证当前位置

Issue: Domain Unclear

问题：领域不明确

User says: "I'm not sure which domain to choose"

AI Assistant Action: Run follow-up questions from DOMAIN_SELECTION_QUESTIONNAIRE.md:

Does project involve financial transactions? → Financial Services
Multi-tenant SaaS application? → Software/SaaS
Handle patient health information? → Healthcare
Online store or marketplace? → E-commerce
Connected devices or sensors? → IoT
None of above? → Generic

用户说："我不确定该选择哪个领域"

AI助手操作：运行DOMAIN_SELECTION_QUESTIONNAIRE.md中的后续问题：

项目是否涉及金融交易？→ 金融服务
是否为多租户SaaS应用？→ 软件/SaaS
是否处理患者健康信息？→ 医疗健康
是否为在线商店或市场平台？→ 电子商务
是否涉及互联设备或传感器？→ IoT
以上都不是？→ 通用

Tool Optimization Notes

工具优化说明

Claude Code

File limit: 50K tokens (200KB) standard, 100K max
Strategy: Single comprehensive files
No artificial splitting needed

文件限制：标准50K令牌（200KB），最大100K
策略：使用单一综合文件
无需人工拆分

Gemini CLI

@ reference limit: 10K tokens (40KB)
Large files: Use file read tool instead of
```
@
```
Command:
```
gemini read FILE.md
```

@引用限制：10K令牌（40KB）
大文件：使用文件读取工具而非
```
@
```
命令：
```
gemini read FILE.md
```

GitHub Copilot

Optimal: 10-30KB per file
Large files: Create companion summaries
Working set: Max 10 files in Edits mode

最佳大小：每个文件10-30KB
大文件：创建配套摘要
工作集：在编辑模式下最多10个文件

Related Skills

Quick Reference

快速参考

When to use project-init:

✅ Brand new project (no folders exist)
✅ Greenfield development
✅ Starting from scratch

When to use doc-flow:

✅ Project already initialized
✅ Folders exist (docs/BRD/, docs/PRD/, etc.)
✅ Workflow execution (creating BRD, PRD, SPEC, etc.)

Workflow sequence:

project-init (Day 0) → doc-flow (Day 1+) → other skills (as needed)

End of project-init Skill

何时使用project-init：

✅ 全新项目（无文件夹）
✅ 从零开始开发
✅ 从头启动

何时使用doc-flow：

✅ 项目已初始化
✅ 文件夹已存在（docs/BRD/、docs/PRD/等）
✅ 执行工作流（创建BRD、PRD、SPEC等）

工作流顺序：

project-init（第0天）→ doc-flow（第1天及以后）→ 其他技能（按需使用）

project-init技能结束