project-execution

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Project Execution Skill

项目执行技能

Execute implementation plan systematically with checkpoints, validation, and progress tracking.

通过检查点、验证和进度跟踪，系统化地执行实施计划。

When To Use

适用场景

After planning phase completes
Ready to implement tasks
Need systematic execution with tracking
Want checkpoint-based validation
Executing task lists with dependencies
Monitoring progress and velocity

规划阶段完成后
已准备好执行任务
需要系统化的执行与跟踪
希望基于检查点进行验证
执行存在依赖关系的任务列表
监控进度与交付速度

When NOT To Use

不适用场景

No implementation plan exists (use
```
Skill(attune:project-planning)
```
first)
Still planning or designing (complete planning phase before execution)
Single isolated task (execute directly without framework overhead)
Exploratory coding or prototyping (use focused development instead)

不存在实施计划（请先使用
```
Skill(attune:project-planning)
```
）
仍处于规划或设计阶段（完成规划阶段后再执行）
单个独立任务（直接执行，无需框架开销）
探索性编码或原型开发（使用聚焦式开发替代）

Integration

集成方式

With superpowers:

Uses
```
Skill(superpowers:executing-plans)
```
for systematic execution
Uses
```
Skill(superpowers:systematic-debugging)
```
for issue resolution

Uses

Skill(superpowers:verification-before-completion)

for validation

Uses

Skill(superpowers:test-driven-development)

for TDD workflow

Without superpowers:

Standalone execution framework
Built-in checkpoint validation
Progress tracking patterns

具备超级技能时：

使用
```
Skill(superpowers:executing-plans)
```
实现系统化执行
使用
```
Skill(superpowers:systematic-debugging)
```
解决问题

使用

Skill(superpowers:verification-before-completion)

进行验证

使用

Skill(superpowers:test-driven-development)

实现TDD工作流

不具备超级技能时：

独立的执行框架
内置检查点验证
进度跟踪模式

Execution Framework

执行框架

Pre-Execution Phase

执行前阶段

Actions:

Load implementation plan
Validate project initialized
Check dependencies installed
Review task dependency graph
Identify starting tasks (no dependencies)

Validation:

✅ Plan file exists and is valid
✅ Project structure initialized
✅ Git repository configured
✅ Development environment ready

操作步骤：

加载实施计划
验证项目已初始化
检查依赖是否已安装
评审任务依赖关系图
确定起始任务（无依赖项的任务）

验证项：

✅ 计划文件存在且有效
✅ 项目结构已初始化
✅ Git仓库已配置
✅ 开发环境已就绪

Task Execution Loop

任务执行循环

For each task in dependency order:

markdown

1. PRE-TASK
   - Verify dependencies complete
   - Review acceptance criteria
   - Create feature branch (optional)
   - Set up task context

2. IMPLEMENT (TDD Cycle)
   - Write failing test (RED)
   - Implement minimal code (GREEN)
   - Refactor for quality (REFACTOR)
   - Repeat until all criteria met

3. VALIDATE
   - All tests passing?
   - All acceptance criteria met?
   - Code quality checks pass?
   - Documentation updated?

4. CHECKPOINT
   - Mark task complete IMMEDIATELY (do NOT batch)
   - Update execution state
   - Report progress
   - Identify blockers

Task Completion Discipline: Always call

TaskUpdate(taskId: "X", status: "completed")

right after finishing each task—never defer completions to end of session.

Verification: Run

pytest -v

to verify tests pass.

按依赖顺序执行每个任务：

markdown

1. 任务前准备
   - 验证依赖任务已完成
   - 评审验收标准
   - 创建功能分支（可选）
   - 设置任务上下文

2. 实施阶段（TDD循环）
   - 编写失败的测试用例（RED阶段）
   - 实现最简代码以通过测试（GREEN阶段）
   - 重构代码以提升质量（REFACTOR阶段）
   - 重复上述步骤直至满足所有标准

3. 验证阶段
   - 所有测试是否通过？
   - 所有验收标准是否满足？
   - 代码质量检查是否通过？
   - 文档是否已更新？

4. 检查点
   - 立即标记任务完成（请勿批量操作）
   - 更新执行状态
   - 汇报进度
   - 识别阻塞问题

任务完成规范：完成每个任务后，请立即调用

TaskUpdate(taskId: "X", status: "completed")

——切勿将任务完成汇报推迟到会话结束。

验证方式：运行

pytest -v

以验证测试通过。

Post-Execution Phase

执行后阶段

Actions:

Verify all tasks complete
Run full test suite
Check code quality metrics
Generate completion report
Prepare for deployment/release

操作步骤：

验证所有任务已完成
运行完整测试套件
检查代码质量指标
生成完成报告
准备部署/发布

Task Execution Pattern

任务执行模式

TDD Workflow

TDD工作流

