Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Work Breakdown Structure for multi-agent project management. Organize work as Roadmap → Epic → Task hierarchy with templates and granularity standards. Use w...
Work Breakdown Structure for multi-agent project management. Organize work as Roadmap → Epic → Task hierarchy with templates and granularity standards. Use w...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
将项目工作从宏观到微观逐层分解:Roadmap → Epic → Task。
层级定义负责人Roadmap产品路线图,规划所有 Epic 的优先级和时间线创始人 / PMEpic大功能模块,包含多个 TaskPM 规划Task可分配给单人、1-2 个工作周期内完成的具体任务PM 创建,Dev 执行
在项目根目录下创建 roadmap/ 目录: roadmap/ ├── roadmap.md ├── epic-001-feature-name/ │ ├── epic.md │ ├── task-001-name.md │ ├── task-002-name.md │ └── task-003-name.md ├── epic-002-feature-name/ │ ├── epic.md │ └── task-001-name.md └── ... 命名规则: Epic 目录:epic-NNN-简短英文名 Task 文件:task-NNN-简短英文名.md 编号在各自层级内递增 模板文件见 templates/ 目录。
这是整个体系的核心。Task 拆得不够细,验收就容易失败。 一个合格的 Task 必须同时满足: 单一交付物 — 只做一件事,只验收一件事 验收可量化 — 条件具体到操作步骤,不是"看起来不错" 体量可控 — 预计 1-2 个工作周期完成,超过则继续拆 独立可测 — 不依赖未完成的其他 Task 判断示例: ❌ "实现农场系统" → 这是 Epic,不是 Task ❌ "优化页面" → 没有验收标准 ❌ "完成种植和收获" → 两件事,应拆两个 Task ✅ "实现 7 块农田网格布局,点击地块高亮" ✅ "接入 Google OAuth,登录后显示用户头像" → 更多拆解指导见 references/breakdown-guide.md
详细操作流程按角色拆分,按需加载: PM(产品经理):references/pm-workflow.md — 规划、拆解、派发、验收、结案 Dev(开发工程师):references/dev-workflow.md — 接收、评估、执行、交付
本 skill 管"做什么":层级、拆解、模板、文档结构。 团队协作协议(如 agent-team-orchestration)管"怎么协作":状态流转、交接协议、评审规则。 两者互补,不重叠。
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.