执行计划指南：高效任务执行、进度跟踪与质量门检查清单 | 项目管理工具

executing-plans by doanchienthangdev/omgkit

1 周安装量

3 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/doanchienthangdev/omgkit --skill executing-plans

质量管理方法论项目管理

🇨🇳中文介绍

执行计划

快速开始

准备 - 通读整个计划，确认理解，检查依赖项
执行任务 - 阅读 -> 定位 -> 实施 -> 验证 -> 完成
跟踪进度 - 每项任务后更新状态，立即报告阻塞项
通过质量门 - 任务后、阶段后、完成前进行验证
处理偏差 - 记录变更，范围变更需获得批准

功能特性

功能	描述	指南
准备阶段	开始前充分理解	阅读计划，验证依赖项，澄清疑问
任务执行	系统化的逐任务流程	阅读、定位、实施、验证、完成
进度跟踪	实时状态更新	已完成 X，进行中 Y，剩余 Z
质量门	验证检查点	每任务、每阶段、完成前
阻塞项解决	系统性地解除阻塞	记录、评估、尝试、上报、变通方案
偏差处理

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

开源项目教练指南 - 诊断问题、制定行动计划、优化开源项目运营

31,600 周安装

飞书日程待办摘要工作流：AI自动生成每日/每周开工报告，提升个人生产力

24,200 周安装

Lark Task CLI 任务管理工具 - 飞书任务创建、分配、更新与协作完整指南

23,400 周安装

BMAD工作流编排与SSD结构化系统设计 - 多代理AI开发流程自动化

10,600 周安装

# 任务执行清单
开始前：
[ ] 完整阅读任务描述
[ ] 理解验收标准
[ ] 检查依赖项是否完成
[ ] 无阻塞项存在

实施过程中：
[ ] 定位到指定文件
[ ] 理解现有代码上下文
[ ] 增量式实施变更
[ ] 边写代码边写测试

完成后：
[ ] 满足所有验收标准
[ ] 测试在本地通过
[ ] 无代码规范/类型错误
[ ] 任务标记为完成

# 质量门
每项任务后：
npm run lint && npm run typecheck && npm test -- --related

每个阶段后：
npm run lint && npm run typecheck && npm test && npm run build

完成前：
npm run lint && npm run typecheck && npm test --coverage && npm run build

# 进度报告模板
## 状态：[日期 时间]

### 摘要
- 已完成：[N] 项任务
- 进行中：[任务名称]
- 剩余：[M] 项任务
- 阻塞项：[无 | 描述]

### 当前任务
**[任务名称]：**[描述]
- 开始时间：[时间]
- 进度：~60%
- 预计完成时间：[时间]

### 预计完成时间
按计划于 [日期] 完成 | 因 [原因] 延迟

# 阻塞项解决流程
检测到阻塞项
      |
1. 立即记录
   - 什么被阻塞了？
   - 为什么被阻塞？
      |
2. 评估影响
   - 关键路径受影响？
   - 时间敏感？
      |
3. 尝试解决 (15-30 分钟)
   - 快速研究
   - 替代方案
      |
   +-> 已解决 -> 继续
      |
4. 若未解决则上报
   - 报告内容：问题、尝试、请求
      |
5. 等待时变通处理
   - 转向非阻塞任务

应做	应避免
开始前通读整个计划	跳过准备阶段
验证对每项任务的理解	假设任务要求
按顺序执行任务（除非并行）	忽略质量门
每项任务完成后进行验证	隐藏阻塞项或延迟
立即报告阻塞项	未经记录就偏离计划
偏差发生时立即记录	为求速度而牺牲质量
完全完成后再标记为完成	留下部分完成的任务
及早提问	跳过测试步骤

writing-plans - 创建待执行的计划
verifying-before-completion - 质量门检查清单
thinking-sequentially - 跟踪执行进度
solving-problems - 系统性地解决问题

🇺🇸English

Executing Plans

Quick Start

Prepare - Read entire plan, verify understanding, check dependencies
Execute Task - Read -> Navigate -> Implement -> Verify -> Complete
Track Progress - Update status after each task, report blockers immediately
Pass Quality Gates - Validate after task, after phase, before completion
Handle Deviations - Document changes, get approval for scope changes

Features

Feature	Description	Guide
Preparation Phase	Understand before starting	Read plan, verify deps, clarify questions
Task Execution	Systematic per-task flow	Read, navigate, implement, verify, complete
Progress Tracking	Real-time status updates	Completed X, In Progress Y, Remaining Z
Quality Gates	Validation checkpoints	Per-task, per-phase, pre-completion
Blocker Resolution	Unblock systematically	Document, assess, attempt, escalate, workaround
Deviation Handling	Adapt to discoveries	Document, assess scope/timeline, get approval

Common Patterns

# Task Execution Checklist
BEFORE STARTING:
[ ] Read task description completely
[ ] Understand acceptance criteria
[ ] Check dependencies completed
[ ] No blockers present

DURING IMPLEMENTATION:
[ ] Navigate to specified files
[ ] Understand existing code context
[ ] Implement changes incrementally
[ ] Write tests alongside code

AFTER COMPLETION:
[ ] All acceptance criteria met
[ ] Tests pass locally
[ ] No lint/type errors
[ ] Task marked complete

# Quality Gates
AFTER EACH TASK:
npm run lint && npm run typecheck && npm test -- --related

AFTER EACH PHASE:
npm run lint && npm run typecheck && npm test && npm run build

BEFORE COMPLETION:
npm run lint && npm run typecheck && npm test --coverage && npm run build



# Progress Report Template
## Status: [Date Time]

### Summary
- Completed: [N] tasks
- In Progress: [Task name]
- Remaining: [M] tasks
- Blockers: [None | Description]

### Current Task
**[Task Name]:** [Description]
- Started: [Time]
- Progress: ~60%
- Expected completion: [Time]

### ETA
On track for [date] | Delayed by [reason]



# Blocker Resolution Flow
BLOCKER DETECTED
      |
1. DOCUMENT immediately
   - What is blocked?
   - Why is it blocked?
      |
2. ASSESS impact
   - Critical path affected?
   - Time sensitive?
      |
3. ATTEMPT resolution (15-30 min)
   - Quick research
   - Alternative approach
      |
   +-> RESOLVED -> Continue
      |
4. ESCALATE if not resolved
   - Report with: issue, attempts, ask
      |
5. WORK AROUND while waiting
   - Move to non-blocked tasks

Best Practices

Do	Avoid
Read entire plan before starting	Skipping preparation phase
Verify understanding of each task	Assuming task requirements
Execute tasks in sequence (unless parallel)	Ignoring quality gates
Validate after each task completion	Hiding blockers or delays
Report blockers immediately	Deviating without documenting
Document deviations as they occur	Rushing quality for speed
Complete fully before marking done	Leaving tasks partially done
Ask questions early	Skipping testing steps

Related Skills

writing-plans - Create plans to execute
verifying-before-completion - Quality gate checklists
thinking-sequentially - Track execution progress
solving-problems - Resolve blockers systematically

Weekly Installs

Repository

doanchienthangdev/omgkit

GitHub Stars

First Seen

1 day ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

zencoder1

amp1

cline1

openclaw1

opencode1

cursor1