RED Phase:

python

undefined

RED阶段：

python

undefined

Write test that fails

编写会失败的测试用例

def test_user_authentication(): user = authenticate("user@example.com", "password") assert user.is_authenticated

Run test → FAILS (feature not implemented)

运行测试 → 失败（功能未实现）

**Verification:** Run `pytest -v` to verify tests pass.

**GREEN Phase**:
```python

**验证方式**：运行`pytest -v`以验证测试通过。

**GREEN阶段**：
```python

Implement minimal code to pass

实现最简代码以通过测试

def authenticate(email, password): # Simplest implementation user = User.find_by_email(email) if user and user.check_password(password): user.is_authenticated = True return user return None

def authenticate(email, password): # 最简实现 user = User.find_by_email(email) if user and user.check_password(password): user.is_authenticated = True return user return None

Run test → PASSES

运行测试 → 通过

**Verification:** Run `pytest -v` to verify tests pass.

**REFACTOR Phase**:
```python

**验证方式**：运行`pytest -v`以验证测试通过。

**REFACTOR阶段**：
```python

Improve code quality

提升代码质量

def authenticate(email: str, password: str) -> Optional[User]: """Authenticate user with email and password.""" user = User.find_by_email(email) if user is None: return None

if not user.check_password(password):
    return None

user.mark_authenticated()
return user

def authenticate(email: str, password: str) -> Optional[User]: """通过邮箱和密码验证用户身份。""" user = User.find_by_email(email) if user is None: return None

if not user.check_password(password):
    return None

user.mark_authenticated()
return user

Run test → STILL PASSES

运行测试 → 仍然通过

**Verification:** Run `pytest -v` to verify tests pass.

**验证方式**：运行`pytest -v`以验证测试通过。

Checkpoint Validation

检查点验证

Quality Gates:

markdown

- [ ] All acceptance criteria met
- [ ] All tests passing (unit + integration)
- [ ] Code linted (no warnings)
- [ ] Type checking passes (if applicable)
- [ ] Documentation updated
- [ ] No regression in other components

Verification: Run

pytest -v

to verify tests pass.

Automated Checks:

bash

undefined

质量门：

markdown

- [ ] 所有验收标准已满足
- [ ] 所有测试通过（单元测试+集成测试）
- [ ] 代码已通过 lint 检查（无警告）
- [ ] 类型检查通过（如适用）
- [ ] 文档已更新
- [ ] 其他组件无回归问题

验证方式：运行

pytest -v

以验证测试通过。

自动化检查：

bash

undefined

Run quality gates

运行质量门检查

make lint # Linting passes make typecheck # Type checking passes make test # All tests pass make coverage # Coverage threshold met

**Verification:** Run `pytest -v` to verify tests pass.

make lint # Lint 检查通过 make typecheck # 类型检查通过 make test # 所有测试通过 make coverage # 覆盖率达到阈值

**验证方式**：运行`pytest -v`以验证测试通过。

Progress Tracking

进度跟踪

Execution State

执行状态

Save to

.attune/execution-state.json

json

{
  "plan_file": "docs/implementation-plan.md",
  "started_at": "2026-01-02T10:00:00Z",
  "last_checkpoint": "2026-01-02T14:30:22Z",
  "current_sprint": "Sprint 1",
  "current_phase": "Phase 1",
  "tasks": {
    "TASK-001": {
      "status": "complete",
      "started_at": "2026-01-02T10:05:00Z",
      "completed_at": "2026-01-02T10:50:00Z",
      "duration_minutes": 45,
      "acceptance_criteria_met": true,
      "tests_passing": true
    },
    "TASK-002": {
      "status": "in_progress",
      "started_at": "2026-01-02T14:00:00Z",
      "progress_percent": 60,
      "blocker": null
    }
  },
  "metrics": {
    "tasks_complete": 15,
    "tasks_total": 40,
    "completion_percent": 37.5,
    "velocity_tasks_per_day": 3.2,
    "estimated_completion_date": "2026-02-15"
  },
  "blockers": []
}

Verification: Run

pytest -v

to verify tests pass.

保存到

.attune/execution-state.json

：

json

{
  "plan_file": "docs/implementation-plan.md",
  "started_at": "2026-01-02T10:00:00Z",
  "last_checkpoint": "2026-01-02T14:30:22Z",
  "current_sprint": "Sprint 1",
  "current_phase": "Phase 1",
  "tasks": {
    "TASK-001": {
      "status": "complete",
      "started_at": "2026-01-02T10:05:00Z",
      "completed_at": "2026-01-02T10:50:00Z",
      "duration_minutes": 45,
      "acceptance_criteria_met": true,
      "tests_passing": true
    },
    "TASK-002": {
      "status": "in_progress",
      "started_at": "2026-01-02T14:00:00Z",
      "progress_percent": 60,
      "blocker": null
    }
  },
  "metrics": {
    "tasks_complete": 15,
    "tasks_total": 40,
    "completion_percent": 37.5,
    "velocity_tasks_per_day": 3.2,
    "estimated_completion_date": "2026-02-15"
  },
  "blockers": []
}

