docs-init
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePhase 1: Parallel Codebase Scouting
第一阶段:并行代码库侦察
You (main agent) must spawn scouts - subagents cannot spawn subagents.
- Run to identify actual project directories
ls -la - Spawn 2-4 (preferred, uses Gemini 2M context) or
scout-external(fallback) via Task toolscout - Target directories that actually exist - adapt to project structure, don't hardcode paths
- Merge scout results into context summary
你(主Agent)必须生成侦察子Agent - 子Agent不能再生成子Agent。
- 运行命令识别实际的项目目录
ls -la - 通过Task工具生成2-4个(优先选择,使用Gemini 2M上下文)或
scout-external(备选)子Agentscout - 以实际存在的目录为目标 - 根据项目结构调整,不要硬编码路径
- 将侦察子Agent的结果合并到上下文摘要中
Phase 2: Documentation Creation (docs-manager Agent)
第二阶段:文档创建(docs-manager Agent)
Pass the gathered file list to agent to create initial documentation:
docs-manager- : Project overview and PDR (Product Development Requirements)
docs/project-overview-pdr.md - : Codebase summary
docs/codebase-summary.md - : Codebase structure and code standards
docs/code-standards.md - : System architecture
docs/system-architecture.md - Update with initial documentation (keep it under 300 lines)
README.md
Use directory as the source of truth for documentation.
docs/将收集到的文件列表传递给 Agent以创建初始文档:
docs-manager- :项目概述与PDR(产品开发需求)
docs/project-overview-pdr.md - :代码库摘要
docs/codebase-summary.md - :代码库结构与编码标准
docs/code-standards.md - :系统架构
docs/system-architecture.md - 更新以包含初始文档(保持在300行以内)
README.md
将目录作为文档的可信来源。
docs/[CRITICAL] Code Evidence Requirements
[关键] 代码证据要求
All documentation MUST follow evidence rules from →
.claude/skills/feature-docs/SKILL.md[CRITICAL] MANDATORY CODE EVIDENCE RULE所有文档必须遵循中的证据规则 →
.claude/skills/feature-docs/SKILL.md[关键] 强制代码证据规则Quick Reference
快速参考
- Format:
**Evidence**: {FilePath}:{LineNumber} - Status: ✅ Verified / ⚠️ Stale / ❌ Missing
- Verification: 3-pass verification required before completion
- 格式:
**Evidence**: {FilePath}:{LineNumber} - 状态:✅ 已验证 / ⚠️ 已过时 / ❌ 缺失
- 验证:完成前需要经过三轮验证
Evidence Verification Table (Required)
证据验证表(必填)
| Entity/Component | Documented Lines | Actual Lines | Status |
|---|---|---|---|
| L6-15 | L6-15 | ✅ Verified |
IMPORTANT: Do not start implementing.
| 实体/组件 | 已记录行数 | 实际行数 | 状态 |
|---|---|---|---|
| L6-15 | L6-15 | ✅ 已验证 |
重要提示:不要开始实施。
IMPORTANT Task Planning Notes
重要任务规划说明
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed
- 始终规划并拆分多个小型待办任务
- 始终添加一个最终审核待办任务,在最后审核已完成的工作,以发现任何需要修复或改进的地方