task-decomposition

Name: task-decomposition
Author: DevelopersGlobal

64stars10forks

How to install task-decomposition?

developersglobal/ai-agent-skills/task-decomposition

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill task-decomposition

Installs into the current project.

Summary

Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Large tasks fail in large ways. Decomposed tasks fail in small, fixable ways. This skill breaks any feature or project into atomic tasks — each independently implementable, testable, and deployable.
4
5	## When to Use
6
7	- Before starting any feature that takes more than half a day
8	- When a task feels overwhelming or unclear
9	- When multiple people need to work in parallel
10
11	## Process
12
13	### Step 1: Identify the Deliverable
14
15	1. State what "done" looks like for the whole feature.
16	2. List all the things that must be true when it's complete.
17	3. Identify dependencies: what must exist before any task can start?
18
19	Verify: You can state the full feature goal in 2 sentences.
20
21	### Step 2: Decompose Into Atomic Tasks
22
23	4. Break the feature into tasks where each task:
24	- Can be completed in under 4 hours
25	- Has a single, clear output
26	- Can be verified independently
27	- Can be reverted without breaking other tasks
28	5. Each task should be: `[verb] [noun] so that [outcome]`
29	- ✅ "Add rate limiting to /api/login so that brute-force is prevented"
30	- ❌ "Work on the login security stuff"
31
32	Verify: Every task is under 4 hours. Every task has a clear verify condition.
33
34	### Step 3: Order and Parallelism
35
36	6. Draw the dependency graph — what blocks what?
37	7. Identify tasks that can be done in parallel.
38	8. Sequence tasks so integration happens incrementally (not as one big bang at the end).
39
40	Verify: The dependency order is clear. No unnecessary sequential dependencies.
41
42	### Step 4: Estimate and Adjust
43
44	9. For each task, estimate: best case / worst case / expected.
45	10. If any task's worst case > 1 day: decompose further.
46	11. Total estimate sanity check: does it add up to a reasonable timeline?
47
48	## Common Rationalizations (and Rebuttals)
49
50	\| Excuse \| Rebuttal \|
51	\|--------\|----------\|
52	\| "I'll figure it out as I go" \| Decomposition takes 30 minutes. Rework from poor planning takes days. \|
53	\| "It's too complex to break down" \| Everything can be decomposed. Start with what you know, decompose the rest later. \|
54	\| "The tasks are too granular" \| Granular tasks ship continuously. Coarse tasks ship never. \|
55
56	## Verification
57
58	- [ ] Each task is under 4 hours
59	- [ ] Each task has a single verify condition
60	- [ ] Dependencies mapped — no circular dependencies
61	- [ ] Parallel work identified
62
63	## References
64
65	- [goal-driven-execution skill](../goal-driven-execution/SKILL.md)
66	- [multi-agent-orchestration skill](../multi-agent-orchestration/SKILL.md)

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

task-decomposition

64stars10forks

View on GitHub

How to install task-decomposition?

developersglobal/ai-agent-skills/task-decomposition

$npx -y skills add DevelopersGlobal/ai-agent-skills --skill task-decomposition

Installs into the current project.

Summary

Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	Large tasks fail in large ways. Decomposed tasks fail in small, fixable ways. This skill breaks any feature or project into atomic tasks — each independently implementable, testable, and deployable.
4
5	## When to Use
6
7	- Before starting any feature that takes more than half a day
8	- When a task feels overwhelming or unclear
9	- When multiple people need to work in parallel
10
11	## Process
12
13	### Step 1: Identify the Deliverable
14
15	1. State what "done" looks like for the whole feature.
16	2. List all the things that must be true when it's complete.
17	3. Identify dependencies: what must exist before any task can start?
18
19	Verify: You can state the full feature goal in 2 sentences.
20
21	### Step 2: Decompose Into Atomic Tasks
22
23	4. Break the feature into tasks where each task:
24	- Can be completed in under 4 hours
25	- Has a single, clear output
26	- Can be verified independently
27	- Can be reverted without breaking other tasks
28	5. Each task should be: `[verb] [noun] so that [outcome]`
29	- ✅ "Add rate limiting to /api/login so that brute-force is prevented"
30	- ❌ "Work on the login security stuff"
31
32	Verify: Every task is under 4 hours. Every task has a clear verify condition.
33
34	### Step 3: Order and Parallelism
35
36	6. Draw the dependency graph — what blocks what?
37	7. Identify tasks that can be done in parallel.
38	8. Sequence tasks so integration happens incrementally (not as one big bang at the end).
39
40	Verify: The dependency order is clear. No unnecessary sequential dependencies.
41
42	### Step 4: Estimate and Adjust
43
44	9. For each task, estimate: best case / worst case / expected.
45	10. If any task's worst case > 1 day: decompose further.
46	11. Total estimate sanity check: does it add up to a reasonable timeline?
47
48	## Common Rationalizations (and Rebuttals)
49
50	\| Excuse \| Rebuttal \|
51	\|--------\|----------\|
52	\| "I'll figure it out as I go" \| Decomposition takes 30 minutes. Rework from poor planning takes days. \|
53	\| "It's too complex to break down" \| Everything can be decomposed. Start with what you know, decompose the rest later. \|
54	\| "The tasks are too granular" \| Granular tasks ship continuously. Coarse tasks ship never. \|
55
56	## Verification
57
58	- [ ] Each task is under 4 hours
59	- [ ] Each task has a single verify condition
60	- [ ] Dependencies mapped — no circular dependencies
61	- [ ] Parallel work identified
62
63	## References
64
65	- [goal-driven-execution skill](../goal-driven-execution/SKILL.md)
66	- [multi-agent-orchestration skill](../multi-agent-orchestration/SKILL.md)

People who liked this also viewed

6 picks

Type