验证方式：运行

pytest -v

以验证测试通过。

Progress Reports

进度报告

Daily Standup:

markdown

undefined

每日站会报告：

markdown

undefined

Daily Standup - [Date]

每日站会 - [日期]

Yesterday

昨日完成

✅ [Task] ([duration])
✅ [Task] ([duration])

✅ [任务]（[耗时]）
✅ [任务]（[耗时]）

Today

今日计划

🔄 [Task] ([progress]%)
📋 [Task] (planned)

🔄 [任务]（完成进度[progress]%）
📋 [任务]（计划执行）

Blockers

阻塞问题

[Blocker] or None

[阻塞问题描述] 或无

Metrics

指标

Sprint progress: [X/Y] tasks ([%]%)
[Status message]

**Verification:** Run the command with `--help` flag to verify availability.

**Sprint Report**:
```markdown

迭代进度：[X/Y]项任务（完成率[%]%）
[状态说明]

**验证方式**：运行命令时添加`--help`参数以确认可用。

**迭代报告**：
```markdown

Sprint [N] Progress Report

第[N]迭代进度报告

Dates: [Start] - [End] Goal: [Sprint objective]

时间范围：[开始日期] - [结束日期] 目标：[迭代目标]

Completed ([X] tasks)

已完成（[X]项任务）

[Task list]

[任务列表]

In Progress ([Y] tasks)

进行中（[Y]项任务）

[Task] ([progress]%)

[任务]（完成进度[progress]%）

Blocked ([Z] tasks)

阻塞中（[Z]项任务）

[Task]: [Blocker description]

[任务]：[阻塞问题描述]

Burndown

燃尽图

Day 1: [N] tasks remaining
Day 5: [M] tasks remaining ([status])
Estimated completion: [Date] ([delta])

第1天：剩余[N]项任务
第5天：剩余[M]项任务（[状态]）
预计完成日期：[日期]（与计划偏差[delta]）

Risks

风险

[Risk] or None identified

**Verification:** Run the command with `--help` flag to verify availability.

[风险描述] 或未识别到风险

**验证方式**：运行命令时添加`--help`参数以确认可用。

Blocker Management

阻塞问题管理

Blocker Detection

阻塞问题检测

Common Blockers:

Failing tests that can't be fixed quickly
Missing dependencies or APIs
Technical unknowns requiring research
Resource unavailability
Scope ambiguity

常见阻塞问题：

无法快速修复的失败测试
缺失的依赖项或API
需要调研的技术未知项
资源不可用
范围模糊

Systematic Debugging

系统化调试

When blocked, apply debugging framework:

Reproduce: Create minimal reproduction case
Hypothesize: Generate possible causes
Test: Validate hypotheses one by one
Resolve: Implement fix or workaround
Document: Record solution for future

遇到阻塞时，应用以下调试框架：

复现问题：创建最小化的复现案例
提出假设：生成可能的原因
测试假设：逐一验证假设
解决问题：实施修复或替代方案
记录文档：记录解决方案以备未来参考

Escalation

升级上报

When to escalate:

Blocker persists > 2 hours
Requires architecture change
Impacts critical path
Needs stakeholder decision

Escalation format:

markdown

undefined

升级上报场景：

阻塞问题持续超过2小时
需要变更架构
影响关键路径
需要相关方决策

升级上报格式：

markdown

undefined

Blocker: [TASK-XXX] - [Issue]

阻塞问题：[TASK-XXX] - [问题描述]

