notion-spec-to-implementation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Spec to Implementation

从规格到实施

Transforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.

将规格转化为可执行的实施计划并进行进度跟踪。获取规格文档、提取需求、拆解为任务，并管理实施工作流。

Quick Start

快速开始

When asked to implement a specification:

Find spec: Use
```
Notion:notion-search
```
to locate specification page
Fetch spec: Use
```
Notion:notion-fetch
```
to read specification content
Extract requirements: Parse and structure requirements from spec
Create plan: Use
```
Notion:notion-create-pages
```
for implementation plan
Find task database: Use
```
Notion:notion-search
```
to locate tasks database
Create tasks: Use
```
Notion:notion-create-pages
```
for individual tasks in task database
Track progress: Use
```
Notion:notion-update-page
```
to log progress and update status

当需要实施某一规格时：

查找规格：使用
```
Notion:notion-search
```
定位规格页面
获取规格：使用
```
Notion:notion-fetch
```
读取规格内容
提取需求：解析并结构化规格中的需求
创建计划：使用
```
Notion:notion-create-pages
```
生成实施计划
查找任务数据库：使用
```
Notion:notion-search
```
定位任务数据库
创建任务：使用
```
Notion:notion-create-pages
```
在任务数据库中创建单个任务
跟踪进度：使用
```
Notion:notion-update-page
```
记录进度并更新状态

Implementation Workflow

实施工作流

Step 1: Find the specification

步骤1：查找规格

1. Search for spec:
   - Use Notion:notion-search with spec name or topic
   - Apply filters if needed (e.g., created_date_range, teamspace_id)
   - Look for spec title or keyword matches
   - If not found or ambiguous, ask user for spec URL/ID

Example searches:
- "User Authentication spec"
- "Payment Integration specification"
- "Mobile App Redesign PRD"

1. 搜索规格：
   - 使用Notion:notion-search，传入规格名称或主题
   - 必要时应用筛选条件（如created_date_range、teamspace_id）
   - 查找匹配的规格标题或关键词
   - 若未找到或结果模糊，向用户索要规格URL/ID

示例搜索：
- "用户认证规格"
- "支付集成技术规格"
- "移动端应用重设计PRD"

Step 2: Fetch and analyze specification

步骤2：获取并分析规格

1. Fetch spec page:
   - Use Notion:notion-fetch with spec URL/ID from search results
   - Read full content including requirements, design, constraints

2. Parse specification:
   - Identify functional requirements
   - Note non-functional requirements (performance, security, etc.)
   - Extract acceptance criteria
   - Identify dependencies and blockers

See reference/spec-parsing.md for parsing patterns.

1. 获取规格页面：
   - 使用Notion:notion-fetch，传入搜索结果中的规格URL/ID
   - 读取完整内容，包括需求、设计、约束条件

2. 解析规格：
   - 识别功能需求
   - 记录非功能需求（性能、安全等）
   - 提取验收标准
   - 识别依赖项和阻塞点

查看reference/spec-parsing.md了解解析模式。

Step 3: Create implementation plan

步骤3：创建实施计划

1. Break down into phases/milestones
2. Identify technical approach
3. List required tasks
4. Estimate effort
5. Identify risks

Use implementation plan template (see [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) or [reference/quick-implementation-plan.md](reference/quick-implementation-plan.md))

1. 拆解为阶段/里程碑
2. 确定技术方案
3. 列出所需任务
4. 评估工作量
5. 识别风险

使用实施计划模板（查看[reference/standard-implementation-plan.md](reference/standard-implementation-plan.md)或[reference/quick-implementation-plan.md](reference/quick-implementation-plan.md)）

Step 4: Create implementation plan page

步骤4：创建实施计划页面

Use Notion:notion-create-pages:
- Title: "Implementation Plan: [Feature Name]"
- Content: Structured plan with phases, tasks, timeline
- Link back to original spec
- Add to appropriate location (project page, database)

使用Notion:notion-create-pages：
- 标题："实施计划：[功能名称]"
- 内容：包含阶段、任务、时间线的结构化计划
- 链接回原始规格
- 添加至合适位置（项目页面、数据库）

Step 5: Find task database

步骤5：查找任务数据库

1. Search for task database:
   - Use Notion:notion-search to find "Tasks" or "Task Management" database
   - Look for engineering/project task tracking system
   - If not found or ambiguous, ask user for database location

2. Fetch database schema:
   - Use Notion:notion-fetch with database URL/ID
   - Get property names, types, and options
   - Identify correct data source from <data-source> tags
   - Note required properties for new tasks

1. 搜索任务数据库：
   - 使用Notion:notion-search查找“Tasks”或“Task Management”数据库
   - 寻找工程/项目任务跟踪系统
   - 若未找到或结果模糊，向用户索要数据库位置

2. 获取数据库架构：
   - 使用Notion:notion-fetch，传入数据库URL/ID
   - 获取属性名称、类型和选项
   - 从<data-source>标签中识别正确的数据源
   - 记录创建新任务所需的必填属性

Step 6: Create implementation tasks

步骤6：创建实施任务

For each task in plan:
1. Create task in task database using Notion:notion-create-pages
2. Use parent: { data_source_id: 'collection://...' }
3. Set properties from schema:
   - Name/Title: Task description
   - Status: To Do
   - Priority: Based on criticality
   - Related Tasks: Link to spec and plan
4. Add implementation details in content

See reference/task-creation.md for task patterns.

针对计划中的每个任务：
1. 使用Notion:notion-create-pages在任务数据库中创建任务
2. 使用parent: { data_source_id: 'collection://...' }
3. 根据架构设置属性：
   - 名称/标题：任务描述
   - 状态：待办
   - 优先级：根据重要性设置
   - 关联任务：链接至规格和计划
4. 在内容中添加实施细节

查看reference/task-creation.md了解任务创建模式。

Step 7: Begin implementation

步骤7：开始实施

1. Update task status to "In Progress"
2. Add initial progress note
3. Document approach and decisions
4. Link relevant resources

1. 将任务状态更新为“进行中”
2. 添加初始进度备注
3. 记录实施方案和决策
4. 链接相关资源

Step 8: Track progress

步骤8：跟踪进度

Regular updates:
1. Update task properties (status, progress)
2. Add progress notes with:
   - What's completed
   - Current focus
   - Blockers/issues
3. Update implementation plan with milestone completion
4. Link to related work (PRs, designs, etc.)

See reference/progress-tracking.md for tracking patterns.

定期更新：
1. 更新任务属性（状态、进度）
2. 添加进度备注，包含：
   - 已完成内容
   - 当前工作重点
   - 阻塞点/问题
3. 更新实施计划中的里程碑完成情况
4. 链接相关工作成果（PR、设计稿等）

查看reference/progress-tracking.md了解跟踪模式。

Spec Analysis Patterns

规格分析模式

Functional Requirements: User stories, feature descriptions, workflows, data requirements, integration points

Non-Functional Requirements: Performance targets, security requirements, scalability needs, availability, compliance

Acceptance Criteria: Testable conditions, user validation points, performance benchmarks, completion definitions

See reference/spec-parsing.md for detailed parsing techniques.

功能需求：用户故事、功能描述、工作流、数据需求、集成点

非功能需求：性能指标、安全要求、可扩展性需求、可用性、合规性

验收标准：可测试条件、用户验证点、性能基准、完成定义

查看reference/spec-parsing.md了解详细解析技巧。

Implementation Plan Structure

实施计划结构

Plan includes: Overview → Linked Spec → Requirements Summary → Technical Approach → Implementation Phases (Goal, Tasks checklist, Estimated effort) → Dependencies → Risks & Mitigation → Timeline → Success Criteria

See reference/standard-implementation-plan.md for full plan template.

计划包含：概述 → 关联规格 → 需求摘要 → 技术方案 → 实施阶段（目标、任务清单、预估工作量） → 依赖项 → 风险与缓解措施 → 时间线 → 成功标准

查看reference/standard-implementation-plan.md获取完整计划模板。

Task Breakdown Patterns

任务拆解模式

By Component: Database, API endpoints, frontend components, integration, testing By Feature Slice: Vertical slices (auth flow, data entry, report generation) By Priority: P0 (must have), P1 (important), P2 (nice to have)

按组件拆分：数据库、API接口、前端组件、集成、测试 按功能切片拆分：垂直切片（认证流程、数据录入、报表生成） 按优先级拆分：P0（必须具备）、P1（重要）、P2（锦上添花）

Progress Logging

进度记录

Daily Updates (active work): Add progress note with completed items, current focus, blockers Milestone Updates (major progress): Update plan checkboxes, add milestone summary, adjust timeline Status Changes (task transitions): Update properties (In Progress → In Review → Done), add completion notes, link deliverables

Progress Format: Date heading → Completed → In Progress → Next Steps → Blockers → Notes

See reference/progress-tracking.md for detailed patterns.

每日更新（活跃工作中）：添加进度备注，包含已完成项、当前重点、阻塞点 里程碑更新（重大进展）：更新计划复选框、添加里程碑摘要、调整时间线 状态变更（任务流转）：更新属性（进行中 → 审核中 → 已完成）、添加完成备注、链接交付物