Symptom: [What's happening]

Impact: [Which tasks/timeline affected]

Attempted Solutions:

[Solution 1] - [Result]
[Solution 2] - [Result]

Recommendation: [Proposed path forward]

Decision Needed: [What needs to be decided]

**Verification:** Run the command with `--help` flag to verify availability.

症状：[当前现象]

影响：[影响的任务/时间线]

已尝试的解决方案：

[解决方案1] - [结果]
[解决方案2] - [结果]

建议：[推荐的解决路径]

需决策事项：[需要确定的内容]

**验证方式**：运行命令时添加`--help`参数以确认可用。

Quality Assurance

质量保证

Definition of Done

完成定义

Task is complete when:

✅ All acceptance criteria met
✅ All tests written and passing
✅ Code reviewed (self or peer)
✅ Linting passes with no warnings
✅ Type checking passes (if applicable)
✅ Documentation updated
✅ No known regressions
✅ Deployed to staging (if applicable)

任务完成的标准：

✅ 所有验收标准已满足
✅ 所有测试用例已编写并通过
✅ 代码已评审（自评或同行评审）
✅ Lint检查通过且无警告
✅ 类型检查通过（如适用）
✅ 文档已更新
✅ 无已知回归问题
✅ 已部署到预发布环境（如适用）

Testing Strategy

测试策略

Test Pyramid:

**Verification:** Run `pytest -v` to verify tests pass.
     /\
    /E2E\      Few, slow, expensive
   /------\
  /  INT  \    Some, moderate speed
 /----------\
/   UNIT    \  Many, fast, cheap

Verification: Run the command with

--help

flag to verify availability.

Per Task:

Unit tests: Test individual functions/classes
Integration tests: Test component interactions
E2E tests: Test complete user flows (for user-facing features)

测试金字塔：

**验证方式**：运行`pytest -v`以验证测试通过。
     /\\
    /E2E\\      数量少、速度慢、成本高
   /------\\
  /  INT  \\    数量中等、速度适中
 /----------\\
/   UNIT    \\  数量多、速度快、成本低

验证方式：运行命令时添加

--help

参数以确认可用。

每项任务的测试要求：

单元测试：测试独立函数/类
集成测试：测试组件间交互
E2E测试：测试完整用户流程（针对面向用户的功能）

Velocity Tracking

速度跟踪

Burndown Metrics

燃尽指标

Track daily:

Tasks remaining
Story points remaining
Days left in sprint
Velocity (tasks or points per day)

Formulas:

**Verification:** Run `pytest -v` to verify tests pass.
Velocity = Tasks completed / Days elapsed
Estimated completion = Tasks remaining / Velocity
On track? = Estimated completion <= Sprint end date

Verification: Run the command with

--help

flag to verify availability.

每日跟踪内容：

剩余任务数量
剩余故事点数
迭代剩余天数
交付速度（每日完成任务数或点数）

计算公式：

**验证方式**：运行`pytest -v`以验证测试通过。
交付速度 = 已完成任务数 / 已用天数
预计完成时间 = 剩余任务数 / 交付速度
是否按计划推进？ = 预计完成时间 <= 迭代结束日期

验证方式：运行命令时添加

--help

参数以确认可用。

Velocity Adjustments

速度调整

If ahead of schedule:

Pull in stretch tasks
Add technical debt reduction
Improve test coverage
Enhance documentation

If behind schedule:

Identify causes (blockers, underestimation)
Reduce scope (drop low-priority tasks)
Increase focus (reduce distractions)
Request help or extend timeline

若进度超前：

拉入拓展任务
处理技术债务
提升测试覆盖率
完善文档

若进度滞后：

识别原因（阻塞问题、估算不足）
缩小范围（移除低优先级任务）
提升专注度（减少干扰）
请求协助或延长时间线

Related Skills

Related Agents

Related Commands

Examples

示例

See

/attune:execute

command documentation for complete examples.

查看

/attune:execute

命令文档获取完整示例。

Troubleshooting

故障排除

Common Issues

常见问题

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with

--verbose

flag

命令未找到 确保所有依赖项已安装且在PATH中

权限错误 检查文件权限并使用适当权限运行

异常行为 添加

--verbose

参数启用详细日志

project-execution

Original

Translation

Table of Contents

目录

Project Execution Skill

项目执行技能

When To Use

适用场景

When NOT To Use

不适用场景

Integration

集成方式

Execution Framework

执行框架

Pre-Execution Phase

执行前阶段

Task Execution Loop

任务执行循环

Post-Execution Phase

执行后阶段

Task Execution Pattern

任务执行模式

TDD Workflow

TDD工作流

Write test that fails

编写会失败的测试用例

Run test → FAILS (feature not implemented)

运行测试 → 失败（功能未实现）

Implement minimal code to pass

实现最简代码以通过测试

Run test → PASSES

运行测试 → 通过

Improve code quality

提升代码质量

Run test → STILL PASSES

运行测试 → 仍然通过

Checkpoint Validation

检查点验证

Run quality gates

运行质量门检查

Progress Tracking

进度跟踪

Execution State

执行状态

Progress Reports

进度报告

Daily Standup - [Date]

每日站会 - [日期]

Yesterday

昨日完成

Today

今日计划

Blockers

阻塞问题

Metrics

指标

Sprint [N] Progress Report

第[N]迭代进度报告

Completed ([X] tasks)

已完成（[X]项任务）

In Progress ([Y] tasks)

进行中（[Y]项任务）

Blocked ([Z] tasks)

阻塞中（[Z]项任务）

Burndown

燃尽图

Risks

风险

Blocker Management

阻塞问题管理

Blocker Detection

阻塞问题检测

Systematic Debugging

系统化调试

Escalation

升级上报

Blocker: [TASK-XXX] - [Issue]

阻塞问题：[TASK-XXX] - [问题描述]

Quality Assurance