进度格式：日期标题 → 已完成 → 进行中 → 下一步计划 → 阻塞点 → 备注

查看reference/progress-tracking.md了解详细模式。

Linking Spec to Implementation

规格与实施的关联

Forward Links: Update spec page with "Implementation" section linking to plan and tasks Backward Links: Reference spec in plan and tasks with "Specification" section Bidirectional Traceability: Maintain both directions for easy tracking

正向链接：在规格页面中添加“实施”板块，链接至计划和任务 反向链接：在计划和任务的“规格”板块中引用原始规格 双向可追溯性：维持双向链接以便于跟踪

Implementation Status Tracking

实施状态跟踪

Plan Status: Update with phase completion (✅ Complete, 🔄 In Progress %, ⏳ Not Started) and overall percentage Task Aggregation: Query task database by plan ID to generate summary (complete, in progress, blocked, not started)

计划状态：更新阶段完成情况（✅ 已完成、🔄 进行中百分比、⏳ 未开始）及整体完成率 任务汇总：通过计划ID查询任务数据库生成汇总（已完成、进行中、阻塞、未开始）

Handling Spec Changes

规格变更处理

Detection: Fetch updated spec → compare with plan → identify new requirements → assess impact Propagation: Update plan → create new tasks → update affected tasks → add change note → notify via comments Change Log: Track spec evolution with date, what changed, and impact

检测：获取更新后的规格 → 与现有计划对比 → 识别新需求 → 评估影响传导：更新计划 → 创建新任务 → 更新受影响的任务 → 添加变更备注 → 通过评论通知相关人员 变更日志：记录规格演进，包括日期、变更内容和影响

Common Patterns

常见模式

Feature Flag: Backend (behind flag) → Testing → Frontend (flagged) → Internal rollout → External rollout Database Migration: Schema design → Migration script → Staging test → Production migration → Validation API Development: API design → Backend implementation → Testing & docs → Client integration → Deployment

功能开关：后端（开关后） → 测试 → 前端（带开关） → 内部灰度发布 → 外部全量发布 数据库迁移：架构设计 → 迁移脚本 → 预发布环境测试 → 生产环境迁移 → 验证 API开发：API设计 → 后端实现 → 测试与文档 → 客户端集成 → 部署

Best Practices

最佳实践

Always link spec and implementation: Maintain bidirectional references
Break down into small tasks: Each task should be completable in 1-2 days
Extract clear acceptance criteria: Know when "done" is done
Identify dependencies early: Note blockers in plan
Update progress regularly: Daily notes for active work
Track changes: Document spec updates and their impact
Use checklists: Visual progress indicators help everyone
Link deliverables: PRs, designs, docs should link back to tasks

始终关联规格与实施：维持双向引用
拆解为小型任务：每个任务应能在1-2天内完成
提取明确的验收标准：清楚界定“完成”的标准
尽早识别依赖项：在计划中记录阻塞点
定期更新进度：活跃工作需每日更新备注
跟踪变更：记录规格更新及其影响
使用复选框：可视化进度指示器便于全员查看
链接交付物：PR、设计稿、文档应链接回对应任务

Advanced Features

高级功能

For additional implementation patterns and techniques, see the reference files in reference/.

如需更多实施模式和技巧，请查看reference/中的参考文件。

Common Issues

常见问题

"Can't find spec": Use Notion:notion-search with spec name/topic, try broader terms, or ask user for URL "Multiple specs found": Ask user which spec to implement or show options "Can't find task database": Search for "Tasks" or "Task Management", or ask user for database location "Spec unclear": Note ambiguities in plan, create clarification tasks "Requirements conflicting": Document conflicts, create decision task "Scope too large": Break into smaller specs/phases

“找不到规格”：使用Notion:notion-search传入规格名称/主题，尝试更宽泛的关键词，或向用户索要URL “找到多个规格”：询问用户需要实施哪一个，或展示选项供选择 “找不到任务数据库”：搜索“Tasks”或“Task Management”，或向用户索要数据库位置 “规格表述模糊”：在计划中记录歧义点，创建澄清任务 “需求冲突”：记录冲突内容，创建决策任务 “范围过大”：拆分为更小的规格/阶段

Examples

示例

See examples/ for complete workflows:

examples/api-feature.md - API feature implementation
examples/ui-component.md - Frontend component
examples/database-migration.md - Schema changes

查看examples/获取完整工作流示例：

examples/api-feature.md - API功能实施
examples/ui-component.md - 前端组件实施
examples/database-migration.md - 架构变更实施